If the profile affects things like dependencies, then having
script-like behavior becomes pretty troublesome for tools attempting
to analyze the pom/tree outside of the dev environment. For example a
repo manager.
On Wed, Oct 20, 2010 at 12:01 PM, Jason van Zyl wrote:
> It's a matter of defining
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, 2
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
wrote:
> On 10/20/10 11:47 AM, Jason van Zyl wrote:
>> I think we just need to make it easier
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...@mave
On Oct 20, 2010, at 11:41 AM, Vincent Siveton wrote:
> And what about profile activation? I mean do you think it could be a
> good idea to add scripting in the activation part?
No, I think that could be remedied without having to resort to scripting. Once
you open the door it just gets opened w
And what about profile activation? I mean do you think it could be a
good idea to add scripting in the activation part?
I know that pom.xml is not like ant and other, but in some cases,
using antrun to do basic validation could be overkill IMHO
Cheers
Vincent
2010/10/20 Jason van Zyl :
>
> On Oc
On Oct 20, 2010, at 10:06 AM, Vincent Siveton wrote:
> Hi guys,
>
> I don't remember if this topic was already discussed in the past.
>
> Some of our plugins have a boolean parameter. In my case, I
> want to use expression to init this boolean, i.e.
> ${project.packaging} != "pom" or similar.
