File it in JIRA, sounds reasonable. Though in this specific case, I
would expect that outputDirectory shouldn't default to anything, but
still be required (and configured via the lifecycle.xml file). That way
the user could call it standalone and pass it a directory. I think it is
good to make individual mojos generally useful as much as possible.
- Brett
Vincent Massol wrote:
-----Original Message-----
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: samedi 25 juin 2005 03:16
To: Maven Developers List
Subject: Re: [m2] How do I prevent a goal from being called?
On Fri, 2005-06-24 at 10:03 +0200, Vincent Massol wrote:
Hi,
I have a Mojo that is called by another one and I'd like to prevent the
called Mojo from being invoked directly by the user. Is there a tag for
this?
The use case is the clover plugin. The clover:check goal spawns a new
lifecycle that calls the clover:instrument goal. The spawned lifeycle
defines a new output dir. If users call directly the clover:instrument
goal
the generated sources will go in the main output dir and the generated
will
then be compiled by any compiler goal. I'd like to avoid this by
preventing
users from calling clover:instrument.
So a mechanism where we could state a goal can only participate as part
of a lifecycle? Basically make the goal non-visible for direct use?
Yep, exactly.
Thanks
-Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
