> -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: 22 April 2004 09:23 > To: 'Maven Developers List' > Subject: RE: Maven extensions (was RE: [Q] Setting a property so that it's > visible from another plugin) > > Dion was going to do this last year (actually make a tags JAR), but > nothing > came of it. > > The only plugin that requires RC3+ is multiproject for the reactor tag, > and > you wouldn't want to upgrade multiproject other than to get the memory > enhancements that come with the new tag. > > To be honest, I'd rather get 1.0 out with what works now and forget about > changing things. I've got enough to do already :)
True and I was not suggesting that it should be you doing it! :-) (you already have more than enough on your plate!). But see my other email (I was offline so only got to send it a few minutes ago). Thanks -Vincent > > - Brett > > > -----Original Message----- > > From: Vincent Massol [mailto:[EMAIL PROTECTED] > > Sent: Thursday, 22 April 2004 5:12 PM > > To: 'Maven Developers List' > > Subject: Maven extensions (was RE: [Q] Setting a property so > > that it's visible from another plugin) > > > > > > I think we already have a mechanism to provide extensions to > > Maven: it's called a plugin! Thus an even better solution for > > adding the setter tag is to move all the existing Maven Jelly > > tags to a plugin of its own. That will allow maven b10, rc1, > > etc users to automatically get the new features without > > breaking the plugins that use these new features. > > > > Any gotcha? > > > > Thanks > > -Vincent > > > > > -----Original Message----- > > > From: Vincent Massol [mailto:[EMAIL PROTECTED] > > > Sent: 22 April 2004 08:50 > > > To: 'Maven Developers List' > > > Subject: RE: [Q] Setting a property so that it's visible > > from another > > > plugin > > > > > > That's very true .... in principle. However when you've > > been having a > > 0.9 > > > or beta or rc for more than 2 years, it has no meaning at > > all! People > > have > > > already been using it in production and you just simply can't break > > them > > > completely, even though it's a beta or rc... :-) > > > > > > At least, we should make an attempt not to break them. For > > example, we > > > could instead create a jelly taglib. This taglib we could check > > whether > > > such class exists. If it does, use it. If not, use some jelly to set > > the > > > property. > > > > > > Alternatively we could simply provide a patch for versions < rc3 in > > the > > > form of a jar to drop in one's own mavenhome/lib for example. > > > > > > Of course, once we are in 1.0 final, for 1.1 we could > > remove the patch > > > support. > > > > > > It's more complex for us to manage but we should > > acknowledge that some > > > people have been using maven in production for some time > > and they may > > not > > > be able to switch quickly from, say, beta 10 to rc3. > > > > > > Thanks > > > -Vincent > > > > > > > -----Original Message----- > > > > From: Brett Porter [mailto:[EMAIL PROTECTED] > > > > Sent: 22 April 2004 08:20 > > > > To: 'Maven Developers List' > > > > Subject: RE: [Q] Setting a property so that it's visible from > > another > > > > plugin > > > > > > > > > > We should create a set tag as well I guess. > > > > > > > > > > Yep. That would be great. Only problem with this (as with > > > > > pluginVar - which is not too well named BTW if we add a set > > > > > tag) is that plugins who uses it will not be compatible with > > > > > previous Maven versions... > > > > > > > > I don't think we can support old betas and RCs. The whole point of > > > having > > > > a > > > > final 1.0 is that we are making a commitment to support > > that across > > > future > > > > releases - within reason. > > > > > > > > - Brett > > > > > > --------------------------------------------------------------------- > > 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]
