Incremental build api - #1118
Closed
gnodet wants to merge 1 commit into
Closed
Conversation
gnodet
force-pushed
the
build-context
branch
2 times, most recently
from
May 24, 2023 07:22
32fabfe to
d4b6a15
Compare
Member
|
This is a must have thing... |
gnodet
force-pushed
the
build-context
branch
from
December 13, 2023 19:32
2c7b5ad to
9b2bbbd
Compare
9 tasks
gnodet
added a commit
that referenced
this pull request
Jul 28, 2026
Avoid package collision with the incremental build context API (PR #1118) which uses org.apache.maven.api.build for BuildContext, Input, Output, etc. Moving the report types to a sub-package keeps both features cleanly separated under the shared org.apache.maven.api.build namespace. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Jul 28, 2026
Port the incremental build context from PR apache#1118 to Maven 4 conventions: - API in org.apache.maven.api.build.context (avoids collision with build report API) - Core impl in maven-impl using Maven 4 DI (org.apache.maven.api.di) - Maven integration (MavenBuildContext, ProjectWorkspace, digest) stays in maven-core - Replace plexus-utils dependencies (MatchPatterns, CachingOutputStream) with pure Java - Add Maven 4 annotations (@experimental, @nonnull, @nullable, @SInCE 4.0.0) - All 41 tests passing in maven-impl Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
Author
|
Superseded by #12576, which ports this incremental build context API to Maven 4 architecture:
Thank you @gnodet for the original design — the Workspace abstraction, Metadata/Resource type hierarchy, and InputSet aggregation pattern are excellent foundations. |
Contributor
Author
|
Closing in favor of #12576 which modernizes this for Maven 4. |
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.
This is a draft of an incremental build api to replace https://github.com/sonatype/sisu-build-api and https://github.com/codehaus-plexus/plexus-build-api.
It's very heavily inspired from https://github.com/takari/io.takari.incrementalbuild.
Usage snippets are available https://github.com/gnodet/maven/blob/build-context/maven-core/src/test/java/org/apache/maven/internal/build/impl/Snippets.java
More to follow...