Closed wardev closed 3 years ago
Thanks for reporting this issue. Yes, you are right. The javadoc for the getExceptions()
method says:
Gets the exceptions that occurred while resolving the artifact. Note that this list can be non-empty even if the artifact was successfully resolved, e.g. when one of the contacted remote repositories didn't contain the artifact but a later repository eventually contained it.
I will only log exception and not break the build
Fixed: 0.15.3
That worked! Thanks for the quick release!
Hi,
First, thanks for making japicmp!
I have a pom with multiple repositories. One, of the repositories is inaccessible. The old version artifact is available from a repository further down the list. Maven's normal dependency resolution logic is fine with that, but japicmp is breaking the build. I think the problem is that the check at [1] is to strict. It checks if any errors occurred. In this case some errors occurred but the artifact was still resolved successfully. I think that line should just check if the artifact was resolved successfully. I've included below the debug output from maven which shows a successful download of the the old version artifact, and then japicmp breaking the build because it couldn't download the old version artifact.
Regards, Evan
[1] https://github.com/siom79/japicmp/blob/f0f845243b09b1f197f44514adf9a83f7581315f/japicmp-maven-plugin/src/main/java/japicmp/maven/JApiCmpMojo.java#L226