RE: [VOTE] Remove developers from plugins project.xml

2004-05-17 Thread Arnaud Heritier
> > I don't have time until early June, but would be happy to help you if > you need by then. Same thing for me. We could think about this in June. > > > > Jerome Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For add

RE: [VOTE] Remove developers from plugins project.xml

2004-05-13 Thread Jerome Lacoste
On Thu, 2004-05-13 at 00:50, Arnaud Heritier wrote: > > > I think you're reaching an interesting point here. > > > > The developer information should be retrieved from an external > > repository, this being an LDAP or a simple global XML file shared by all > > projects. > > > > Otherwise yo

RE: [VOTE] Remove developers from plugins project.xml

2004-05-12 Thread Arnaud Heritier
> I think you're reaching an interesting point here. > > The developer information should be retrieved from an external > repository, this being an LDAP or a simple global XML file shared by all > projects. > > Otherwise you have a maintenance burdain on big projects. > > Furthermore, it i

RE: [VOTE] Remove developers from plugins project.xml

2004-05-12 Thread Jerome Lacoste
Arnaud wrote: > Yes. But we use the same declaration for a developer (or contributor) in > several project.xml. > Actually a developer is defined by a name, an email, ... > Someone asked some month ago to have a messengerId. > We can think that it all this data could be retrieved from a single > r

RE: [VOTE] Remove developers from plugins project.xml

2004-05-11 Thread Arnaud Heritier
> > I'm agree with you but the result is that all maven-plugins commiters > are > > developers for all plugins :-( > > Nope. They are potential plugin "developers" that's all. Yes, potentially. > > > > Yes. I think that we can have developers with a commiter role but also > > developers without

RE: [VOTE] Remove developers from plugins project.xml

2004-05-11 Thread Vincent Massol
> -Original Message- > From: Arnaud Heritier [mailto:[EMAIL PROTECTED] > Sent: 11 May 2004 22:39 > To: 'Maven Developers List' > Subject: RE: [VOTE] Remove developers from plugins project.xml > > > > > -Message d'origine- >

RE: [VOTE] Remove developers from plugins project.xml

2004-05-11 Thread Arnaud Heritier
> -Message d'origine- > De : Vincent Massol [mailto:[EMAIL PROTECTED] > Envoyé : mardi 11 mai 2004 18:02 > À : 'Maven Developers List' > Objet : RE: [VOTE] Remove developers from plugins project.xml > ... > > For me, developers are the persons

Re: [VOTE] Remove developers from plugins project.xml

2004-05-11 Thread Jason van Zyl
On Tue, 2004-05-11 at 11:26, Heritier Arnaud wrote: > Hi all, > > I would like to propose that we remove the developers declaration in the pom > for each plugin and that we use only the one in the plugin-parent. > > Why > > Because : > - It will simplify the mainten

RE: [VOTE] Remove developers from plugins project.xml

2004-05-11 Thread Vincent Massol
> -Original Message- > From: Heritier Arnaud [mailto:[EMAIL PROTECTED] > Sent: 11 May 2004 17:45 > To: Maven Developers List > Subject: RE: [VOTE] Remove developers from plugins project.xml > > ok for this. > But in this case we must use roles to define this.

RE: [VOTE] Remove developers from plugins project.xml

2004-05-11 Thread Heritier Arnaud
x27; > Objet : RE: [VOTE] Remove developers from plugins project.xml > > > -1 > > If section is missing in some plugins it should > be added there. > > > It should be clearly indicated who is a responsible for each > of the plugins > and who is "the man"

RE: [VOTE] Remove developers from plugins project.xml

2004-05-11 Thread Vincent Massol
I'm -1 because more and more plugins will be considered as standalone projects with their own lifecycle. Thanks -Vincent > -Original Message- > From: Heritier Arnaud [mailto:[EMAIL PROTECTED] > Sent: 11 May 2004 17:27 > To: Maven Dev (E-mail) > Subject: [VOTE] Remove developers from plugi

RE: [VOTE] Remove developers from plugins project.xml

2004-05-11 Thread Maczka Michal
-1 If section is missing in some plugins it should be added there. It should be clearly indicated who is a responsible for each of the plugins and who is "the man" which should be contacted when any changes to plugin are going to be added. It's clear that each plugin has different developers.