Let me answer some of my own questions... > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: jeudi 7 avril 2005 22:30 > To: 'Maven 2 Developers List' > Subject: Questions on maven-scm and others... > > Hi there, > > I'm using maven-scm as my example for trying to migrate cargo from m1 to > m2. > I have a few questions: > > 1/ In maven-scm/scm-api/pom.xml, why is groupId equal to maven and not > org.apache.maven.scm?
Apparently scm-api is the old version and I should look at maven-scm-api instead. I've now done a clean checkout... > Isn't the groupId inherited anyway from the master pom? Yes it is. > 2/ Most elements are duplicated from the master pom. Is that normal? Have a look at maven-scm-api > 3/ Is it necessary to have <modelVersion>4.0.0</modelVersion> in all > subprojects or can it be inherited? Still unsure about the answer. > 4/ I have the following directory structure in Cargo: > > cargo/ > |_ core/ > |_ util/ > |_ pom.xml > |_ pom.xml > |_ pom.xml > > When I type "m2 install" in cargo/, it doesn't find the nested modules. I > have the following module definitions: > > cargo/pom.xml: > > <modules> > <module>cargo-core</module> > </modules> > > cargo/core/pom.xml > > <modules> > <module>cargo-core-util</module> > </modules> > > What am I doing wrong? You need to tell what parent to use using a <parent> tag!! Ok, here's another question: What if I want to share a version between all my modules and I don't want to have to specify it everywhere because when I move to a new version I'll have to update the 20 places where it is written? (I'm sure you have an answer for that! :-)). Thanks -Vincent
