GitHub-Spring/spring-framework - spring-framework - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
rstoyanchev	3b13f2ed38	Update code-of-conduct email	2 years ago
Brian Clozel	be560d7ad5	Remove artifactory plugin from build As we're moving the build to Concourse CI, we don't need to use the Artifactory plugin anymore. Our build will publish the artifacts to a repository on the local filesystem and will push its content to Artifactory with the spring-io/artifactory-resource. This commit also adds the conditional configuration for publishing to a local repository. See gh-22490	6 years ago
Brian Clozel	a446f572a6	Fix missing project information in generated POMS This commit ensures that the project name and description are published with the generated POMs.	6 years ago
Brian Clozel	7cfae94d70	Use resolved dependency versions for published POMs This commit ensures that Gradle publications are using resolved dependency versions for Maven publications (i.e. POMs). This is useful since we're using the Spring dependency management plugin and we can't rely on declared dependency versions only. See gh-23282	6 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	6 years ago
Brian Clozel	7902ae4c1f	Change Gradle publication name for artifactory This commit switches to the default publication name considered by the artifactory plugin when it comes to publishing artifacts to the artifactory repository. See gh-23282	6 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	6 years ago