-
Notifications
You must be signed in to change notification settings - Fork 158
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
Gradle metadata not published by artifactory gradle plugin #247
Comments
Gradle 6.0 will no longer require the feature preview flag to produce the Gradle Module Metadata as it will become the default. |
This is increasingly important as Kotlin Multiplatform requires the |
I am working on a PR to address this |
This fixes for example the publication of Gradle Module Metadata, stable since Gradle 5.3 and produced by default with Gradle 6.0. Issue jfrog#247
This now leverages the APIs on MavenNormalizedPublication to make sure all artifacts are published. This fixes for example the publication of Gradle Module Metadata, stable since Gradle 5.3 and produced by default with Gradle 6.0. Fixes jfrog#247
This now leverages the APIs on MavenNormalizedPublication to make sure all artifacts are published. This fixes for example the publication of Gradle Module Metadata, stable since Gradle 5.3 and produced by default with Gradle 6.0. Fixes jfrog#247
A Maven publication does not always have a main artifact. Issue jfrog#247
#265 had been merged. Thanks @ljacomet!
We'll appreciate you feedback for that! |
This has been fixed. Thanks! |
As 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 inbuild/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:
The build log shows that now both
generateMetadataFileForMavenJavaPublication
andgeneratePomFileForMavenJavaPublication
tasks are running before theartifactoryPublish
task, but themodule.json
is not pushed to the artifact repository by theartifactoryDeploy
task.Is this feature supported by the artifactory gradle plugin?
Am I missing an experimental flag or some specific configuration on my side?
The text was updated successfully, but these errors were encountered: