Hello all, thanks for all those long replies.
Ron, I would be happy to follow any good practice and to comply to the way
maven does things.
But in this particular case, I wasn't able to find anything to comply to. I am
indeed describing the usage of a parent POM, but with the exception that only
Hello Wayne,
Seems my first post was really not clear. Trying to make it simpler:
Basically, my main concern is to be able to package separately parts of the POM:
- plugin configuration and/or dependencies (previously the "type POM")
- distribution management information (previously the "deployme
Hello Ron,
I'm not sure I understand what you meant...
My problem is all about the POMs, that is, how can I share pieces of
configuration (i.e pieces of POM file) between bundles, the main problems being
that I have not a single inheritance chain (because of project specific
deployment propert
Hello all,
I'm currently working in several projects using maven 3, and I need some help
defining a new POM hierarchy to avoid POM code duplication.
My projects are composed of multiple bundles (it's OSGi based).
Each project has its own deployment and source repositories and defines a
differen
