Hello Bernd,
you could think about having a multi-module pom project with an
aggregation-pom, having life cycle/configuration jar module and your
company pom. Testing would be defined in the aggregation pom. Only ugly
thing that you have to duplicate some plugin versions in the aggregate and
Sorry Bernd and everyone,
I did not see that you just outlined the solution I proposed yourself.
Regards
Mirko
--
Sent from my mobile
On Mar 1, 2014 1:11 PM, Mirko Friedenhagen mfriedenha...@gmail.com
wrote:
Hello Bernd,
you could think about having a multi-module pom project with an
Hello,
I am currently wondering what the best way would be to deploy a
company wide parent POM (with maven release plugin) but have only the
information in the parent POM which is actually about the object model
of the clients (and not the definitions for deploying and testing the
parent).
I
