maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Casey" <casey.joh...@gmail.com>
Subject Re: [discuss] add validate/initialize to site lifecycle
Date Wed, 04 Apr 2007 14:21:28 GMT
Max is right, if you add these phases to the site lifecycle (fine by me, I
suppose), they'll have to have different names. This is really unfortunate,
but that's the only way they can be incorporated into 2.0.x, or 2.1 (without
some redesign).

-john

On 4/4/07, Max Bowsher <maxb1@ukf.net> wrote:
>
> 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
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message