Any idea?
The main reason why we want to do this is to be able to have different
types of projects.
Each type has different pom settings which we want to maintain in a
central place.
At the moment we have a master pom per project type which limits us in
combination with module builds as Maven doesn't support multiple
inheritance at the moment (master pom+ module parent).
That's why we want to implement profiles but don't know how to
workaround MNG-3228.
Any input highly appreciated!
Thanks
Stefan
-------- Original Message --------
Subject: Looking for a workaround for MNG-3228 (activate inherited
profile)
Date: Wed, 28 Jan 2009 08:11:34 +0100
From: Stefan Fritz <sfritz.nos...@gmx.at>
Reply-To: Maven Users List <users@maven.apache.org>
To: Maven Users List <users@maven.apache.org>
References:
<9aec5f50bd7e0f48891ae45adc56118403592...@ldnukms2.caplin.com>
<562346790901200455i39250a79vd311d152b3884...@mail.gmail.com>
<9aec5f50bd7e0f48891ae45adc56118403592...@ldnukms2.caplin.com>
Hi all,
We try to define profiles in our master pom.
When we trigger a build we want to activate a specific profile via a
property in the projects pom.
(activation via -P works fine).
But it seems we ran into the following issue:
http://jira.codehaus.org/browse/MNG-3228
Is there any workaround to be able to activate a profile (defined in a
master pom) per project?
Thanks
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
