On Thu, May 23, 2002 at 09:03:55PM +0100, James Strachan wrote: > I agree; each jar you're dependent on should be able to have its own > dependencies. e.g. using commons-digester means you have to use > commons-logging, commons-beanutils and commons-collections. So it'd be > nice to not have to manually flatten the dependency trees, or only > flatten/mention those jars that you have specific requirements on.
Maven will eventually resolve all dependencies. Thus, if your project depends on commons-digester, then you don't have to specify the jars that it depends on as Maven will create its own dependency graph. Jason is working on this. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
