Complete Migration from Plexus to Eclipse Sisu

[sparsick]

A long time ago, Maven switched from Plexus to Eclipse Sisu.

My understanding is that it is a core functionality because it is the dependency injection framework (I hope, I'm correct).

Ideas:

• Let's ensure that plexus is not used in core and plugins, that are managed by Apache (if not already done)
• Support for 3rd party plugins (tutorial, rewrite recipe etc.)
• Clean up documentation where Plexus is mentioned.
• Migration of elder plugin outside Apache (for example Mojohaus)

[rmannibucau]

+1, the plugins (and extensions) must use v4 api now which totally hides the maven "core" internal IoC. Work started but is not yet complete.

[khmarbaise]

Technically Maven can use https://maven.apache.org/maven-jsr330.html (JSR 330) which means using JSR330 compliant annotations (https://github.com/eclipse/sisu.plexus/wiki/Plexus-to-JSR330) should be documented better and examples should be created/updated accordingly.

[rmannibucau]

Hmm, technically JSR330 does not define any sufficient behavior and is already legacy so hope we don't promote it at all for external use since we would ultimately 1. defeat one of the best mvn4 purpose and 2. just expose Guice and not JSR330 (the API is just 10% of the contract there).

[khmarbaise]

An plain Guice would be also an option... Yes there are a number of limitations that's true...

[gnodet]

I would not invest time to migrate to sisu. I would rather migrate the remaining v3 services to the DI framework API and implementation.

[gnodet]

FTR, the current DI framework has a visibility problem, see https://issues.apache.org/jira/browse/MNG-8139