On 2/10/06, Lukas Theussl <[EMAIL PROTECTED]> wrote: > > Ahhh... I think "in the root classloader" is the key there. :) I only > > added the <classloader> tag to Jalopy and jalopy-ant. (How did this > > ever work the way it is??) > > That's what I would like to know, too... > > I'm afraid we really have to overhaul the jalopy plugin, it would be > nice if you could lend us a hand, especially regarding m1.0 combatibility...
What am I volunteering for? :) Are we talking about branching and fixing the problem in a maven-jalopy-plugin 1.3.x release? I need to get that working in order to look at converting to Jalopy 1.5b5 and a 1.4.x version of the plugin. I'm trying to get *out* of m1, but we seem to be going backwards... there's no m2 Cactus plugin, and now we have this dependency on the Jalopy plugin, which is listed as "low priority" for m2. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
