On Thu, 2004-04-15 at 17:02, Mark Langley wrote: > This allows me to maintain details of each item in exactly one place (the > .ent file), and have them automatically updated in the 5, 10, or 15 projects > that might happen to need them. This is particularly useful for dependencies > - I can guarantee that any module using log4j links to version 1.2.8, then > enforce that they migrate simultaneously to 1.2.9 with a one-line change.
I was asking because I believe why this is not possible in maven1 because recursive inheritence isn't support, it is in maven2. > The maintenance time goes way down this way, and as a side benefit our > project.xml files are shorter and much more comprehensible. Certainly, anything that makes the process more comprehensible is a good thing. > I'm not sure why you would consider entities a workaround - they allow you > to define a master list of resources, pick and choose which resources fall > into each project, and keep everything synchronized. In maven2 I believe this can be done without the use of entities, but still it ultimately makes no difference to the XML processing of the POM as long as what maven gets is intact. > One could always > implement the same capability within Maven, but that seems like unnecessary > duplication of effort. The XML parser is giving you this functionality for > free - might as well take advantage of it. It's free in the XML parser, but with the advent of maven2 you'll see things like POMs being stored in DBs and prevayler (which I'm working on) and LDAP (which is something Alex is interested in) and hopefully a variety of other sources. For maven1 it is the only way to make a large set of POMs managable, but for maven2 I don't think it will be necessary but you certainly don't have to change the way you do things. Someone else answered me in IRC and they problem for them was that recursive inheritence doesn't work in maven1 so they needed to entities to make things sane. > Mark > > -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: April 15, 2004 4:13 PM > To: Maven Users List > Subject: RE: Maven and Development Process > > 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] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
