Mark,
it's <activeByDefault> and not <activatedByDefault>
Emmanuel
Mark Hobson wrote:
Just trying this on the latest m2 and get:
Error: 'Unrecognised tag: 'activatedByDefault' (position: START_TAG
seen ...<activation>\r\n\t\t\t\t<activatedByDefault>
... @60:25) '
I have:
<project>
...
<profiles>
<profile>
<id>default</id>
<activation>
<activatedByDefault>true</activatedByDefault>
</activation>
...
</profile>
</profiles>
...
</project>
Not sure what the parser validates against (XSD, model?) but does it
need updating for this?
Cheers,
Mark
On 13/09/05, John Casey (JIRA) <[EMAIL PROTECTED]> wrote:
[ http://jira.codehaus.org/browse/MNG-835?page=all ]
John Casey closed MNG-835:
--------------------------
Resolution: Fixed
Fix Version: (was: 2.0-beta-2)
2.0-beta-1
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-1
Original Estimate: 3 hours
Time Spent: 3 hours
Remaining: 0 minutes
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
