I (for one) would love to see a feature like this. This would as cool, perhaps even cooler, than the existing artifact dependency feature Maven has so elegantly employed. I presume that this would require that each individual project deploy meta-data about what their dependencies are...wait that is the POM! :-) Maybe distributing the POM, or a POM like structure, with each artifact that is installed in the remote repository? That will work with projects that use Maven to build, but it won't work nicely for non Maven software.
> How do I found out what the dependencies for a given artifact are? > > Example: I can place a dependency on struts-1.1 in > project.xml, which will be fine for compilation, but to > deploy an app using this I need a whole bunch of stuff that > struts depends on, and I can't see any thing under struts on > ibiblio that tells me what jars and versions I need. > > It seems the only way to find this out is to download struts > from apache look at what's inside and fill in a bunch of > dependencies. Would it not be sensible to have every artifact > in ibiblio define its dependencies (within > ibiblio) and have maven resolve the lot - else its just a big > collection of versioned jars - So when the next version of > struts is out I have to make sure I update every dependency > in project.xml again. > > Is this the case? > > Cheers > > Kevin > > > > > --------------------------------------------------------------------- > 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]
