Fully concurrent builder for Maven 4 #1429
Draft
Conversation
This file contains 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
gnodet
force-pushed
the
concurrent-lifecycle
branch
from
4109405
to
c96755e
Compare
gnodet
force-pushed
the
concurrent-lifecycle
branch
from
c96755e
to
02cdc33
Compare
gnodet
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR aims at defining a complete new lifecycle for Maven 4. This lifecycle is enabled by default for easy testing in this PR, which would be equivalent as running
mvn --builder=concurrent -T1C.Note that the builder is fully concurrent, so that a project may not be executed in a single thread and continuously, rather, all mojos will be scheduled independently. The builder displays a nice summary at the beginning (currently at
infolevel).Status
MavenProjectwrapProjectwhich is immutable instead.