-
Notifications
You must be signed in to change notification settings - Fork 38.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish Gradle metadata #23503
Comments
Reverting and reopening since publishing Gradle metadata seems to fails for a combination of "Gradle < 6.0" and "using the spring dependency management plugin". Here's a repro project: plugins {
id 'java'
id "io.spring.dependency-management" version "1.0.8.RELEASE"
}
repositories {
mavenCentral()
maven { url 'https://repo.spring.io/milestone' }
maven { url 'https://repo.spring.io/snapshot' }
}
dependencyManagement {
imports {
mavenBom 'org.springframework:spring-framework-bom:5.2.2.BUILD-SNAPSHOT'
}
}
dependencies {
implementation 'org.springframework:spring-core'
}
task testbom {
doLast {
def managedVersions = dependencyManagement.managedVersions
def springCoreVersion = managedVersions['org.springframework:spring-core']
println springCoreVersion
}
} This is failing with:
As this combination (Gradle version and plugin) is quite popular, I'm unpublishing this metadata for now. We might consider publishing that now in a future minor version as we're moving on with the maintenance versions in this branch. |
Closed with 9bd60f6 |
As of its 5.3 version, Gradle is able to generate and consume Gradle-specific build metadata. It's an opt-in feature for now, but it will be enabled by default with Gradle 6.0.
Should we produce and publish this metadata for our 5.2.0 release?
Here is the
module.json
file published forspring-webflux
:Here is the
module.json
file for our Java Platform (also exported as a Maven BOM):Note that all the generated POMs are slightly changed with the following:
The text was updated successfully, but these errors were encountered: