On Wed, May 20, 2009 at 1:54 AM, David Blevins <[email protected]> wrote:
> So when it's not in the build you get the published version which > does not drag in the unwanted dependencies. That part is a mystery for me. Could you rephrase it so I could get the entire picture? I do remember you mentioned it before that it should move to xbean where asm would have to be repackaged. What I wasn't happy with was that if we face such a problem with another project we can't control wouldn't maven-shade-plugin with its inlining feature be a solution? Should we always ask for a package change in the project where the issue was "born"? I thought it's a responsibility of the project that integrates with another so in our case it'd be OpenEJB. Why XBean should care about asm repackaging if it's us who run into it? Perhaps, if/when XBean were used with Hibernate the XBean developers would face it too, but alas it's not the case now. Where is my perception drifted away? Jacek -- Jacek Laskowski Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
