How would we be able to differentiate then between the properties a plugin exposes and those it uses for it's own purposes? The plugin plugin uses plugin.properties to generate docs. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Work: http://www.multitask.com.au
Jason van Zyl <[EMAIL PROTECTED]> wrote on 26/06/2003 07:58:52 AM: > Hi, > > We had a quick chat in IRC about aligning plugin artifacts with normal > Maven Projects. By this I mean using maven.xml instead of plugin.jelly > and the simple project.properties instead of plugin.properties. > > I think this alignment would make explaining plugins work as they now do > work the same as a normal project. > > I can change all the plugins in CVS but admittedly plugins outside the > ones we store will have to change the file names if we make the change. > I would like to make the plugins more consistent with normal projects > for 1.0 if there are no objections. > > -- > 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] >
