Vincent Massol wrote:
Hi Michal,
Thanks for the suggestion. Several points:
- I would prefer to use the Mojo API for now as it allows me to learn how to
use it, to flesh it out if required
- I don't have much hope that the Clover plugin will be able to be reused in
another context... It's too bound to the execution lifecycle I think.
The task itself should be though - you are just relying on the lifecycle
to get you a database. You just process the database. That's easy enough
to use elsewhere.
- If I use plexus then am I not simply replacing the maven dep by the plexus
dep (actually I'll be adding it as the maven dep will always be needed I
think). ATM, someone could reuse the Mojos that I have written. They would
simply need to provide implementations for the Maven interfaces. But again I
don't think it could be reused easily.
Yes, manually doing work Maven does for you is not a good idea.
- What about the other Mojos they're all bound to Maven too?
Some more than they need to be. Ideally it shouldn't be necessary,
unless you are doing Maven project specific things. eg. if you just need
the packaging - use ${project.packaging}, not ${project} where you later
get the packaging.
It's ok for them to depend on maven-artifact, the model or such - they
can be used outside of Maven. It's more the construction of those things
that is a bigger deal usually.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
