tchekai704/src-spring-framework - src-spring-framework - Gitea

Author	SHA1	Message	Date
Brian Clozel	d4089747b8	Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates	5 years ago
Brian Clozel	86c734785d	Apply Artifactory Gradle plugin Instead of relying on the CI server to apply and configure this plugin, this commit does it directly in the Spring Framework build. This allows us to take full control over which projects are published and how. See gh-23282	5 years ago
Brian Clozel	7ce1f5e652	Configure Maven publications with Gradle Prior to this commit, the build would use a custom task to create a BOM and manually include/exclude/customize dependencies. It would also use the "maven" plugin to customize the POM before publication. This commit now uses a Gradle Java Platform for publishing the Spring Framework BOM. We're also now using the "maven-publish" plugin to prepare and customize publications. This commit also tells the artifactory plugin (which is currently applied only on the CI) not to publish internal modules. See gh-23282	5 years ago
Brian Clozel	e9523161f0	Revert "Revert "Refactor Gradle tasks in Spring Framework build"" This reverts commit `fb0d618751`.	5 years ago
Stephane Nicoll	fb0d618751	Revert "Refactor Gradle tasks in Spring Framework build" This reverts commit `1539ba8991`.	5 years ago
Brian Clozel	1539ba8991	Refactor Gradle tasks in Spring Framework build This commit reorganizes tasks and scripts in the build to only apply them where they're needed. We're considering here 3 "types" of projects in our build: * the root project, handling documentation, publishing, etc * framework modules (a project that's published as a spring artifact) * internal modules, such as the BOM, our coroutines support and our integration-tests With this change, we're strealining the project configuration for all spring modules and only applying plugins when needed (typically our kotlin support). See gh-23282	5 years ago
Brian Clozel	998f6af290	Move integration tests to dedicated module This commit moves the dependency management and test source files related to integration tests to a dedicated module. This allows us to focus the root project on building the Spring Framework. See gh-23282	5 years ago