Publish to secondary respository without sources

Help/Discuss
1

hi all,

I have a legacy java (web) application built with gradle. it creates multiple artifacts, but is not multi-module for historic reasons. the artifacts are introduced using java { registerFeature(…) } and extra sourcesets. we are also leveraging testFixtures which also produces an artifact. for all artifacts, ‘withSourcesJar()’ and ‘withJavadocJar()’ is used.

the artifacts are the published to a private repository using maven-publish. also some extra artifacts produced by some custom jar tasks are published to that repository.

the artifacts from that repository can successfully be consumed by other projects. the variants can be referenced using capabilities {requireCapability(…)}. the thirdparty-dependencies are automatically resolved in the consuming projects.

I now need to publish the main artifacts (jar, secondJar, testFixturesJar) to another (semi-private) repository - but WITHOUT the sources (because of the ‘semi’), but keeping the full consuming capabilities. consumers might be maven or gradle projects.

I’m aware of Customizing publishing which is kind of describing my exact requirement - but - as far as I understand - this would need to remove withSourcesJar() (because otherwise “from components.java” will auto-include everything in my single publication) and introducing the source-tasks again manually. And the dependencies are also not published with the described solution. I’d need to manually describe pom{withXml…} which feels kind of awkward.

I assume my requirements, having ‘private’ sources, are not that exotic. what’s the cleanest, gradle-likest solution for this?

br
gerhard

2

I assume my requirements, having ‘private’ sources, are not that exotic.

“private” sources no.
But “sometimes private” sources probably are exotic. :smiley:

Removing withSourcesJar() and instead adding the sources jar using artifact(...) could be a solution, but not really a good one. Because then it is just a jar file that is uploaded additionally, but not a proper variant you could select using attributes which for example IntelliJ uses to download sources and would then not find those sources anymore.

I think the only way to publish in one build execution would be to configure a second software component like the java component where you then not have the sources variant and publish that component to the semi-private repository.

But I think the best and most pragmatic solution in your case might be to publish the artifacts in two Gradle invocations, having the withSourcesJar() calls guarded by an if so that it is not called when publishing to the semi-private repository.

3

sometimes it’s that simple :slight_smile:
I was also aware of the downside when using explicit artifact() in the publication.
and for the secondary component, the usecase doesn’t justify the (expected) added complexity.

thx for your help!

1 Like