You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When referencing a specific commit of a multi-module project, JitPack rewrites the POM so that the other modules in project also get downloaded at the same commit. The bug is that JitPack is also rewriting other entries in the POM, in an unpredictable pattern.
To Reproduce
The latest POM published to mavenCentral is here, condensed below:
com.diffplug.spotless:spotless-plugin-gradle:228aa3...
<dependencies>
com.diffplug.spotless:spotless-lib:228aa3...
com.diffplug.spotless:spotless-lib-extra:228aa3...
com.diffplug.spotless:durian-core:228aa3... <-- error: rewrote group and version
com.diffplug.durian:durian-io:1.2.0 <-- ok: did not rewrite group and version
com.diffplug.spotless:durian-collect:228aa3... <-- error: rewrote group and version again
</dependencies>
Expected behavior
I would expect that only the modules in the multi-module project would be rewritten. In this case, that would mean spotless-lib and spotless-lib-extra. It's especially confusing that durian-core and durian-collect are being rewritten, while durian-io is being left alone.
The text was updated successfully, but these errors were encountered:
nedtwigg
changed the title
JitPack is overwriting dependencies of multi-module project with wrong group and version
Overwriting dependencies of multi-module project with wrong group and version
Dec 30, 2019
nedtwigg
added a commit
to diffplug/spotless
that referenced
this issue
Dec 31, 2019
JitPack is looking for .pom files in the build directory and then checks if they've been installed in ~/.m2. For all found artifacts it will rewrite group and version.
In this case it found durian-core and durian-collect in:
Describe the bug
When referencing a specific commit of a multi-module project, JitPack rewrites the POM so that the other modules in project also get downloaded at the same commit. The bug is that JitPack is also rewriting other entries in the POM, in an unpredictable pattern.
To Reproduce
The latest POM published to mavenCentral is here, condensed below:
For this commit, (buildlog), the resultant POM is here, condensed below:
Expected behavior
I would expect that only the modules in the multi-module project would be rewritten. In this case, that would mean
spotless-lib
andspotless-lib-extra
. It's especially confusing thatdurian-core
anddurian-collect
are being rewritten, whiledurian-io
is being left alone.Additional context
We have purchased a custom group,
com.diffplug
, which we are using above. But we get the same result at thecom.github.diffplug
location as well.The text was updated successfully, but these errors were encountered: