[MNG-7629] Change reactor reader to copy packaged artifacts and reuse them across builds if needed#954
Conversation
… them across builds if needed
178a46e to
7421d07
Compare
d7931d9 to
489e194
Compare
489e194 to
9a5ac83
Compare
mthmulders
left a comment
There was a problem hiding this comment.
Left a couple of questions.
Also, I wonder if this change allows us to remove the fallbacks that were previously on line 150 - 159. Since those lines aren't changed, it seems GitHub doesn't allow me to comment on the spot :-\.
Good question. I think part of it could be removed, but we need to keep the Another possible strategy instead of copying the artifacts would be to only record their paths. |
This reverts commit 7421d07. # Conflicts: # maven-core/src/main/java/org/apache/maven/ReactorReader.java
I'm not sure I understand. You mean "run |
Yes. I haven't removed this part in this PR. If the main artifacts have not been packaged, they will point to the |
MartinKanters
left a comment
There was a problem hiding this comment.
I like the solution in general. Added small comments.
Co-authored-by: Martin Kanters <mkanters93@gmail.com>
I've been able to remove the check to load the packaged artifacts. |
|
In the internal project local repository structure, I've added a child directory with the version of a given artifact. This gives a structure which is closer to the maven local repository, and it allows deleting artifacts during the clean phase without having to rely on a heuristic to split between classifier / version / extension. @mthmulders @MartinKanters I'm done on this PR, so unless you have further comments, an approval before the merge would be nice ! |
MartinKanters
left a comment
There was a problem hiding this comment.
Looks like an elegant solution to me. Nice job.
mthmulders
left a comment
There was a problem hiding this comment.
I've been able to remove the check to load the packaged artifacts.
Awesome.
In the internal project local repository structure, I've added a child directory with the version of a given artifact. This gives a structure which is closer to the maven local repository, and it allows deleting artifacts during the clean phase without having to rely on a heuristic to split between classifier / version / extension.
Also awesome.
Happy to see this improvement. Thanks a lot @gnodet!
|
Resolve #8824 |
Similar to #912 but without removing the best effort artifact resolution to keep
mvn testworking if possible.This require a few ITs to be modified:
apache/maven-integration-testing#234