Jason, One interesting side-effect of using entities is that if you're importing them from an external source (which, if you're not, what's the point?) then packaging/deploying a pom to the repo will result in an incomplete info set for others d/l'ing that project for a recursive build or recursive resolution...
-john On Thu, 2004-04-15 at 16:12, Jason van Zyl wrote: > On Thu, 2004-04-15 at 14:38, Mark Langley wrote: > > If you use XML entities to define your version numbers rather than hard > > coding them in the project.xml files, the process of switching between > > snapshot and release versions becomes much easier. > > > > See http://wiki.codehaus.org/maven/EnsureProjectConsistencyWithEntities for > > more details. > > Do a lot of people actually use this mechanism? > > Is it simply because maven1 doesn't support recursive inheritance? > > Maven2 support recursive inheritance well so would anyone still really > need to use entities like this. Ultimately I suppose it doesn't matter > how the POM comes together but I would like support to come from Maven > itself and not the use of entities which I would consider a workaround. > > > > > -----Original Message----- > > From: John Casey [mailto:[EMAIL PROTECTED] > > Sent: April 15, 2004 1:46 PM > > To: Maven Users List > > Subject: Re: Maven and Development Process > > > > Somewhat unfortunately (because it does amount to a lot of work), that > > is the current best practice, I believe. At any rate, this is exactly > > what we do. > > > > -john > > > > On Thu, 2004-04-15 at 12:12, Amato Massimiliano (TLAB) wrote: > > > Hello guys, > > > > > > I am trying to convert our system from Ant to Maven, I managed to > > succesfully migrate all the projects into Maven but right now i am facing > > the problem of the development process integration. > > > > > > I saw there is a Snapshot feature that upload the latest build to the > > repository, but I am not really sure how does it work? > > > > > > >From my understanding if i am working on a project composed of several > > sub-project, like i do, i need to set in each project.xml file the version > > as x.y-dev and then install the articaft produced as install-snapshot or > > deploy-snapshot for the remote repo > > > > > > Now in each project that depends on that one, we need to update the > > version tag of the dependancy to SNAPSHOT and when we build, Maven > > automatically download the latest snapshot between the 2 that are in the > > local and remote repo > > > > > > When our development is completed we just need to change all the > > dependancy version number from snapshot to x.y and the main project.xml > > version from x.y-dev to x.y as well > > > > > > and there restart the cycle.... > > > > > > Is it correct or not? There is a better way to handle the development > > process? > > > > > > Thanks a ton for your help > > > Massimiliano > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey [EMAIL PROTECTED] CommonJava Open Components Project http://www.commonjava.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
