On Thu, 2003-11-13 at 17:24, Brett Porter wrote: > Jason, > > I think it would be better not to mess with it right now. But it's a fine > goal for a cleaner bootstrap - the bootstrap ant task can just pull down the > JARs from the repo.
The bootstrap can just run the reactor in ../maven-plugins instead of src/plugins-build. I would just like placed all together for the sake of not even having to worry about merging the changes and start moving toward full consistency. I don't think this would be hard to do at all. > As far as what is different between the original branch and the new RC2 > branch, diffs probably aren't going to help. While I pulled across the goal > to script mapper, jelly plugin class, etc, I wrote the plugin manager > changes piece by piece based on your code, and made some refactorings and > bugfixes. > > Here is what I didn't take: > - driver.jelly still exists, didn't do the complete removal of that > - didn't change to XPP > - didn't use the new werkz goals. This seemed to be where a lot of > incompatibilities were introduced with plugins. I did need to do the new > goal tag so that overrides worked correctly. > - didn't upgrade to werkz-beta-11 or use the build listener. > > I think that should be it. Coolio, I give it a full day tomorrow. Are the memory leaks completely gone in RC2_UNSTABLE as they are in RC1_REFACTOR? If so then then that's a big cross section I won't look at. In RC1_REFACTOR I basically eliminated the use of Jelly/Ant until as late as possible which is in the PluginManager which did in a big chunk of the memory problem. > - Brett > > > -----Original Message----- > > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > > Sent: Friday, 14 November 2003 2:20 AM > > To: Maven Developers List > > Subject: Moving all plugins to maven-plugins > > > > > > Howdy, > > > > I am starting to compare MAVEN_RC1_REFACTOR, > > MAVEN_RC2_UNSTABLE and HEAD and having copies of the core > > plugins in each of those is really annoying. > > > > Could we move all of the plugins to maven-plugins and figure > > out a simple way to pull in what we consider core plugins for > > the bootstrap? > > > > This would certainly make working across the branches easier > > because there will be no plugins to deal and this I think > > would be more consistent in that all the plugins will be out > > of the core. > > > > -- > > 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] > > -- 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]
