<fanning the flames> Also, while we're talking about ibiblio, wouldn't it be nice if we as project managers could retain control over our own release cycles by deploying to a public webserver controlled by us? Then, this dependency analyzer-on-steriods could perform some kind of lookup to determine which site to actually perform the download from...The accuracy of this (specified in the POM, maybe) could be determined via test code before the project's POM is allowed to be housed on the maven server (whichever instance of that server it is).
I know that the core developers have been talking about this for quite some time, and I have to say that I salivate merely thinking about having this type of power at my fingertips. I know, I know, someone will inevitably mention "What about nesting depth of dependencies...couldn't high depth produce an unbuildable project?" but I'd definitely rather work with that danger (and manage it) than have to constantly cut and paste dependency lists... Like I said, they are working/thinking on it, and I think they have something up their sleeves. But it never hurts to throw a feature vote into the circle when the subject comes up, I suppose! :) Cheers, John On Wed, 2003-11-19 at 17:22, Sonnek, Ryan wrote: > I think that if this was a supported feature, there would be several > projects that would migrate to the maven distributed POM due to greater > exposure and easier implementation. You just can argue with ease of use! > If there are high profile projects that ignore the distribution of the POM, > they could easily be left by the wayside for a smaller project with easier > pluggability to come in. in fact, it could be made a requirement that to > get posted on ibiblio.org/maven, you MUST have a pom for the version? > > Ryan > > -----Original Message----- > From: Steve Garcia [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 19, 2003 4:19 PM > To: 'Maven Users List' > Subject: RE: Finding artifact dependencies > > 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] > > --------------------------------------------------------------------- > 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]
