Gradle metadata not published by artifactory gradle plugin
See original GitHub issueAs of Gradle 5.3, we can now publish Gradle metadata with our build. Right now, one needs to enable this feature with enableFeaturePreview("GRADLE_METADATA")
.
I’m using Gradle 5.6.1 and artifactory plugin 4.9.8 with a publication setup. The module.json
are generated during the build (and they can be seen in build/publications/mavenJava/
for each module. As advised by Gradle developers I’m publishing porper software components as well.
You can more details about my setup here and here, but basically:
// using a software component in the publication setup
publishing {
publications {
mavenJava(MavenPublication) {
from components.java
artifact sourcesJar
artifact javadocJar
}
}
}
// publishing the maven publication for each project
artifactoryPublish {
publications(publishing.publications.mavenJava)
}
The build log shows that now both generateMetadataFileForMavenJavaPublication
and generatePomFileForMavenJavaPublication
tasks are running before the artifactoryPublish
task, but the module.json
is not pushed to the artifact repository by the artifactoryDeploy
task.
Is this feature supported by the artifactory gradle plugin? Am I missing an experimental flag or some specific configuration on my side?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:6 (4 by maintainers)
Top GitHub Comments
https://github.com/jfrog/build-info/pull/265 had been merged. Thanks @ljacomet!
@bclozel, @ansman, A snapshot is available in
oss.jfrog.org
. To test it, use the following configuration in yourbuild.gradle
file:We’ll appreciate you feedback for that!
This has been fixed. Thanks!