fix(MavenLauncher): maximum recovery from missing libraries #4336
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.
The way Spoon build the class path for a Maven project in
MavenLauncher
is to launchmvn dependencies:build-classpath
to generate a text file containing class path. However, for multi-module projects, when there is a module whose dependencies can not be resolved, Maven will skip the remaining modules and report an error.In this PR, I added the
-fn
flag to the Maven invocation request such that Maven can continue to resolve dependencies for the remaining modules even though there is an error occurred. This can help resolve as many libraries as possible.