> -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: 16 April 2004 03:08 > To: Maven Users List > Subject: RE: Maven and Development Process > > On Thu, 2004-04-15 at 17:05, Vincent Massol wrote: > > > 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. > > > > I agree with this. However I'm not sure recursive inheritance is enough. > > If we wish to support all use case, we'll need to support dependencies > > reference as several projects may want to share some references while > > they are not sharing exactly the same set of references. Putting all > > references at the top level would mean that several subprojects which do > > not need all these references will still inherit from them. > > Do you use this sort of setup?
Yes. I personally don't like XML entity includes. So I'd be happy to have some built in ways in Maven. I made some proposal a long time ago on the Maven mailing lists about the ability to define groups of dependencies, giving them an id and the ability to reference by id. The main problem is that we wish all projects to use the same version of such and such dependency (say version 1.2.8 of log4j for ex). How do you ensure this? The solution we have followed was to move all external dependencies to the top level project.xml so that versions are controlled in one place. Unfortunately the side effect is that you can't guess anymore what is the minimal set of dependencies required by such subproject. Not sure it matters that much but I personally like to know this kind of information and have some clean stuff. If this use case could be supported it would be great. Here are the requirements: 1- ability to define deps in each project 2- ability to factor some set of dependencies 3- ability to say that all deps for such artifact is always for such version (this third requirement could be satisfied by requirement #2). > > I think that the dep section would be expanded along the tree of POMs > where needed. But one thing I was think about the POM structure was the > possibility of a meta flag to indicate whether an element was overriden > or aggregated. Still not sure if this would be necessary for this type > of scenerio, but there will be some surveys coming along with the maven2 > alpha so we'll find out :-) cool Thanks -Vincent > > > -Vincent > > > > > > > > > > > > > -----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] > > > > > > > > --------------------------------------------------------------------- > > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
