|
From: Alastair R. <ala...@ph...> - 2004-01-30 20:17:56
|
AFAIK, with Maven the developer still has to list all the dependencies = in the POM (Maven's project object model). I think the Maven team have = plans to improve this so that in effect each library will be distributed = with a structured description of its dependencies, so that when you want = to use the lib all of its dependencies are automatically discovered and = downloaded (and all their dependencies too... etc), and are then also = included in your app. Sounds great, though I think it's tentatively = scheduled for the 1.1 release, so it's still some way off.=20 > -----Original Message----- > From: spr...@li...=20 > [mailto:spr...@li...] > On Behalf Of William G. Thompson, Jr. > Sent: 28 January 2004 16:04 > To: spr...@li... > Subject: Re: [Springframework-developer] Another Spring=20 > positive reference..... >=20 >=20 > FYI. In reference to the dependency manager...it seems like=20 > Maven has=20 > been making good progress. I recently downloaded Pluto (RI Portlet=20 > Container) and the "maven fullDeployment" command snarfed all the=20 > dependant jars down for me...very nice. >=20 > Kopylenko, Dmitry wrote: >=20 > > <quote> > > Agree - especially with packages like collections and=20 > beanutils being=20 > > so > > standard, it creates a lot of resistance to pulling down a=20 > project and=20 > > giving it a quick trial run. I appreciate the _Spring approach_=20 > > <http://sourceforge.net/project/showfiles.php?group_id=3D73357> - = one=20 > > version with all dependencies and one without. At the very=20 > least, it=20 > > would be useful if projects released with a list of URLs=20 > for the JARs=20 > > (either online or in the installation notes). > >=20 > > Still, it makes me wonder if there's a need for a project like the=20 > > linux > > dependency managers, which would go and fetch all the jars=20 > you need.=20 > > That would make a sweet Ant task. I haven't seen anything=20 > like that,=20 > > though I recall the perl CPAN module can handle it. The problem is=20 > > there's no protocol for specifying version dependencies in=20 > JAR files. > >=20 > > </quote> > >=20 > > from TSS thread: > > _http://www.theserverside.com/news/thread.jsp?thread_id=3D23544_ > >=20 > > Regards, > > Dmitriy. > >=20 >=20 >=20 |