spring-boot

Commit Graph

Author	SHA1	Message	Date
Scott Frederick	f28eb073b3	Remove unnecessary exclusion from web-services starter See gh-28648	4 years ago
Andy Wilkinson	fe7b13ec46	Upgrade to Spring Framework 6 and Jakarta EE 9 Closes gh-28619 Closes gh-28620 Closes gh-28621 Closes gh-28622 Closes gh-28623 Closes gh-28624 Closes gh-28625 Closes gh-28626 Closes gh-28627 Closes gh-28628 Closes gh-28629 Closes gh-28630 Closes gh-28631 Closes gh-28632 Closes gh-28633 Closes gh-28634 Closes gh-28635 Closes gh-28636 Closes gh-28638 Closes gh-28639 Closes gh-28640 Closes gh-28644 Closes gh-28645 Closes gh-28650 Closes gh-28711 Closes gh-28866 Closes gh-28867 Closes gh-28868 Closes gh-28872 See gh-28641 See gh-28642 See gh-28643 See gh-28646 See gh-28647 See gh-28648 See gh-28649 See gh-28721 See gh-28869 See gh-28871	4 years ago
Andy Wilkinson	0de466e06e	Require dependency on s-b-dependencies to use its constraints Previously, Spring Boot's modules published Gradle Module Metadata (GMM) the declared a platform dependency on spring-boot-dependencies. This provided versions for each module's own dependencies but also had they unwanted side-effect of pulling in spring-boot-dependencies constraints which would influence the version of other dependencies declared in the same configuration. This was undesirable as users should be able to opt in to this level of dependency management, either by using the dependency management plugin or by using Gradle's built-in support via a platform dependency on spring-boot-dependencies. This commit reworks how Spring Boot's build uses spring-boot-dependencies and spring-boot-parent to provide its own dependency management. Configurations that aren't seen by consumers are configured to extend a dependencyManagement configuration that has an enforced platform dependency on spring-boot-parent. This enforces spring-boot-parent's version constraints on Spring Boot's build without making them visible to consumers. To ensure that the versions that Spring Boot has been built against are visible to consumers, the Maven publication that produces pom files and GMM for the published modules is configured to use the resolved versions from the module's runtime classpath. Fixes gh-21911	6 years ago
Stephane Nicoll	51740133c3	Upgrade to Saaj Impl 1.5.2 Closes gh-21335	6 years ago
Andy Wilkinson	1f00938c5a	Upgrade to SAAJ Impl 1.5.2 Closes gh-21277	6 years ago
Phillip Webb	e0013454b5	Use parentheses when declaring dependencies Update all dependencies declarations to use the form `scope(reference)` rather than `scope reference`. Prior to this commit we declared dependencies without parentheses unless we were forced to add them due to an `exclude`.	6 years ago
Phillip Webb	0209cd3e4c	Polish quote form used in Gradle scripts Replace Gradle single quote strings with the double quote form whenever possible. The change helps to being consistency to the dependencies section where mostly single quotes were used, but occasionally double quotes were required due to `${}` references.	6 years ago
Andy Wilkinson	714a187d8f	Rework dep mgmt again to avoid consumers picking up strict constraints This paves the way for publishing Gradle module metadata once the problem caused by snapshot versions and our two-step publication process has been addressed. See gh-19609	6 years ago
Andy Wilkinson	aefe52e4d0	Revert "Rework dep management to avoid consumers picking up strict constraints" This reverts commit `b34a311d02` as, having disabled the publishing of Gradle's module metadata (`4f75ab5`), the changes are no longer needed. See gh-19609	6 years ago
Andy Wilkinson	b34a311d02	Rework dep management to avoid consumers picking up strict constraints Previously, enforcedPlatform dependencies were using to pull in the constraints defined in spring-boot-dependencies and spring-boot-parent and applied them strictly so that the constrained version had to be used. This worked as intended in Spring Boot's own build but incorrectly enforced those same strict version requirements on external consumers of Spring Boot's modules. This commit reworks how Spring Boot defines its internal dependency management so that platform dependencies are exposed to external consumers while enforced platform dependencies are using internally. See gh-19609	6 years ago
Andy Wilkinson	ce99db1902	Port the build to Gradle Closes gh-19609 Closes gh-19608	6 years ago
Andy Wilkinson	3d4157ad6d	Correct SCM URLs in published poms Previously, Maven's default behaviour was relied up which resulted in the artifact ID being appended to each URL as it was inherited. This behaviour can only be disabled in Maven 3.6 and later, a version that we cannot use due to an incompatibility with the Flatten Plugin. This commit works around Maven's default behaviour by defining properties for the SCM URL, connection, and developer connection and then explicitly defining the settings in each pom using these properties. The explicit definition of the properties in each pom prevents them being inherited from the parent, thereby disabling the unwanted appending of the artifact ID to the URL. Fixes gh-18328	6 years ago
Spring Operator	3e2b6ac8ed	Update build and setup configuration to use HTTPS See gh-16246	7 years ago
Andy Wilkinson	d6a869fa98	Switch to Jakarta EE API dependencies where possible Closes gh-16113 Closes gh-16112 Closes gh-16111 Closes gh-15916 Closes gh-15689	7 years ago
Andy Wilkinson	923b48bae0	Exclude duplicate javax.activation classes from web services starter In 2.3.1, the JAX-B API now depends on javax.activation-api. This has caused duplicate Activation classes to appear in the starter due to dependencies on both javax.activation:activation:1.1 and on javax.activation:javax.activation-api:1.2. This commit removes the duplicate classes by excluding the former in favour of the latter. See gh-14754	7 years ago
Stephane Nicoll	4bc5535c37	Rework "Remove redundant spring-boot-starter dependency" This commit reworks `40d8726` as it has introduced an unfortunate side effect for those who are using a starter with optional starter dependencies. `spring-boot-starter-web` defines the json and the tomcat starter. The latter is part of a set of starters that do not bring the base starter and the former can be excluded to use gson rather than jackson. When such arrangement happens, spring-boot-starter-web no longer defines the base starter (and therefore doesn't bring the core dependencies that Spring Boot needs to bootstrap). This commit reviews the starters that define optional starters and reintroduce the base starter. Closes gh-14076	7 years ago
Jan Groot	40d8726d47	Remove redundant spring-boot-starter dependencies from starters Closes gh-14078	7 years ago
Madhura Bhave	9570cd4172	Add saaj and jax-ws to webservices starter Closes gh-13360	8 years ago
Stephane Nicoll	b2f34f5c20	Remove spring.provides Closes gh-12435	8 years ago
Andy Wilkinson	0aedd3f11d	Exclude tomcat-annotations-api and use javax.annotations-api instead Closes gh-10133	8 years ago
Phillip Webb	b87f9c11f1	Fix POMs for the updated build/release process Fix POMs following project relocations and apply CI friendly Maven conventions. See gh-9316	8 years ago
Phillip Webb	0ba4830b4f	Relocate projects to spring-boot-project Move projects to better reflect the way that Spring Boot is released. The following projects are under `spring-boot-project`: - `spring-boot` - `spring-boot-autoconfigure` - `spring-boot-tools` - `spring-boot-starters` - `spring-boot-actuator` - `spring-boot-actuator-autoconfigure` - `spring-boot-test` - `spring-boot-test-autoconfigure` - `spring-boot-devtools` - `spring-boot-cli` - `spring-boot-docs` See gh-9316	8 years ago

24 Commits (3.0.x)