I've taken an approach which separates parents and aggregates. I've put
all my parents into one eclipse project, each with a folder naming the
parent, and in that folder, a pom.xml; this is of course a flat
structure. These I then mvn install into my local repo, and/or
deploy. I'm following the
Hy List,
lets assume i have 3 Projects:
xx.yy.app.parent
xx.yy.app.module1
xx.yy.app.module2
.parent is Parent of both modules
--- cut ---
parent
artifactIdxx.yy.app.parent/artifactId
groupIdxx.yy.app/groupId
version1.0.0-SNAPSHOT/version
/parent
modelVersion4.0.0/modelVersion
Am 27.04.2010 09:28, schrieb Robert Einsle:
Hy List,
lets assume i have 3 Projects:
xx.yy.app.parent
xx.yy.app.module1
xx.yy.app.module2
.parent is Parent of both modules
Hi,
even though maven 2 supports it - kind of, I really suggest to have any
aggregation and parent definition in the
You need to add a relativePath for parent elements. Its mandatory in
Maven 3.
Add those and your builds should work.
And you can always see other issues about compatibility by googling.
Subir
-Original Message-
From: Robert Einsle [mailto:rob...@einsle.de]
Sent: Tuesday, April 27, 2010
