On Tue, 2003-03-04 at 20:10, Stanley,Michael P. wrote: > > The problem with this is that I would still have to manually maintain > my > > own macro file to make sure the dependencies listed for the projects > it > > contains are up to date. But if Maven simply has access to a public > > version of the turbine-2.2.0 POM, it can always resolve the correct > > dependencies from there. Cut out the middle man :) > > I agree making the POM available can help resolve dependencies. I'm > curios to see how the dependency graph will be implemented.
A very rough version works in the plexus plugin to resolve all the dependencies. > The macro capability would still be pretty cool/useful, since it can > help with things other than just dependencies. In my previous email I > suggest a way to share macro files within the repository. > > Any interest in this type of functionality? Macros in the POM? No I would rather not see a macro facility popping up in the POM. I really don't think it's necessary. Full transitive dependencies will be supported. > - Mike > > > > > 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] -- 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]
