Page History

...

• Make sure Plexus AbstractLogEnabled is not used (extended) any more: Maven since 3.x uses SLF4J API instead.
• Make sure ancient org.codehaus.plexus:plexus-container-default is NOT used as dependency IN ANY SCOPE: use Sisu Plexus Shim instead (but only in test scope) = org.eclipse.sisu:org.eclipse.sisu.plexus (currently 0.3.5, soon 1.0.0), because in general, all shared components should be migrated to JSR330, while use of Plexus Container MAY BE still needed in UTs (due to Plexus Components present in dependencies).
• Make sure components in project use JSR330 annotations and not org.codehaus.plexus:plexus-component-annotations or EVEN WORSE, the Plexus QDox Javadoc annotations.
• Drop use of Plexus Component Descriptor (META-INF/plexus/components.xml) and org.codehaus.plexus:plexus-component-metadata plugin: use org.eclipse.sisu:sisu-maven-plugin instead.
• Use JSR330 (javax.inject) consistently.
• Sisu tutorials:
  • https://eclipse.github.io/sisu.inject/
  • https://eclipse.github.io/sisu.plexus/

Maven

• ... should really drop Maven 2.x support (was it 10 years?), so maven-compat must go.

...

• ... should really make up the 10 year lag, and stop depending on maven-compat stuff. Baseline for plugins should be Maven 3.12.x 5+ line.
• We must forget the "ill fated" Maven 3.0.x line, not only due org.sonatype/org.eclipse Resolver problem (m-artifact-transfer kinda covers it), but also due it's "sealed" Plexus/Sisu implementation and ancient version. We must comprehend, that we have no resources to support 10+ years spanning compatibility. Move on.
• (to be reviewed) mark Maven core dependencies as scope=provided

Note about plugins carrying custom lifecycle mappings: while Plexus XML will work across 3.2.5-3.99 versions, converting lifecycle mapping to JSR330 is not so simple: there was a type erasure change that renders mappings in plugin between 3.2.5 and 3.3.9 broken (well, not trivial to migrate). In this case, simplest is to just "avoid" the breakage, and raise the bar on that plugin to 3.3.9+

See here:

• https://github.com/apache/maven-rar-plugin/pull/3/commits/8a23374ffd5ee9d5f92559e702b813a0b6fe6c06

• Jira
  server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key MNG-5958

Maven SCM

Maven SCM is bloated too big given our resources and contains many providers we cannot test, given they bridging for are non OSS SCMs.

Proposal: keep only those SCM providers that are OSS and not obsolete (like cvs...) in Maven project, and provide a clear path for SCM integrators . Propose to maintain their providers in their community. Proposed plan:

Phase 1

• mark as @Deprecated all except following providers: git (gitexe, jgit), svn (svnexe), mercurial

  • maven-scm-provider-accurev

  • maven-scm-provider-bazaar
  • maven-scm-provider-clearcase
  • maven-scm-provider-integrity
  • maven-scm-provider-jazz
  • maven-scm-provider-perforce
  • maven-scm-providers-cvs
  • maven-scm-providers-standard (skim POM)
  • maven-scm-provider-starteam
  • maven-scm-provider-synergy
  • maven-scm-provider-tfs
  • maven-scm-provider-vss
• release as-is as next minor version = 1.12.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828&version=12350600

...

• drop all deprecated modules/providers (incuding svnkit)
  • write down how to move these to a new home?
• up major version?: 2.0.0
• make it Java 8?
• provide "clear path" (documentation, repository, mini-site?) for SCM integrators (prev codebase will be still available under release tag done in phase 1)

  • Jira
    server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key SCM-1002

    prepare orphaned Git branches for each removed SCM provider with the code as it was before
• Get rid of Plexus DI

Maven Wagon

...

• release 1.7.0 (soon): DONE (Java8 + locking) https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12349416
• release 1.9.x (to be used in Maven 3.9.0+) - DONE (current 3.9.6 + 1.9.18)

Phase 2

...

• up major version (2.x)
• Drop ServiceLocator, as it currently forces us to use bad practices: create mutable components, and is just cruft (member population is "circumvented" by init method, no way for ctor injection). Anyway, anyone integrating resolver w/o guice should just manually craft the "component graph", basically all they need is a "factory pattern" w/o the half-ass DI-like cruft in SL (that forces how components are created), see

  Jira
  server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key MRESOLVER-157

• make all things proper ctor injection and final (lot of code breakage)

...

org.eclipse.aethereclipse.aetherorg.

Maven version line	Java level	Plexus XML	Sisu index	Resolver			Latest Maven release
				Java package (code)	Artifact GA (dependency)	Version
3.0.x	5	Yes	No	org.sonatype.aether	org.sonatype.aether:aether-api	1.11	3.0.5, 2013-02-19
3.1.x			5	Yes	Yes	org.eclipse.aether	org.eclipse.aether:aether-api	0.9.0.M2	3.1.1, 2013-09-17
3.2.x	6		Yes	Yes				org.eclipse.aether	org.eclipse.aether:aether-api	1.0.0.v20140518	3.2.5, 2014-12-14
3.3.x	7		Yes	Yes					org.eclipse.aether:aether-api	1.0.2.v20150114	3.3.9, 2015-11-10
3.5.x			7	Yes			Yes		org.	apache.maven.resolver:maven-resolver-api	1.1.1	3.5.4, 2018-06-21
3.6.x			7	Yes			Yes				org.eclipse.aether	org.apache.maven.resolver:maven-resolver-api	1.4.1	3.6.3, 2019-11-19
3.8.x			7	Yes			Yes				org.eclipse.aether	org.apache.maven.resolver:maven-resolver-api	1.6.3	3.8.6, 2022-06-118, ?
3.9.x ?	8		Yes	Yes			org.eclipse.aether	org.apache.maven.resolver:maven-resolver-api			1.8.x	1.9.x (1.9.18)	3.9.6, ?
4.0.x (old + new Maven API)	8?		Yes	Yes			org.eclipse.aether	org.apache.maven.resolver:maven-resolver-api			2.x2.x (compat with 1.9.x)	?
4.1.x (only Maven API)	?		Yes	Yes			org.eclipse.aether	org.apache.maven.resolver:maven-resolver-api			2.x (direct resolver access removed)	?
5.x ?	?	No ?	Yes	org.apache.maven.resolver		org.apache.maven.resolver:maven-resolver-api	3.x (direct resolver access removed)	?

Note: this table contains latest releases only and just for quick reference. For details history of Maven, go to Maven Releases History page.

...

• mark as @Deprecated all except following providers: xdoc, fml, apt, markdown, asciidoc, xhtml, xhtml5
  

  • doxia-logging-api

  • doxia-module-confluence
  • doxia-module-docbook-simple
  • doxia-module-fo
  • doxia-module-itext
  • doxia-module-latex
  • doxia-module-rtf
  • doxia-module-twiki
• release as-is as next minor version = 1.11.1 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317230&version=12350888

Phase 2 (post release)

• drop all deprecated modules/providers/classes
• up major version?
• make it Java 8?
• Get rid of Plexus DI
• Get rid of Doxia Logging

...

• mark as @Deprecated all except following renderers: site
  

  • doxia-doc-renderer

• release as-is as next minor version = 1.11.1 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320&version=12351046

Phase 2 (post release)

• drop all deprecated modules/providers/classes
• up major version?
• make it Java 8?
• Get rid of Plexus DI
• Get rid of Doxia Logging

...