Would shading be eliminated if Maven 2.1 integrated OSGi so that component and plugin dependencies can be totally isolated from each other (i.e., privatized)?
Paul On Tue, Feb 26, 2008 at 7:59 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > On 26-Feb-08, at 5:40 PM, Brett Porter wrote: > > > > > On 27/02/2008, at 11:32 AM, Jason van Zyl wrote: > > > >> > >>> > >>> > >>> The reason for this is that commons-logging in the root > >>> classloader makes plugins unhappy (and the error reporting seems > >>> to be swallowed now). > >>> > >> > >> What about using slf4j and it's commons-logging replacement? > > > > this didn't give me any luck unfortunately. I'm not entirely > > comfortable tossing commons-logging into the root classloader at > > this stage without tying it into the plexus logging properly, so I > > think the pre-shaded webdav library is the way to go at this point > > (it's essentially the same thing). > > > > No the replacement for commons logging, so there is no commons logging > jar in the root classloader. > > > - Brett > > > > > > -- > > Brett Porter > > [EMAIL PROTECTED] > > http://blogs.exist.com/bporter/ > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Apache Maven > jason at sonatype dot com > ---------------------------------------------------------- > > Selfish deeds are the shortest path to self destruction. > > -- The Seven Samuari, Akira Kirosawa > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
