maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian E. Fox" <bri...@reply.infinity.nu>
Subject RE: [discuss] add validate/initialize to site lifecycle
Date Wed, 04 Apr 2007 02:49:03 GMT
That's right. What I'm asking for though is a phase that is common
between both lifecycles so a plugin can be bound to run in both cases
without having to duplicate executions. In the case of enforcer, it
would be the default as specified in the mojo annotation.

-----Original Message-----
From: Franz Allan Valencia See [mailto:franz.see@gmail.com] 
Sent: Tuesday, April 03, 2007 10:41 PM
To: Maven Developers List
Subject: Re: [discuss] add validate/initialize to site lifecycle

I think pre-site is the site lifecycle's "initialize" phase ( as is
pre-clean for the clean lifecycle ).

On 4/3/07, Brian E. Fox <brianf@reply.infinity.nu> wrote:
>
> As Jerome pointed out earlier today on the enforcer thread, it would
be
> nice to be able to bind some plugins like the enforcer to a phase that
> affects both default and site. After all, if you don't want to support
> some Maven/Jdk/Os/other version, chances are that applies to sites and
> reports as well (especially since they might fork to compile aka
> cobertura etc).
>
>
>
> Is there any drawback to adding one or both of those to the lifecycle,
> and if so, what about a new one for both? (although I suspect this is
> what validate was really intended for)
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Mime
View raw message