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

...

• 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)

...

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

...