Exposing the problem causing artifact if Resolver throws an exception#1224
Merged
andrzejj0 merged 1 commit intomojohaus:masterfrom Mar 16, 2025
Merged
Conversation
Contributor
Author
|
@slawekjaranowski please check; we can release after this one is merged. |
versions-common/src/main/java/org/codehaus/mojo/versions/api/VersionRetrievalException.java
Outdated
Show resolved
Hide resolved
andrzejj0
force-pushed
the
log-deps-on-resolver-errors
branch
2 times, most recently
from
7762c1d to
2c256e8
Compare
slawekjaranowski
approved these changes
Mar 16, 2025
andrzejj0
force-pushed
the
log-deps-on-resolver-errors
branch
from
2c256e8 to
b8bae78
Compare
Contributor
Author
|
Automatic import optimalisation was enabled... Will merge if build is clean. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Any problems causing the Resolver to fail resolving a version should be reported to the end user, including the artifact causing the problem which can facilitate problem resolution on the resolver end.
Here we're propagating the information about the problematic artifact to the mojo which can then output it in the log.
Related: #1147