Actually, here's the answer to my own question:
<profiles>
<!-- profile for executing all tests as well -->
<profile>
<id>tests</id>
<modules>
<module>xmlctf-framework</module>
<module>maven-plugins</module>
<!-- Joachim: the tests are not yet running when
started using mvn install in super project
<module>xmlctf</module>
-->
<!-- Joachim: cpactf is not yet successfully executeable..
<module>cpactf</module>
-->
<!-- Joachim: cpaptf are performance tests - nothing
for every time execution
<module>cpaptf</module>
-->
<!-- Joachim: examples not yet successfully executeable..
<module>cpaptf</module>
-->
</modules>
</profile>
</profiles>
A profile named 'tests' that adds all testing-related modules to the
parent POM only if the profile is actually activated. This can be done
issuing ...
> mvn test -P tests
from the root directory.
Enjoy
Werner
Werner Guttmann wrote:
Reinahrd,
can I use a profile to add additional modules as well ? 'Cause as
Joachim said, you'd want modules such as cpactf et alias to be included
during running tests, but not during deployment.
Werner
Reinhard Poetz wrote:
Joachim Grüneis wrote:
As a developer I want to have as many modules within as possible -
because when I start 'mvn install' on the super project I want all
tests run! Only by this process I can be assured that my
modifications are valid for all of Castor... I think we should have
another way to suppress things from being deployed...
I usually use Maven profiles. The default build only contains the
things that you want to deploy. Into the profiles goes everything
else. So building Castor can be done by 'mvn install' and if you also
want to execute the performance tests, you can do this by 'mvn install
-P perf-tests'.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
