On Tue, 2003-03-04 at 19:46, Stanley,Michael P. wrote: > Cool. > > Question: What happens when dependencies collide? i.e. in my > dependency I state that I depend on projectX version 1.3 and projectY > version 2.0. projectY version 2.0 has dependency on a different version > of projectX. How will situations like these be resolved?
It would be easy enough to detect differing versions. Typically during integration work I use the JAR override mechanism to make sure that I'm using the same version of all the JARs that go into the final work. Often I have to diddle the versions to get things to work correctly. > - Mike > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, March 04, 2003 6:45 PM > > To: Turbine Maven Developers List > > Subject: Re: POM repository and dependency references > > > > The idea is to be able to have a dependency on a POM, and all the > > dependencies of that POM are 'inherited' for your project. > > > > For this to be workable, we need many more POMs to be deployed. > > > > See http://www.ibiblio.org/maven/plexus/poms/ for an example. > > > > As part of the repository audit, I've got a whole heap of projects > that we > > can create POMs for, from the repository audit file. > > > > See > > > http://jakarta.apache.org/turbine/maven/reference/plugins/repository/tas > ks > > .html > > for details about what's happening there. > > > > Creating these directories and files is item 2 & 3 for me. Item 1 I've > > delegated to Jason already. > > -- > > dIon Gillard, Multitask Consulting > > Blog: http://www.freeroller.net/page/dion/Weblog > > Work: http://www.multitask.com.au > > > > > > "Age Mooy" <[EMAIL PROTECTED]> wrote on 05/03/2003 09:11:52 AM: > > > > > Hi, > > > > > > Jason has mentioned the idea of a POM repository a few times on this > > > list. I don't know exactly what he proposes to do with it but I have > > > also been thinking about something like that lately. > > > > > > I have built quite a lot of Turbine 2.x/Torque webapps the last few > > > months and when writing the project.xml for these projects, I keep > > > running into the same problem. For each new webapp project I have to > > > manually copy all the dependencies from the turbine-2 and db-torque > > > project descriptors. If I upgrade from Turbine 2.2.0 to 2.2.1 or > 2.3, I > > > have to check the Turbine project.xml to see if any of the > dependencies > > > changed and make the relevant corrections in my own project.xml > > > > > > Things would be a lot simpler if I could just say something like > this: > > > > > > <dependencies> > > > <dependency ref="turbine-2.2.0"/> > > > <dependency ref="torque-3.0.0"/> > > > <dependencies> > > > > > > and Maven would lookup the relevant dependencies in a (local/remote) > POM > > > repository somehow. > > > > > > Is this what the proposed POM repository would be used for ? If not, > how > > > about implementing something like this ? > > > > > > Age > > > > > > > > > > > > > --------------------------------------------------------------------- > > > 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] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
