Arnaud, I'm a firm believer in submitting patches rather than complaints. I have submitted patches for plugins in the past and I will continue to submit patches in the future.
I actually started looking into this problem a few days ago in hopes of being able to submit a patch. Unfortunately, it appears to me that the solution to this problem involves changes to both maven and the jelly:ant library. I could be way off in that conclusion so please let me know if I'm wrong. If I'm correct and the solution involves making coordinated changes to both maven and the jelly:ant library, then, IMHO, this problem needs to be solved by someone with commit privileges to both the maven project and the jelly:ant library. I realize that it might be possible to coordinate the fixes by only submitting patches, but it just seems like a daunting non-technical task. Just my my 2 cents :-) Mike Gaffney On Thu, 14 Oct 2004 17:53:10 +0200, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > I'm aggree with you. The ant limitation is annoying but there are > actually two problems : > - An annoying incompatible change in Ant between the 1.5.X and the > 1.6.X complicates the ant upgrade in the maven's core. It's a question > of time. As soon as one of us will have the time to fix it, it will be > done. We hope that future ant releases won't break our integration. > - There's a big problem in maven 1 because there's not a separate > classloader for the core and for plugins. We are not able to use one > release of ant in the core and another in a plugin. I think that this > issue will be addressed in maven 2. > > In the meantime, we are forced to do with these issues. > > If you are interested to help us, you can try to submit patches !! > > That were my 2 cents :-) > > Arnaud > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
