-
Notifications
You must be signed in to change notification settings - Fork 33
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 consumers issue #81
Comments
First of all, thank you for reporting this @elect86. Ideally, of course, Gradle tooling didn't have this limitation. But it sounds like that this is not going to happen? Now... I have no plans to move to Gradle so (1) won't work. (2) might work, but depends a bit on complexity of the approach. If it's easy to show in form of PR I'd be interested. But... alternatively maybe just going with the simplest (in some sense) choice of just flattening versions to remove use of intermediate
Note, too, that the oldest branch from which full releases are likely is 2.17 (full patch release takes 2.5 - 3 hours to make so I have to choose where to spend my time for maximum benefit). So PR probably should be against 2.17 |
That's actually the simplest solution, yes I'll craft one with that then |
Great! Also please add an XML comment or two to indicate reasoning (and if there's a link to Gradle platform limitation, that'd be great) |
This reverts commit 77da4b4.
Gradle has a known issue when it comes to bom, it can't properly resolve dependency versions which have more than one layer of indirection
In my case, that is
jackson.version.module.kotlin
in jackson-bom-2.16.1If
jackson.version.module.kotlin
had${jackson.version}
, then it'd work fine insteadHow to fix this?
.pom
for Maven users and.module
for Gradle ones.module
file generation and include that in the publication, as I did with pom-Scijava, where you have platform (and catalog, if you want) published altogether at the very same coordinates.I can provide a PR for either of them
The text was updated successfully, but these errors were encountered: