Re: Using a parent POM plugin config in only some child modules?
Steinar Bang wrote: Tomasz Pik [EMAIL PROTECTED]: Configure plugins in profiles in parent pom and activate profiles in child poms? This won't be automatic (I do not know if there's a way to activate profile using packaging, maybe there's?) - you'll need to add avtivation to child poms but should solve problem with storing configuration in one place. Yes, I was wondering about if profiles could be triggered by packaging, and if that was a way to go...? I had the same problem and you might find some background and suggestions in this thread: http://www.nabble.com/How-to-activate-profile-for-certain-packaging--tf4243177s177.html#a12074301 However, we endet up checking for the existence of a certain directory that our homegrown deployment plugin pulls it's code in and activating the profile when that directory does exist. That has proven the most stable approach in the current situation. -Gisbert -- Gisbert Amm Softwareentwickler Infrastruktur Telefon: (0721) 91374 - 4224 Telefax: (0721) 91374 - 2740 E-Mail: [EMAIL PROTECTED] Internet: www.1und1.de 11 Internet AG Elgendorfer Strasse 57 56410 Montabaur Amtsgericht Montabaur HRB 6484 Vorstand: Ralph Dommermuth, Matthias Ehrlich, Andreas Gauger (Vorsitzender), Matthias Greve, Henning Ahlert, Norbert Lang, Achim Weiss, Robert Hoffmann, Aufsichtsratsvorsitzender: Michael Scheeren - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using a parent POM plugin config in only some child modules?
Wayne Fay [EMAIL PROTECTED]: You just need multiple parents. One top parent, then another one below it that sets the dependency plugin configs, then have your bundles inherit from it, and the other modules inherit from the top parent. That would require a project restructuring for us. We have two levels of parents. One top parent spanning all projects, and then pairs of *def and *impl bundles (the *def bundles defining the interfaces for OSGi services, and the data structures they use, and *impl creating OSGi components exposing services) with a common parent, handling common settings for the bundle pairs. To use your idea, we would have to drop the common settings layer, which would take some work. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using a parent POM plugin config in only some child modules?
On 9/26/07, Steinar Bang [EMAIL PROTECTED] wrote: Is it possible to create a plugin configuration in a top level POM with packagingpom/packaging, that will only be executed in child modules with packagingbundle/packaging (modules using the apache FELIX maven-bundle-plugin)? The use case is where I have a dependency:copy config in the POM of each bundle projects, that copies the installed bundle into an eclipse PDE target platform. I would like to move the config up to a common parent, but that causes the projects with packagingpom/packaging to be copied to the PDE target platform as well. They aren't bundles, so they won't have any effect on eclipse, but it's clutter I'd like to avoid... Configure plugins in profiles in parent pom and activate profiles in child poms? This won't be automatic (I do not know if there's a way to activate profile using packaging, maybe there's?) - you'll need to add avtivation to child poms but should solve problem with storing configuration in one place. HTH, Tomek - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using a parent POM plugin config in only some child modules?
Tomasz Pik [EMAIL PROTECTED]: Configure plugins in profiles in parent pom and activate profiles in child poms? This won't be automatic (I do not know if there's a way to activate profile using packaging, maybe there's?) - you'll need to add avtivation to child poms but should solve problem with storing configuration in one place. Yes, I was wondering about if profiles could be triggered by packaging, and if that was a way to go...? But I dread going this way, because my last incursion into profiles in 2.0.4 broke when 2.0.5 was released, and also breaks on the current 2.0.7... and has (along with another bug introduced with 2.0.5) stuck us on 2.0.4 (which is increasingly more of a problem). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using a parent POM plugin config in only some child modules?
On 9/27/07, Steinar Bang [EMAIL PROTECTED] wrote:
Tomasz Pik [EMAIL PROTECTED]:
Configure plugins in profiles in parent pom and activate profiles in
child poms? This won't be automatic (I do not know if there's a way
to activate profile using packaging, maybe there's?) - you'll need
to add avtivation to child poms but should solve problem with
storing configuration in one place.
Yes, I was wondering about if profiles could be triggered by
packaging, and if that was a way to go...?
a bit strange thing...
this do not work for me (in fact, as expected):
profile
idxxx/id
activation
property
name${pom.packaging}/name
valuewar/value
/property
/activation
this works:
profile
idxxx/id
activation
file
existssrc/main/webapp/WEB-INF/web.xml/exists
/file
/activation
so maybe you may distinguish by looking for a particular file
(dedicated MANIFEST?).
the strange thing is that this is not working:
profile
idxxx/id
activation
file
exists${basedir}/src/main/webapp/WEB-INF/web.xml/exists
/file
/activation
and I do not know why, maybe somebody knows (mvn 2.0.6).
HTH,
Regards,
Tomek
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using a parent POM plugin config in only some child modules?
You just need multiple parents. One top parent, then another one below it that sets the dependency plugin configs, then have your bundles inherit from it, and the other modules inherit from the top parent. Wayne On 9/26/07, Steinar Bang [EMAIL PROTECTED] wrote: Is it possible to create a plugin configuration in a top level POM with packagingpom/packaging, that will only be executed in child modules with packagingbundle/packaging (modules using the apache FELIX maven-bundle-plugin)? The use case is where I have a dependency:copy config in the POM of each bundle projects, that copies the installed bundle into an eclipse PDE target platform. I would like to move the config up to a common parent, but that causes the projects with packagingpom/packaging to be copied to the PDE target platform as well. They aren't bundles, so they won't have any effect on eclipse, but it's clutter I'd like to avoid... Thanx! - Steinar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
