Thanks. I had a look this morning and came to the same conclusion. I don't think jelly:maven should extend jelly:core, but I don't really want to change it now... I think we'll have to live with it for now and call it deprecated and semi-removed :)
I'll add an FAQ. Cheers, Brett > -----Original Message----- > From: Maxwell Grender-Jones [mailto:[EMAIL PROTECTED] > Sent: Friday, 21 May 2004 4:15 AM > To: [EMAIL PROTECTED] > Subject: rc3 breaking maven:set > > > Brett, > > I think I've worked out what the problem was that I was > complaining about on irc (TheManiac). > > previously jelly:maven extended jelly:core, so when I called > maven:set, it *actually* called the core:set (using the same > notation). This meant that I could happily call <maven:set > var="foo" value="bar"/> and everything worked fine. > > However, since there is now a <maven:set /> tag, it now > overwrites the <core:set /> tag, which broke my build. The > problem therefore was really one of me misusing maven rather > than anything else (I just blindly tried a whole bunch of > things until I got something that worked without, at the > time, really understanding what what was going on). > > However, might be worth a little footnote perhaps, who knows... > > Regards, > > Max > -- > [M. Grender-Jones ] > [Work: 0845 6667778 Play: 07714 762940] > [MSN: [EMAIL PROTECTED] ICQ: 28467015] > > I hate the country, all those animals walking around un-cooked. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
