-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Fix test-distribution classpath re resolver #8187
Fix test-distribution classpath re resolver #8187
Conversation
As currently it seems mixed versions of resolver artifacts are present on classpath. Resolver 1.8.0 introduces a binary breakage. Anyway, this fixes the thing, as impl was actually coming in as transitive dep of maven-resolver-provider, that is NOT the same version as the rest of resolver dependencies. Relying on transitive while fixing other versions is wrong.
And add exclusion to banned dependency, that is used when running in SISU container.
<artifactId>maven-resolver-impl</artifactId> | ||
<version>${maven.resolver.version}</version> | ||
<exclusions> | ||
<!-- Used when running in SISU container to manage beans lifecycle (of locking factories) --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand this comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sisu container is able to manage lifecycle, and on container shutdown will invoke this method. For your case is not needee, as you craft resolver manually, but also do not use any special kind of named locks that would require this cleanup (you use defaults).
Strange, this PR now made module far-far before change to break and seems completely unrelated
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
FTR, created eclipse-sisu/sisu-project#58 |
As currently it seems mixed versions of resolver artifacts are
present on classpath. Resolver 1.8.0 introduces a binary
breakage against 1.6.x.
Updated to bugfix 1.8.1 resolver
Anyway, this fixes the thing, as impl was actually coming in
as transitive dep of maven-resolver-provider, that is NOT
the same version as the rest of resolver dependencies.
Relying on transitive while fixing other versions is wrong.