Great ! That's exactly what I meant. Is this going to be in the b9 release ?
Age > 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]
