Is anyone using these extra profiles:
<snip>
<profile>
<id>all</id>
<activation>
<property>
<name>all</name>
</property>
</activation>
<modules>
<module>${all}</module>
</modules>
</profile>
<profile>
<id>singlemodule</id>
<activation>
<property>
<name>module</name>
</property>
</activation>
<modules>
<module>modules/${module}</module>
</modules>
</profile>
<profile>
<id>singleplugin</id>
<activation>
<property>
<name>plugin</name>
</property>
</activation>
<modules>
<module>m2-plugins/${plugin}</module>
</modules>
</profile>
<profile>
<id>singleapp</id>
<activation>
<property>
<name>application</name>
</property>
</activation>
<modules>
<module>applications/${application}</module>
</modules>
</profile>
</snip>
Most of these can be replaced by a simple:
cd path
mvn
To help keep the pom simple, I recommend that these extra profiles be
removed. These profiles will make less and less sense as the build
is restructured into more specific component hierarchies.
If a developer wants to use this style of connivence then it is easy
enough to drop this into a local profiles.xml next to pom.xml.
--jason
