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]
