The problem is that any profile with activation "activeByDefault" will be
deactivated if another profile is activated. This is a bad "feature" of Maven
IMO because it's counter-intuitive to most people. As a work around you can
explicitly activate the default profile and do something like.
| mvn -Passembly,default install -Dmaven.test.skip
|
In general I would recommend not using activeByDefault and instead using a not well
documented feature of the property activation to make a profile activeByDefault. So it
looks something like this.
| <profile>
| <id>default</id>
| <activation>
| <property>!skip.default.profile</property>
| </activation>
| <properties>
| </profile>
|
This tells maven that the profile "default" is active unless the property
"skip.default.profile" is set.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232789#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...