Hi John,
> -----Original Message-----
> From: John Casey (JIRA) [mailto:[EMAIL PROTECTED]
> Sent: lundi 12 septembre 2005 22:23
> To: [email protected]
> Subject: [jira] Commented: (MNG-835) Default profile in pom.xml not
> activated
[snip]
> <always/> doesn't really have the same semantics, though...does it? When
> you specify <always/> it would seem to indicate to me that this profile
> will always be in effect to some measure. When you set a default profile,
> it means that profile will be activated if no others are, doesn't it?
>
> What I really want to get at here is whether it makes sense to have a
> default profile, particularly now that you can specify:
>
> <project>
> ...
> <properties>
> <someproperty>somevalue</someproperty>
> </properties>
> </project>
>
> In the case of a default value for a property, this should suffice.
Right. I wasn't sure how you specified what you called pom-level properties.
That should be enough indeed for default property values. So the following
will work right?
<build>
<plugins>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<systemProperties combine.children="append">
<property>
<name>cargo.containers</name>
<value>${cargo.containers}</value>
</property>
</systemProperties>
</configuration>
</plugin>
</plugins>
</build>
<properties>
<cargo.containers>resin3x, orion2x,...</cargo.containers>
</properties>
And if the cargo.containers property is defined in a profile it will
override the default value?
> Beyond
> that, having a default profile in settings.xml doesn't really make sense,
> since you can activate a profile using <activeProfiles/> in the
> settings.xml itself.
true
> If you're using a profiles.xml, there may be a time when you need
> <always/> or <default/> or somesuch...I'll investigate adding both.
Yep that's the only remaining point I have.
Thanks
-Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
