> -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: 23 April 2004 01:38 > To: 'Maven Developers List' > Subject: RE: [Q] Setting a property so that it's visible from another > plugin
[snip] > > In my case at work, we are using beta 10. We want to move to > > rc2 and we have started the migration even before rc2 was out > > (we started about 2 months ago I think). > > I'm surprised its such a hassle - I have a complicated system (including > Solaris too :) and it migrated to RC1 seamlessly. RC2 works the same too, > as > will RC3, etc. > > If there's anything I can do to help, let me know... No, it's not that hard in principle. It's just that everyone is busy so it takes long. Of course we also had lots of "hacks". For example we had extended the reactor and it stopped working because we were using some internal API which have changed, etc. Mostly our fault. > > I was speaking to some Atlassian folk last night and they are also on > beta-10, as is Avalon. I wonder how many others have decided to stick with > it? I guess quite a few. They'll probably start migrating with 1.0 final. > > > So we tried using the latest checkstyle > > plugin with beta 10. > > I don't think you can reliably install newer plugins on the betas because > of > the changes in the core. > > > But I do agree with you Brett. Please accept my apologies. I > > had forgotten about the possibility of not upgrading one's > > own plugins... > > :-) > > No problem. I apologise too because I may have come across a bit harsher > than I intended. I agree with all of your concerns, and think we should > careful focus on this after 1.0 is released, but not put the effort in to > support beta-10. I think we should spend that effort getting 1.0 up to > scratch and out the door, and invest it also in helping people migrate > from > beta-10. I agree. Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
