On Thu, 2003-09-11 at 09:19, Vincent Massol wrote: > > -----Original Message----- > > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > > Sent: 11 September 2003 15:01 > > To: Maven Developers List > > Subject: Re: Core plugins? > > > > On Thu, 2003-09-11 at 03:44, Vincent Massol wrote: > > > Hi, > > > > > > Brett mentioned in a an earlier email today that the idea of RC1 > would > > > be a maven core containing core plugins and other plugins which > would > > > not be part of the main maven distribution. > > > > > > What I don't understand is the concept of "code plugins". For me a > > > plugin is a plugin and they should all be treated equal. > > > > > > What is the rationale behind hosting core plugins in the maven core? > > > > Being required for the bootstrap is one criterion, > > The bootstrap is done with Ant AFAIK.
The first stage is. Subsequent stages use Maven itself along with several plugins. > It could contain the Plugin > Manager and thus the code to download plugins. Anyway, the bootstrap > already retrieves the needed jars from the remote repo. Why couldn't it > also retrieve plugin jars? I am all for doing this but not with the current code. I don't think it's necessary so long as plugins can be downloaded separately and used. > > the other is the core > > reports that people expect. The reports we could eventually off load > by > > themselves but for now I'm happy keeping the standard reports in the > > core for now. > > I think we're mixing 2 things here: > - what plugins and reports people are used to use > - where the plugins are located Yes, I realize. There are many things in the core currently that are mixed. I'm just saying it is not worth the time now to eliminate every last plugin from the core before we make a release. > What we seem to need is a way to prevent folks having to enter 20 plugin > dependencies in all their project.xml. These are the "core plugin". But > these plugins do not have to be located in Maven nor do they need to be > distributed with Maven. Yes, I'm saying a stopgap measure is to include the plugins so people don't have to do this for the majority of things and make a release. > What we need is a default project.xml that is automatically inherited by > all projects. In this default project.xml, we would list: > - the core plugins > - the core reports This can certainly come in subsequent releases but I would like to stick to the roadmap and get the release out. Or we will linger as we usually do. > But again, I don't see why we need to host any plugin within maven core. > > What would be nice is to let people add plugin they use daily to this > default project.xml so that they can benefit from them being > automatically added to all their projects. > > Comments? I would like to stick to the roadmap, but this issue can certainly be placed in JIRA for consideration for a 1.1 release say. I think it would suffice to include some expected plugins with the ability to add new ones and improve the mechanism in a later release. > Thanks > -Vincent > > [snip] > > > > --------------------------------------------------------------------- > 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]
