Absolutely. If you get something that works, then I'll commit to both maven (against HEAD please) and jelly.
I don't know if anyone else uses the jelly-ant tag library. If so, we might need to be careful what changes are made there. You might need to look into the sandbox commons-grant library, which I'll try and fold back into Maven ASAP as I had intended to. This is the bridge between Maven and an Ant project. Good luck! - Brett On Tue, 19 Oct 2004 03:48:55 -0200, Felipe Leme <[EMAIL PROTECTED]> wrote: > On Thu, 2004-10-14 at 14:18, Michael Gaffney wrote: > > > 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 th > > That's great :-) > > > 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. > > I haven't checked the issue, but I doubt you're wrong. > > > to be solved by someone with commit privileges to both the maven > > project and the jelly:ant library. > > There are many committers with both privileges, so this is not an issue. > The main issue is finding them time :-) > > > 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. > > I agree that submitting patches which are not applied (or even worse, > that get obsolete when someone find the time to apply them) is > frustrating, but given the urgency of this issue (i.e., supporting ant > 1.6.x), it should not be a problem. So, bring the patches one :-) > > -- Felipe > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
