On Wed April 1 2009 11:16:58 am Jochen Wiedmann wrote: > On Wed, Apr 1, 2009 at 1:23 PM, Mark Hobson <[email protected]> wrote: > > 2009/4/1 Olivier Lamy <[email protected]>: > >> No the release parent has correct information but not your child(s) > >> pom(s) because if the child doesn't have any scm information they are > >> inherited from the parent ! + your current project's artifactId > > > > Are there any plans to change this for Maven 2.x/3.x? It's quite an > > assumption to make that a project's SCM location is directly beneath > > its parent. > > It's the only reasonable assumption for a default value. So, why change it?
No. If everything is being released as a reactor build, there are at LEAST two better options for a "default" value: 1) If the <parent> element in the pom has a "relativePath" element in it, that could be used to resolve the current location against the parent. 2) If the parent is in the reactor, you can get the "basedir" for the parent and the "basedir" for the child and calculate the difference from an scm standpoint. Either of those would yield much better results (IMO) than the "blindly assume parent+artifactId" thing that is there now. -- Daniel Kulp [email protected] http://www.dankulp.com/blog --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
