slachiewicz opened a new issue, #13302:
URL: https://github.com/apache/maven/issues/13302
### Description
An impact study, not a migration: on 2026-09-30 the Apache Maven components
and plugins were ported from the Maven 3 API (`MavenProject`,
`org.apache.maven.artifact`, `maven-compat`, Sisu and Plexus components) to the
Maven 4 API at 4.0.0-rc-7, to measure what ports cleanly, where the Maven 4 API
has no equivalent, and which components are better kept on Maven 3 than ported.
The study was closed as not planned on 2026-10-07: Maven 4.0.0 is not
released, and a second line per component would double the maintenance. No port
was merged. This description was revised on 2026-11-14 to say where each
finding stands now.
How to read it:
- Component results are measurements from 2026-09-30 at rc-7 and were not
re-run. The ports are local branches named `agent/mvn4-api`, rebased onto their
default branches on 2026-10-06; none is published. The 19 study pull requests
are closed unmerged; two CI fixes that came with them were merged. The comments
below are the record of that date and are not updated.
- The gap tables were rechecked against the code on 2026-11-14, on
`maven-4.0.x` (35b8736f85) and `master` (6145dae0de). `maven-4.0.x` is what
4.0.0 will ship: its API modules differ from rc-7 by fewer than 200 changed
lines. `master` is 4.2.0-SNAPSHOT and carries the new API. A gap closed on
`master` only is not closed for a plugin that targets 4.0.x, and every API type
added on `master` is still `@Experimental`.
- The design work moved to other issues: #13460 (migrate Maven's internals
to the Maven 4 API, with the Maven 3 types kept as wrappers until Maven 5),
#13499 (API and SPI gaps for build extensions and IDE embedders, from Tycho and
m2e), #13989 (build extensions on Maven DI alone), #13223 (class loading),
#13472 (an execution service for embedded use) and #13762 (replace `aggregator`
and `@Execute` with phase ordering).
### Where the gaps stand
#### Closed on both branches
| Gap at rc-7 | Fixed by |
|---|---|
| `PackagingProvider` ignored by the packaging registry (#13306, reopened
and still open) | `maven-4.0.x`: #13550, the backport of #13319. `master`:
#13319 was reverted by #13574 and redone in #13570, which also filters
providers by class-loader visibility. Core IT `gh-13306` on both branches |
| `MojoExecution.getPlugin().getDependencies()` throws when the plugin realm
comes from the cache (#13307) | #13312 |
| Maven DI cannot inject an empty `List` or `Map` | #13878, backport #13879 |
#### Closed on `master` only
| Gap at rc-7 | Fixed by | Still missing |
|---|---|---|
| An `XmlNode` mojo parameter loses its XML attributes (#13305) | #13636
replaced the Plexus configurator; the node is passed through unchanged (#13528)
| `PlexusConfiguration` parameters remain unsupported; `XmlNode` is the
replacement |
| No conflict data on `Node` | #13485: `winner()`, `premanagedVersion()`,
`premanagedScope()`, `originalScope()` | A parent link and the declared version
constraint |
| No request data on `Session`: `-ff`/`-fae`/`-fn`, requested `-P` profiles,
`-pl`, `-rf`, threads | #13542: `Session.buildInvocation()` | `-e`, and the
settings and toolchains file locations |
#### Partly closed, on `master` only
| Gap at rc-7 | What `master` has | What is still missing |
|---|---|---|
| No plugin manager: nothing resolves, configures or runs another plugin's
mojo, so a Maven 4 site plugin cannot run reports | `PluginManager.loadPlugin`
(#13625) returns a plugin's descriptor, dependencies and realm with a `Lookup`;
`LifecycleExecutor` (#13612) plans and executes a project's lifecycle, with a
filter | A configured mojo instance that is not executed: a site plugin calls
`generate` on the report, it does not run the goal. Tracked in #13518.
`loadPlugin` accepts build plugins only, not the ones under `<reporting>` |
| No SPI to skip or replace a mojo execution, and no lifecycle participant |
`ProjectTransformer` (#13808) replaces `afterProjectsRead`;
`ExecutionListener`, and `Listener` discovered as an SPI service (#13701);
`LifecycleProcessor`; a static filter, `maven.lifecycle.filter` (#13392) | A
decision taken at execution time with access to the build state, which is what
the build cache needs: #13987. Per-project callbacks: #13807 |
| plugin-tools writes no `<resolutions>`, does not extract
`dependencyResolutionPathScopes`, and fails on `dependencyCollection` | Maven
has its own descriptor generator, `maven-plugin-mixin` (#13644, #13658), an
annotation processor that writes all three | No `<resolutions>` support found
in maven-plugin-tools, whose latest release is still 4.0.0-beta-3;
apache/maven-plugin-tools#1229 (constructor injection) is open |
| Legacy `BuildContext` forces `org.eclipse.sisu.plexus` at compile scope |
Nothing merged | #12576 was closed; #13983 replaces it with an incremental
build context, and apache/maven-filtering#363 is the experiment on it |
#### Open, with a design issue
| Gap | Issue |
|---|---|
| No public `Session` outside a Maven runtime. `ApiRunner` is still internal
to `maven-impl`, though it is now used and fixed as if it were public (#13655,
#13469, #13835) | #13472 |
| A Maven 4 API mojo cannot inject a Sisu or Plexus component from its
plugin realm (`ScmManager`, `ArchiverManager`, the Doxia managers, Wagon).
`loadV4Mojo` still builds a standalone injector | #13326 and its fix #13327 are
closed. The direction is the opposite one: #13989 prepares build extensions for
a Maven 5 without Sisu |
| `Project` has no resolved-artifact view and no project references | #13460
puts resolved dependencies and attached artifacts on `Project`; #13463 defines
the project graph |
| Mojo configuration cannot be read without running the mojo | #13518 |
| No forked-lifecycle API; `@Execute(phase = "none")` crashes the descriptor
generator | #13762 deprecates `@Execute` and `aggregator` in favour of `@After`
and the `after:` phases; #13763 already maps `aggregator` in the concurrent
builder; the migration guide is #13764 |
| A plugin or extension cannot ask for a core package in its realm, or share
types with another plugin | #13223 |
| No API to start a process; maven-shared-utils `JavaTool` reaches the
toolchain by reflection and silently runs the Maven JDK on Maven 4 | #13895 |
| `org.apache.maven.api.di.MojoExecutionScoped` is unusable, and the mojo
execution scope does not reach threads a plugin starts | #13839, #13827 |
#### Open, no issue found
Rechecked in the code on both branches, unchanged.
| Gap | Hit in |
|---|---|
| No settings encryption or decryption API for a plugin | release, gpg,
jarsigner |
| No original (pre-interpolation) model on `Project` | release, enforcer |
| No metadata resolution service (`master` has a `RepositoryMetadata` type
and repository events, but nothing resolves metadata); `RemoteRepository` has
no policies; no artifact-descriptor service, so relocation is re-implemented |
archetype, resolver-ant-tasks, dependency, doap |
| `Transport` has no existence check | doap |
| `Session.getProject` returns nothing for a project without a base
directory, so `Project.getParent()` is empty for a parent from a repository and
`ProjectBuilder` returns an empty result for a `Source`. This is also half of
what blocks maven-project-info-reports-plugin | site, doap, invoker,
project-info-reports |
| `JavaPathType` classifies each dependency alone; `addOutputDirectory` is
still marked as not called | jmod |
| Mojo expressions resolve objects under `session.`, `project.`, `mojo.` and
`settings.` only: no `${plugin.*}` | surefire, scm-publish, changelog |
| `ToolchainFactory` is not a `Service`, so a plugin cannot inject one to
turn a `ToolchainModel` into a `Toolchain` | toolchains |
| `DependencyCoordinatesFactory.create(Session, model.Dependency)` drops
scope, optional and exclusions | shade |
#### Not rechecked
Stated at rc-7 and not looked at again; each needs a reproducer before it is
acted on.
- Resolution ignores `includesDependencies` of `war`, `ear` and `rar`, and
lists an artifact reached by several paths only under its nearest parent (ear).
Doubtful as worded: `FatArtifactTraverser` in `maven-impl` read that property
at rc-7 already.
- No timestamped snapshot version on a resolved artifact (ear).
- `Session.withLocalRepository` cannot override the split local repository
layout; no settings merge; no view of the plugin's own artifacts (invoker).
- No remote-layout service (doap).
- Resolved dependencies come level by level rather than in tree order
(dependency).
- No version resolution for plugins, report plugins and extensions
(release). `VersionResolver` existed at rc-7 and takes any artifact
coordinates, so what was missing is narrower than stated.
- No way to configure conflict resolution or scope selection for a verbose
collection (dependency-tree). `DependencyResolverRequest.getVerbose()` existed
at rc-7.
- A `ToolchainFactory` contributed by an extension is found only through the
Sisu index (toolchains).
- No factory for `Dependency`, `Type` or `Version` without a `Session`
(dependency-tree, mapping, surefire).
- Configuration cannot populate model types, and the strict reader rejects
`<reports>` and plugin `<goals>` (surefire, archetype).
- A plugin cannot replace the project's POM file (shade). #13543 changed how
an explicitly set artifact path is honoured, and apache/maven-shade-plugin#864
is open for the conflict with the consumer POM.
- A model without `<name>` gives a null name where Maven 3 fell back to the
artifactId (site). The fix belongs in doxia-sitetools.
#### Withdrawn
These were listed as API gaps at rc-7 and should not have been.
| Claim | Correction |
|---|---|
| `Session` has no build start time | `ProtoSession.getStartTime()` existed
at rc-7, and `Session` extends `ProtoSession` |
| No public test fixtures | `maven-testing` shipped `ProjectStub`,
`SessionMock`, `MojoExtension` and `@InjectMojo` at rc-7. Defects found in it
later are fixed (#13810 to #13813, #13928) |
| No `ArtifactHandler` equivalent | `Type` carries the id, language,
extension, classifier, `includesDependencies` and path types. What disappeared
are the reflective file-name tokens of maven-mapping, which is a property of
that library |
| The mojo-descriptor model lacks `threadSafe`, `instantiationStrategy`,
`executionStrategy`, `requiresReports` and requirements | They are in
`plugin.mdo`, for descriptor versions 1.0.0 and 1.1.0; version 2.0.0 does not
have them. The consequence is narrower than stated: maven-plugin-tools cannot
use the API model as its internal model for Maven 3 descriptors |
| Model builders do not clear a value set to `null` | How the generated
builders work: `null` keeps the value of the base object;
`Model.newBuilder(model, true)` or `withParent(null)` clears it. A trap, not a
gap |
| A bare `@Named` is the empty key, not `default` | A difference from Sisu
to document for plugin authors, not a defect |
| `Session.resolveArtifact` no longer fetches the POM or follows relocation
| It is a shortcut for `ArtifactResolver.resolve`. The Maven 3 code read the
artifact descriptor, and the gap is the missing descriptor service, listed
above |
| No path from `Session` or `Project` to `MavenProject` or
`RepositorySystemSession` | #13460 keeps the Maven 3 types for Maven 3 plugins
as wrappers; a Maven 4 mojo is not meant to get them |
### In estate tooling and libraries
| Gap | State on 2026-11-14 |
|---|---|
| `ScmManager`, the Doxia parser managers and a `CompilerManager` can be
built only through Sisu | The ServiceLoader factories were dropped
(apache/maven-scm#1418, apache/maven-doxia#1110,
codehaus-plexus/plexus-compiler#524) because #13326 was to make them
unnecessary. #13326 is closed, so the question is open again; see #13989. For
Doxia, apache/maven-doxia-sitetools#736 proposes passing parsers their context
instead of injecting Maven objects |
| plexus-archiver archivers created without a container fail when unpacking
| codehaus-plexus/plexus-archiver#500 is merged on its `master`
(5.0.0-SNAPSHOT); 4.15.0 does not contain it |
| plexus-velocity `VelocityComponent` in maven-archetype |
apache/maven-archetype#1044, merged |
| Report mojos: maven-site-plugin 3.x accepts only Maven 3 mojos as reports,
and plugin-tools writes `<requirements>` inherited from `AbstractMavenReport`
into a 2.0.0 descriptor, which Maven rejects for every goal of the plugin |
Unchanged. Reporting still has to move as a chain, and the chain waits for
#13518 |
| `<proc>none</proc>` in the parent POMs: the Maven DI index is written by
hand | Not rechecked |
| Dependency-reduced POM of a shaded build rejected by Maven 4 |
apache/maven-shade-plugin#813, closed as completed |
| spotless-maven-plugin `@Component` warning on Maven 4 |
diffplug/spotless#3122, released in 3.10.4 |
### Findings, revised
- **Timing.** #13460 keeps `MavenProject`, `MavenSession`, `AbstractMojo`
and the Maven 3 model as supported wrappers until Maven 5. A Maven 3 API plugin
keeps working on Maven 4, so a port buys a plugin nothing until it needs
something only the Maven 4 API offers.
- **Branch.** Most of what closed since rc-7 closed on `master` only, so a
port against 4.0.x re-implements what 4.2 provides. But `master` is moving too:
every `getXxx()` accessor of `Project` and of the other value types is
deprecated for removal in 4.2 in favour of noun-style accessors (#13036,
#13830), and each port made at rc-7 uses the old ones.
- **Compatibility.** A ported mojo still cannot run on Maven 3: the `Mojo`
contract and the injector differ. The reverse works for single services: #13919
put the Maven 4 `MessageBuilderFactory` into `maven-3.10.x`, so one plugin
binary injects it on 3.10 and 4 (#13917; no 3.9 backport is merged). That is
cheaper than a second line per plugin.
- **Reporting.** Still the largest blocker. doxia-sitetools,
maven-site-plugin, reporting-impl and reporting-exec must move together, and
the site plugin needs a configured report instance (#13518). Until then every
report goal stays on the Maven 3 API; the non-report goals of the same plugins
ported.
- **Sisu libraries.** maven-scm, plexus-archiver, Doxia and Wagon are Sisu
components. With #13326 closed and #13989 open, a port either waits for those
libraries or builds their components by hand, as the maven-scm-publish-plugin
port did.
- **Redesigns.** A port is rarely a type swap. The immutable model forced
redesigns (maven-release edits the POM as a DOM), and three enforcer rules were
removed rather than silently weakened: `requireUpperBoundDeps`,
`banDynamicVersions` and `requireProfileIdsExist`. On `master` the first has
the pre-managed version it lacked and the third has
`buildInvocation().activeProfiles()`; `banDynamicVersions` still has no
declared version constraint on `Node`. None was re-tried.
- **Scope.** Not every component should adopt Maven DI. indexer-core is used
outside Maven; dropping its Maven dependency serves it better than a port.
- **Tests.** Green tests do not prove a port. A `@Resolution` field that
stayed null passed every maven-rar-plugin test until an IT with real
dependencies was added, and maven-shade-plugin stayed green while publishing
the original POM instead of the reduced one.
- **Maven 3 lines.** What landed is #13309: 33 changes on the 3.x lines (23
bugs and cleanups, 10 deprecations and seams). The rest were dropped with this
study.
### Filed from this work
| Item | Outcome |
|---|---|
| #13305 `XmlNode` parameters lose attributes | closed as not planned; fixed
on `master` by #13636 |
| #13306 `PackagingProvider` ignored | fixed on both branches; issue still
open |
| #13307 plugin dependencies throw on a cached realm | closed as not
planned; fixed on both branches by #13312 |
| #13326 Sisu components in Maven 4 API mojos | closed with #13327 and
#13328: the fix was proven only with a test-side import of `javax.inject` |
| #13309 simplifications for the 3.x lines | done, 33 changes;
apache/maven-toolchains-plugin#196 was the last |
| #12709 minimum Maven baseline | closed as not planned; #13748 (raise the
plugin prerequisite to Maven 3.9.0) is closed as completed |
| apache/maven-plugin-tools#1229 mojo constructor injection | open |
| apache/maven-doxia#1111 `MarkdownHtmlParser` registered through a bare
`@Named` | closed |
| apache/maven-shared-resources#87, apache/maven-archiver#416,
apache/maven-filtering#411, apache/maven-archetype#1044 | merged |
| #13895 process execution service, #13917 Maven 4 `MessageBuilderFactory`
on Maven 3, #13827 mojo execution scope and plugin threads | opened later from
the same line of work; open |
### Components
Results at rc-7 on 2026-09-30, not re-run. Counts are `src/main` files
importing the Maven 3 API on the default branch at that date, excluding a
plugin's own `org.apache.maven.plugins.*` packages; for the shared components
the count is imports. For repositories that hold both a library and a plugin
(surefire, release, enforcer, plugin-tools, archetype, scm, jxr, wrapper), only
the library modules were counted and ported.
| Uses the Maven 3 API | of which ported | partial | blocked | Uses no Maven
API | Already on the Maven 4 API |
|---|---|---|---|---|---|
| 45 | 22 | 19 | 4 | 16 | 12 |
#### Uses the Maven 3 API
| Component | Maven 3 API use | Study PR | Result at rc-7 |
|---|---|---|---|
| maven-acr-plugin | 1 | | ported, green locally (4 ITs); `app-client`
packaging still registered through Plexus `components.xml`: rc-7 ignores
`PackagingProvider` |
| maven-antrun-plugin | 7 | | ported, green locally (4 unit, 29 ITs); Ant
reference `maven.project` is now the v4 `Project`, `maven.project.helper`
removed |
| maven-archetype | archetype-common 11 | | partial: archetype-common
ported; archetype plugin excluded, does not compile; remote catalog loses cache
and update policy |
| maven-artifact-plugin | 11 | | partial: 25 unit tests; ITs 13 → 12 passed
(`buildinfo-dir`: a `pom` project has no main artifact); `check-buildplan`
approximated with no execution-plan service; `reproducible-central` report
blocked by the reporting chain |
| maven-assembly-plugin | 21 | | ported, green locally (271 unit, 156 ITs;
the one failing IT is excluded from `run-its` by the POM); needs an unreleased
plexus-archiver: its archivers cannot unpack without a container |
| maven-build-cache-extension | 31 | apache/maven-build-cache-extension#544,
closed | blocked: no SPI to skip or replace a mojo execution (now #13987); no
code change |
| maven-changelog-plugin | 3 | | blocked: compiles, but maven-site-plugin
3.x cannot run a v4 report mojo (`Cannot cast ChangeLogReportFactory to
org.apache.maven.plugin.Mojo`); ITs 4 of 4 → 0 of 4 |
| maven-changes-plugin | 28 | | partial: the four non-report goals ported
(54 unit tests, 16 ITs incl. 11 new); report goals excluded |
| maven-checkstyle-plugin | 8 | | partial: `check` ported (16 unit, 30 ITs;
4 ITs no longer run the report first); report goals blocked, 19 report ITs
excluded; plexus-resources built without Sisu |
| maven-common-artifact-filters | 16 |
apache/maven-common-artifact-filters#130, closed | ported, one feature removed
(`actTransitively`) |
| maven-dependency-analyzer | 14 | apache/maven-dependency-analyzer#305,
closed | ported |
| maven-dependency-plugin | 75 | | partial: 25 of 29 goals ported (174 unit
tests; about 265 Maven 3 harness tests excluded, not deleted); `add`, `remove`,
`list-repositories`, `analyze-report` have no route; `tree -Dverbose` loses
conflict data |
| maven-dependency-tree | 12 | apache/maven-dependency-tree#149, closed |
ported, verbose detail reduced; retirement proposed in
apache/maven-dependency-tree#150, closed as not planned |
| maven-doap-plugin | 3 | | ported, green locally (15 unit, 4 ITs); five
behavioural approximations: repository policies, metadata, existence checks |
| maven-doxia-sitetools | 5 (integration-tools, site-renderer) |
apache/maven-doxia-sitetools#701, closed | ported; usable only at Maven 4
runtime |
| maven-ear-plugin | 20 | | partial: 49 unit tests, 103 `EarMojoIT` cases
and 17 of 18 ITs pass; `skinny-wars-timestamp` fails (no timestamped snapshot
version); `includesDependencies` ignored by the resolver |
| maven-ejb-plugin | 1 | | ported, green locally (36 unit, 9 ITs); needs
`sisu.plexus` at compile scope for the legacy `BuildContext`, as
maven-resources-plugin does |
| maven-enforcer | enforcer-rules 38, enforcer-api 2, enforcer-extension 1 |
| partial: api and rules ported (347 tests, 0 failures); 3 rules removed for
lack of API (`requireUpperBoundDeps`, `banDynamicVersions`,
`requireProfileIdsExist`); plugin and extension excluded |
| maven-gpg-plugin | 9 | | partial: green locally (13 ITs + 4 Bouncy Castle
ITs; `gpg` signer ITs not runnable here); encrypted `{...}` passphrases have no
API route and now fail explicitly |
| maven-help-plugin | 12 | | ported, green locally (61 unit, 36 ITs);
`describe` prefix lookup and `evaluate` rebuilt without a plugin manager or
expression evaluator; `effective-pom` properties now sorted |
| maven-indexer | indexer-core 3 | | partial: indexer-core ported (model
only); indexer-cli and search-backend-indexer still wired through Sisu and fail
at runtime |
| maven-invoker-plugin | 18 | | partial: 67 unit tests; 70 of 71 ITs run
pass (22 not run); `MINVOKER-377` fails because an alternate local repository
cannot override the split layout; report goal blocked by the reporting chain |
| maven-jarsigner-plugin | 3 | | ported, green locally (52 unit, 9 ITs);
settings decryption rebuilt from plexus-sec-dispatcher internals |
| maven-javadoc-plugin | 24 | | partial: every goal runs directly (75 unit
tests; ITs 79 → 75 passed, the 4 new failures are `mvn site` runs); as a site
report blocked by the reporting chain |
| maven-jdeprscan-plugin | 5 | | ported, green locally (6 unit, 6 ITs) |
| maven-jdeps-plugin | 3 | | ported, green locally (11 unit, 7 ITs);
`@Resolution` fields stay null because plugin-tools writes no `<resolutions>` |
| maven-jlink-plugin | 5 | | ported, green locally (17 unit, 28 ITs);
module path now from `DependencyResolver`, `LocationManager` dropped |
| maven-jmod-plugin | 5 | | ported, green locally (18 ITs);
main-module-aware module path still from plexus-java `LocationManager` |
| maven-mapping | 1 | apache/maven-mapping#77, closed | ported; reflective
file-name tokens lost |
| maven-plugin-tools | tools-api 13, annotations 4, generators 3 | |
partial: all but the descriptor model ported; maven-plugin-plugin and
plugin-report excluded, do not compile |
| maven-pmd-plugin | 26 | | partial: check goals ported (20 unit, 5 new
ITs); report goals blocked; `check` depended on the report only through
`@Execute`, now removed |
| maven-project-info-reports-plugin | 26 | | blocked: every goal is a
report; `ProjectBuilder` cannot build a project from a repository artifact, and
conflict data exists only as text |
| maven-rar-plugin | 4 | | ported, green locally (4 ITs, one new covering
dependencies); `rar` packaging still registered through Maven 3 components |
| maven-release | release-manager 59, release-api 7, oddeven-policy 1 | |
partial: libraries ported (791 tests, 0 failures); immutable model forced a
DOM-editing redesign; maven-release-plugin excluded, does not compile |
| maven-remote-resources-plugin | 8 | | ported, green locally (11 unit, 9 +
7 ITs); supplemental-model merging reduced; a project resource can no longer
exclude a bundle resource |
| maven-reporting-exec | 21 | apache/maven-reporting-exec#167, closed |
partial: public API ported, implementation stays on maven-core; ITs 5 of 5 → 0
of 5 |
| maven-reporting-impl | 8 | apache/maven-reporting-impl#254, closed |
blocked: compiles but cannot render; ITs 6 of 6 → 1 of 6 |
| maven-resolver-ant-tasks | 10 | | partial: model and settings ported;
relies on internal `ApiRunner` for a `Session` outside Maven |
| maven-scm-publish-plugin | 2 | | ported, green locally (5 ITs);
`ScmManager` built from the Sisu index by hand, maven-scm has no non-Sisu
factory |
| maven-scripting-plugin | 4 | | ported, green locally (5 ITs); script
binding `project` is now the v4 `Project` |
| maven-shade-plugin | 10 | | partial: green locally (72 unit, 85 ITs), but
the dependency-reduced POM can no longer become the published POM (the original
is installed); transformer SPI unchanged, `Shader` SPI changes |
| maven-shared-jar | 4 | apache/maven-shared-jar#182, closed | ported |
| maven-site-plugin | 24 | | partial: 10 goals run (deploy, stage,
effective-site, attach-descriptor fully; site, jar, run without reports); 40 of
62 ITs, the other 22 lose report pages; reports need a plugin-manager API |
| maven-surefire | maven-surefire-common 8; the forked-JVM modules use none
| | partial: maven-surefire-common ported; it holds the mojo base class, so
surefire and failsafe plugins cannot move separately |
| maven-toolchains-plugin | 9 | | ported, green locally (8 ITs); an
extension's toolchain factory is found only through the Sisu index |
#### Uses no Maven API
<details>
<summary>16 components</summary>
These use no import from Maven core, model, plugin or artifact packages and
no `org.apache.maven:*` dependency (Doxia is not Maven API). They work on Maven
4 as they are; there is nothing to port.
| Component | Study PR | Result at rc-7 |
|---|---|---|
| maven-archetypes | | green locally, 18 archetype builds; only archetype
templates use the Maven API |
| maven-doxia | apache/maven-doxia#1109 | CI-only PR closed unmerged |
| maven-doxia-converter | apache/maven-doxia-converter#165 | CI-only PR
closed unmerged |
| maven-executor | | green locally, 62 tests |
| maven-file-management | apache/maven-file-management#119 | CI-only PR
closed unmerged |
| maven-fluido-skin | apache/maven-fluido-skin#351 | CI-only PR closed
unmerged |
| maven-invoker | apache/maven-invoker#189 | CI-only PR closed unmerged |
| maven-jarsigner | apache/maven-jarsigner#117 | CI-only PR closed unmerged |
| maven-jxr | | only maven-jxr-plugin uses the Maven API (34 tests green on
Maven 4) |
| maven-reporting-api | apache/maven-reporting-api#88 | CI-only PR closed
unmerged |
| maven-scm | | green locally, 340 tests; only maven-scm-plugin uses the
Maven API |
| maven-script-interpreter | apache/maven-script-interpreter#223 | CI-only
PR closed unmerged |
| maven-shared-resources | apache/maven-shared-resources#89 | CI-only PR
closed unmerged |
| maven-shared-utils | apache/maven-shared-utils#442 | CI-only PR closed
unmerged |
| maven-wagon | | green locally, 1035 tests |
| maven-wrapper | | green locally, 34 tests; only maven-wrapper-plugin uses
the Maven API |
</details>
#### Already on the Maven 4 API
<details>
<summary>12 components</summary>
- maven-archiver and maven-filtering
- maven-xinclude-extension
- maven-mvnd (`maven.version` is now 4.0.0-rc-7)
- maven-clean-plugin, maven-compiler-plugin, maven-deploy-plugin,
maven-install-plugin, maven-jar-plugin, maven-resources-plugin and
maven-source-plugin on master, each with a `-3.x` maintenance branch
- maven-war-plugin on its `4.0.x` branch (master is 3.x)
</details>
The 2022 `mvn4` prototype branches, written against an earlier API, were
deleted (61 branches).
Out of scope at the time: maven (core), maven-integration-testing and
maven-resolver (core or below it); maven-verifier (superseded by
maven-executor); maven-shared-incremental and maven-shared-io (retired);
maven-doxia-linkcheck and maven-default-skin (archived); maven-plugin-testing
(its master was empty); parent POMs, maven-apache-resources,
maven-gh-actions-shared, maven-site, maven-sources and maven-dist-tool (no
library code).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]