[ http://jira.codehaus.org/browse/MNG-835?page=comments#action_46244 ]
John Casey commented on MNG-835:
--------------------------------
<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. 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.
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.
> Default profile in pom.xml not activated
> ----------------------------------------
>
> Key: MNG-835
> URL: http://jira.codehaus.org/browse/MNG-835
> Project: Maven 2
> Type: Bug
> Components: maven-core
> Versions: 2.0-alpha-3
> Reporter: Vincent Massol
> Assignee: John Casey
> Fix For: 2.0-beta-2
>
>
> Pasted email from mailing list explaining the problem. I've also ran "m2
> projecthelp:active-profiles" and it doesn't show the profile as active.
> ---
> Hi,
> I want to allow cargo build users to override a plugin property. I have seen
> that using a <build> element is not allowed in a settings.xml file and Brett
> has suggested I use a <properties> element instead. However I also need to
> define a default value for the property that can be overridden.
> Thus I have defined the following in my project's pom.xml:
> [...]
> <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>
> <profiles>
> <profile>
> <id>default</id>
> <properties>
> <cargo.containers>jetty4xEmbedded</cargo.containers>
> </properties>
> </profile>
> </profiles>
> </project>
> I want cargo build users to be able to create a settings.xml file with the
> following for example:
> <settings>
> <profiles>
> <profile>
> <id>user-vmassol</id>
> <properties>
> <cargo.containers>resin3x</cargo.containers>
> </properties>
> </profile>
> </profiles>
> <activeProfiles>
> <activeProfile>user-vmassol</activeProfile>
> </activeProfiles>
> </settings>
> Is that the correct way to implement my use case?
> So far, the issue I've had is that the default profile created in pom.xml is
> not used when I issue a "m2 install" command. I've read on
> http://docs.codehaus.org/display/MAVEN/Build+Profiles that naming a profile
> "default" will automatically activate it. Isn't that so?
> If not how can I activate a profile defined in pom.xml by default?
> Thanks a lot
> -Vincent
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
