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
On Mon, Apr 2, 2012 at 7:55 AM, Gillet Thomas (2) <
thomas.gille...@consultant.volvo.com> wrote:
> 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 dependencie
Hi Gillet,
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 "deployment POM")
>
To me, it sounds like you are asking for multiple inh
It sounds like you are describing the usage of a parent POM.
A parent is a project specific POM that ideally carries your plug-in
versions, deployment information and code versions for all of the POMs
in the maven projects that makes up your application. Some of this is
properties and some is f
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
> 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 properties and target specific configuration).
I'm not sur
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
I read it to the end but I am not sure that I got it all.
One suggestion that we found helpful is to start to look at some of the
maven projects as utilities that are really no different from a
developers point of view than utilities that we use from Apache or
Springframework or others.
They g
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
