Hi,
a simple solution is to make such a module (sounds like an integration
test module) just the profile inside the module so the execution of the
integration tests is activated/deactivated by a profile things like
maven-failsafe-plugin or whatever...
This prevent problems with releases etc.
Kind regards
Karl-Heinz Marbaise
On 8/29/14 9:15 PM, Thomas Larsson wrote:
Thanks Karl,
This seems like the sensible thing to do, and yes, we have already
encountered the headache of keeping the submodules version number in
sync after a release :-)
Perhaps this should have been obvious. Thanks for the help anyway!
/Thomas
On Fri, Aug 29, 2014 at 8:28 PM, Karl Heinz Marbaise <[email protected]
<mailto:[email protected]>> wrote:
Hi,
>
I am trying to create an archetype with two modules, one main
and one itest.
I would like to have the itest module only active when run with
a profile.
In my original project, the root pom includes a part like this:
<profiles>
<profile>
<id>itest</id>
<modules>
<module>itest</module>
</modules>
</profile>
</profiles>
However, in the archetype-metadata.xml reference there is
nothing mentioned
about profiles.
First do never create a module which is included by a profile, cause
you will get trouble...
In particular if you do a release and afterwards doing a build and
activate the profile...
Take a deeper look
here:http://blog.soebes.de/__blog/2013/11/09/why-is-it-bad-__to-activate-slash-deactive-__modules-by-profiles-in-maven/
<http://blog.soebes.de/blog/2013/11/09/why-is-it-bad-to-activate-slash-deactive-modules-by-profiles-in-maven/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
