It's a matter of defining what is mutable in MavenProject from a plugin and lifecycle participants (which are new in Maven 3).
A profile activator would need full context, or a lifecycle participant which can hook in before the build execution occurs could mutate/activate profiles. On Oct 20, 2010, at 11:53 AM, Paul Benedict wrote: > Couldn't a maven plugin be written to pre-process the POM structure > and do the evaluation? I would rather see that than ever making it > part of Maven core. > > On Wed, Oct 20, 2010 at 10:50 AM, Justin Edelson > <justinedel...@gmail.com> wrote: >> On 10/20/10 11:47 AM, Jason van Zyl wrote: >>> I think we just need to make it easier to create and add profile activators. >> +1 >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl --------------------------------------------------------- We know what we are, but know not what we may be. -- Shakespeare
