Hi Adrian,
thank you for the fast response! I am using the "manifest-first"
strategy to generate the pom.xml from the eclipse-manifest.
As far as I understand the inheritance of poms I have to reference the
"parent" from the "child" (I had that already working with manually
generated poms).
I could do that, but that means I have to touch the generated pom.xml
and add the reference which I would want to avoid.
Inheritance would solve my problem if there was some way to define a
"standard parent" to inherit from e.g. in settings.xml.
regards
Moritz
On 01/07/2011 09:26 AM, Adrian Shum wrote:
Hi Moritz,
Why don't you simply make a parent pom for all your poms to inherit from?
--
Best Regards,
AdRiAN ShUM
-----Original Message-----
From: Moritz Maisel [mailto:mai...@sipgate.de]
Sent: Friday, January 07, 2011 4:00 PM
To: users@maven.apache.org
Subject: specify "<build>" section outside projects pom.xml
Hi all,
I am using maven with tycho to build osgi bundles. In my project's
pom.xml I need the following section:
<build>
<plugins>
<plugin>
<groupId>org.sonatype.tycho</groupId>
<artifactId>tycho-maven-plugin</artifactId>
<version>0.9.0</version>
<extensions>true</extensions>
</plugin>
</plugins>
</build>
I don't want to repeat that in all my projects, but would rather like to
have that specified in one single place from where it is automagically
included in all poms. I researched about putting that into settings.xml,
but had no success with that.
Any ideas?
Thanks for any help!
Moritz
--
sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf
HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois
Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391
www.sipgate.de - www.sipgate.at - www.sipgate.co.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org