5:08 p.m.
Hi,
Following some guidelines from "Mvn the definitive guide" I've
factorized common libraries parent pom.xml(log4j and xstrem) - this
will allow us to change the version identifier during upgrades in a
single place, rather than in several.
I also reduced dependency for each module: each module depends by
default by easymock, easymockextension and testng. All other 'shared'
artifacts were moved to dependecyManagent (from dependency).
Some unused dependencies (mvn dependecy:analyze) were removed.
Please let me know if you see any build issues.
And a question: what is the purpose of having a parent pom.xml and
<root>/pom.xml -> can't the <root>/pom.xml be the parent?
Cheers,
Mircea
6:30 p.m.
On Sat, Aug 29, 2009 at 8:08 AM, Mircea Markus <mircea.markus(a)jboss.com>wrote:
Hi,
And a question: what is the purpose of having a parent pom.xml and
<root>/pom.xml -> can't the <root>/pom.xml be the parent?
Yes it can. Years ago Eclipse wasn't able to handle nested projects, in
which both a folder and a subdirectory of it contained a .project file with
the expectation that they would both result in projects on import. Because
this didn't fit Maven's view of the world people would put the parent pom in
a peer directory--this was called a Flat Project Layout--see the bottom of
http://maven.apache.org/plugins/maven-eclipse-plugin/reactor.html.
Nested projects are no longer a problem in Eclipse, and in particular
m2eclipse supports them well. I don't see why the two parents (the
parent-parent and the peer-parent) shouldn't be merged (into the former) in
Infinispan. This particular case is strange since it seems to merge the
ideas from nested and flat structures. Not sure why...
-jeff
3:34 p.m.
On 29 Aug 2009, at 17:30, Jeff Ramsdale wrote:
On Sat, Aug 29, 2009 at 8:08 AM, Mircea Markus
<mircea.markus(a)jboss.com
> wrote:
Hi,
And a question: what is the purpose of having a parent pom.xml and
<root>/pom.xml -> can't the <root>/pom.xml be the parent?
Yes it can. Years ago Eclipse wasn't able to handle nested projects,
in which both a folder and a subdirectory of it contained a .project
file with the expectation that they would both result in projects on
import. Because this didn't fit Maven's view of the world people
would put the parent pom in a peer directory--this was called a Flat
Project Layout--see the bottom of
http://maven.apache.org/plugins/maven-eclipse-plugin/reactor.html
.
Nested projects are no longer a problem in Eclipse, and in
particular m2eclipse supports them well. I don't see why the two
parents (the parent-parent and the peer-parent) shouldn't be merged
(into the former) in Infinispan. This particular case is strange
since it seems to merge the ideas from nested and flat structures.
Not sure why...
Parent-parent structures are needed to share common libraries and
functionaliity, while a peer-parent is needed to build assemblies, jun
post-package tasks, etc.
If you can manage to build these into a single pom at the root level,
be my guest. :)
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org
5354
days inactive
5363
days old
infinispan-dev@lists.jboss.org
2 comments
3 participants
participants (3)
-
Jeff Ramsdale -
Manik Surtani -
Mircea Markus