No, that's not the case (at least in intent). It just indicates that
the plugin contains component registrations for the core (which is
the same for <extensions>, though they are not plugins). This is
generally use for artifact type handlers.
- Brett
On 08/10/2007, at 8:18 PM, nicolas de loof wrote:
No, I'm looking for any way to get intialized before the lifecycle
starts.
Do you know how the <extensions> (boolean) element in <plugin>
differs from
<extensions> in <build> ?
From what I've read in code (but I can be wrong) only the first
plugin with
extensions=true is considered for extension. Is this what is
expected ?
Nico.
2007/10/8, Brett Porter <[EMAIL PROTECTED]>:
On 08/10/2007, at 11:36 AM, nicolas de loof wrote:
Hello,
is there any way for a plugin to get initialized before the build
lifecycle
starts ?
does maven honor
org.codehaus.plexus.personality.plexus.lifecycle.phase.Initializable
f
or
plugins ?
yes, but this won't cause it to be instantiated before the build
lifecycle - it is initialized on first use IIRC. You might be able to
use the validate lifecycle phase to achieve what you need though?
- Brett
Nico.
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
