This is not a maven mojo problem but a plugin design problem. Most
plugins, like the jar plugin and the surefire plugin, to name some,
are rather empty. The jar plugin just extracts information from the
MavenProject, giving it to maven-archiver (plexus-archiver under water),
and later updates the MavenProject with the newly created archive.
The same goes for the surefire plugin.
So you really don't want to re-use mojo's, but the functionality they
offer. And since the functionality they offer is, or should be, separated
from the mojo itself you actually want to use the libraries behind them.
So I really see no problem here, except maybe for some design issues with
some current plugins.
I don't want to hijack this thread, so if people can find the original
message for
http://www.nabble.com/MJAR-28-Advice-from-dev%3A-Mainfest.mf-Class-Path-entries-by-MavenArchiver%2C-Assembly-and-Jar-tf1908862.html#a5225318
and reply there that would be preferable.
The problem that I have at this point is the coupling between plugins
that are built on top of plugins, and in this case as you raise the
PlexuArchiver -> MavenArchiver -> Jar.
In this particular case I suspect the problem is in something lower
level and I am hesitant to make any changes without dev guidance
because the possibility of far reaching effects is too high.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
