Re: element in plugin POMs

2008-08-11 Thread John Casey
So that suggests that the only appropriate place to use inheritance for the section would be in projects using a parent POM such that the parent and these children are released at the same time. This way, I *think*, the inherited SCM urls would be correct after the release, and the new develop

Re: element in plugin POMs

2008-08-11 Thread Stephen Connolly
I think that is the issue On Mon, Aug 11, 2008 at 9:37 PM, David Jencks <[EMAIL PROTECTED]>wrote: > Maybe I misunderstood what Benjamin is saying but I believe I've run into > this also... IIUC the situation is that the plugin and its parent pom are in > totally unrelated svn locations and _not_

Re: element in plugin POMs

2008-08-11 Thread David Jencks
Maybe I misunderstood what Benjamin is saying but I believe I've run into this also... IIUC the situation is that the plugin and its parent pom are in totally unrelated svn locations and _not_ including the svn tag in the plugin results in _completely incorrect and meaningless_ scm info in

Re: element in plugin POMs

2008-08-11 Thread Jason van Zyl
It sounds more like problems in particular plugins. Restating the SCM URL is a bad thing and we should make it so that it can be used reliably. If certain plugins are not dealing with it correctly then those need to be fixed soon. On 11-Aug-08, at 11:41 AM, Benjamin Bentmann wrote: Brian

Re: element in plugin POMs

2008-08-11 Thread Benjamin Bentmann
Brian E. Fox wrote: Seems fishy to me as well. We have inheritance for a reason. Over at Mojo I suggested adding several times for the following reason. Most of the time, a plugin inherits from a released parent whose SCM URL points to its tag, say repo/tags/parent-1 Now, running "mvn si

RE: element in plugin POMs

2008-08-11 Thread Brian E. Fox
Seems fishy to me as well. We have inheritance for a reason. -Original Message- From: Vincent Siveton [mailto:[EMAIL PROTECTED] Sent: Monday, August 11, 2008 1:53 PM To: Maven Developers List Subject: Re: element in plugin POMs 2008/8/11, Jason van Zyl <[EMAIL PROTECTED]>: >

Re: element in plugin POMs

2008-08-11 Thread Vincent Siveton
2008/8/11, Jason van Zyl <[EMAIL PROTECTED]>: > > On 11-Aug-08, at 10:29 AM, Vincent Siveton wrote: > > > > 2008/8/11, Benjamin Bentmann <[EMAIL PROTECTED]>: > > > > > Hi, > > > > > > about 2/3 of the plugin POMs have a element, the others can > > > apparently live well without. Maybe we could de

Re: element in plugin POMs

2008-08-11 Thread Jason van Zyl
On 11-Aug-08, at 10:29 AM, Vincent Siveton wrote: 2008/8/11, Benjamin Bentmann <[EMAIL PROTECTED]>: Hi, about 2/3 of the plugin POMs have a element, the others can apparently live well without. Maybe we could decide for one of these approaches to have things consistent. How do we want to han

Re: element in plugin POMs

2008-08-11 Thread Vincent Siveton
2008/8/11, Benjamin Bentmann <[EMAIL PROTECTED]>: > Hi, > > about 2/3 of the plugin POMs have a element, the others can > apparently live well without. Maybe we could decide for one of these > approaches to have things consistent. How do we want to handle this, delete > the SCM stuff from them or

element in plugin POMs

2008-08-11 Thread Benjamin Bentmann
Hi, about 2/3 of the plugin POMs have a element, the others can apparently live well without. Maybe we could decide for one of these approaches to have things consistent. How do we want to handle this, delete the SCM stuff from them or add it to all POMs? WDYT? Benjamin --