Ok thanks a lot for your help! I'll move on with this solution.
I'd still be interested in the versions:use-latest-snapshots call, though.
-Ursprüngliche Nachricht-
Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im Auftrag
von Anders Hammar
Gesendet: Dienstag, 16. Febru
I think you misunderstood me. I won't put dependency depmgmt-x into the parent
of Z(what would be mnet-parent). I will put it into component Z.
-Ursprüngliche Nachricht-
Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im Auftrag
von Anders Hammar
Gesendet: Dienstag, 16.
Ok I agree with your solution, it will make it less complicated and more
maintainable.
Ok if I go ahead and add depmgmt-x:1.0.0 to the dependencyManagement section of
Z(Parent), subsystem X (with released components) is going to be properly
referenced by project Z. But what if a developer want'
Every component in a subsystem has a different version.
What do you mean with: "ONE import pom per subsystem"?
e.g. replacing depmgmt-rel-x & depmgmt-dev-x with depmgmt-x ? If so, how can I
handle different subsystem component-versions in depmgmt-x without profiles?
-Ursprüngliche Nachricht--
Thanks a lot for your fast response!
The file can be found here: http://www.christian-moser.ch/fx/subsystems.pdf
Yes im using depmgmt poms with import. Every of the five subsystems can be used
by any project(in diagram project Z) with different versions, this would mean I
had to set 5 project de
