Closed gastaldi closed 2 months ago
I'd suspect this have to to with the move from Maven resolver to MIMA. @cstamas do you have an idea of what may be the cause of this issue?
I t looks like Pomchecker lost the ability to resolve artifacts from a local directory that's not explicitly listed as a local repository. Pomchcker evaluates files individually AFAICT and thus defining a location where other artifacts may be found (the staging directory configured in JReleaser) is not built-in behavior. I believe the expectation is to find parent poms using the value of <relativePath>
by default, which in this case is undefined and results in the wrong parent pom search.
It may be the case that pomchecker requires adding an extra parameter for a local directory that defines a local repository that may be searched during model resolution.
This was old code: https://github.com/kordamp/pomchecker/pull/20/files#diff-c2b667416488ee8da6c6cea7d47ab804bce3d1609a3bb8b692a9123608db088dL122-L130
and here is withUser(true) (so should pick up whatever is in settings.xml), or simple override should be added?
🎉 This issue has been resolved in v1.13.0
(Release Notes)
I don't know if this belongs to https://github.com/jreleaser/jreleaser or here, but when deploying a multimodule project, Pomchecker does not resolve the dependencies from the same repository.
Having the following
repository
contents:Gives the following output when PomChecker runs:
Meaning that it could not resolve the
io.quarkiverse.slack:quarkus-slack-parent:pom:0.0.2
(which is not in central, obviously) while resolvingio.quarkiverse.slack:quarkus-slack-deployment:0.0.2