On Sun, 2003-11-16 at 16:49, Brett Porter wrote: > Status update: I believe I now have all of the plugin context issues licked. > I haven't had a chance to fully test my last set of changes, but I > identified the problem. > > Jason, how did your work on the werkz code go on the weekend?
I worked on Plexus and Wagon all weekend. I'm afraid to start on that Maven branch because it will inevitably mean I won't look at anything else for a span of days. But I think our work in the separate branches is primarily complementary and originally comes from the branch I'm working on so whatever bits and pieces go in don't really matter. I won't attempt to fix the werkz problem until I can replicate it the problem with a test. I am also not averse to rolling in more changes post 1.0. If most of the memory leak is taken care I think everyone will be happy with that. > This leaves some very minor things left to fix and some more testing before > the RC2 branch is (hopefully!) fully functional again with all existing > plugins/projects, unless they seriously abused the way the old system > worked. > > >From there, I'd like to attempt to reimplement plugin caching (the old > technique was incompatible) before RC2 is made available to reduce the > startup time again. I did reimplement the searching and caching in a different plugin manager that had a number of tests and fixed the problem where the old plugin manager didn't find dependencies properly. It was a source file with a set of diagrams outlining the possible dependencies between goals, prereqs and other plugins. > Cheers, > Brett > > > -----Original Message----- > > From: Brett Porter > > Sent: Thursday, 13 November 2003 8:20 AM > > To: 'Maven Developers List' > > Subject: RE: rc2 unstable > > > > > > Done. I noticed you already did the plugins in CVS - I > > thought this was only on your copy. Cool. Much cleaner now. > > Will also make any merging later a helluva lot easier. > > > > Current status: the pluginVar tag is not working properly in > > a reactor, because project.context != context.project in some > > cases (it seems projects have multiple contexts). I need to > > draw this up and figure out where the double mapping crept in. > > > > This means touchstone runs regularly, but not via maven test > > in the base directory (eg bootstrap). > > > > Cheers, > > Brett > > -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
