maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Max Bowsher <ma...@ukf.net>
Subject Re: [discuss] add validate/initialize to site lifecycle
Date Wed, 04 Apr 2007 13:24:45 GMT
Brian E. Fox 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)

Maven seems to require that phases be globally unique across all
lifecycles. DefaultLifecycleExecutor specifically tests for this and
throws a LifecycleExecutionException if a violation is detected.

Max.



Mime
View raw message