Thanks for doing this, David -- sorry I was the cause of said PITA, but always glad to battle the bloat when possible.
As a side note, things are moving again on my CRUD and persistent integration / cascading tests. Cheers, -- Alex On Jan 8, 2008 4:02 PM, David Blevins <[EMAIL PROTECTED]> wrote: > > On Jan 8, 2008, at 12:52 PM, Jacek Laskowski wrote: > > > On Jan 8, 2008 9:17 PM, <[EMAIL PROTECTED]> wrote: > >> Author: dblevins > >> Date: Tue Jan 8 12:17:31 2008 > >> New Revision: 610126 > >> > >> URL: http://svn.apache.org/viewvc?rev=610126&view=rev > >> Log: > >> Added plugin that can spit a list of the dependencies into the META- > >> INF/ directory of the jar > > > > What do we need it for? I mean we get the report generated and... > > Motivated by Alex who sent me like five emails one day. He threw the > openejb-core jar in his classpath and expcted that to work then sent > me the four subsequent emails saying "i've added foo.jar now i'm > getting NoClassDefFoundError on foo.class". I'd like to find a way to > check for our deps then print the txt version in an error message > including the list of jars we require. > > The other thing I've wanted for quite a while is to print something > into the lib/ directory of our standalone distro so if people aren't > using JMS, for example, they know what jars they can delete. Or on > the flip side, if they want to add webservices we can put a list on > the website of the jars they have to add. > > But in general it's really useful for figuring out where deps are > coming from. When I trimmed the deps in standalone from 30 meg to 14 > meg I literally had to trial and error-style delete jars from my repo > i didn't think should be in the assembly, build the assembly offline, > and see the dependency trail in the "can't download" error message, > then add the exclude to the dep that the trail showed as asking for > the dep. Was a real PITA. > > -David > >
