2009/4/1 Jorg Heymans <[email protected]>: > (taking this back to the users list) > > On Wed, Apr 1, 2009 at 10:01 AM, Olivier Lamy <[email protected]> wrote: >> 2009/4/1 Jorg Heymans <[email protected]>: >>> On Wed, Apr 1, 2009 at 9:33 AM, Olivier Lamy <[email protected]> wrote: >>> >>>> Try mvn help:effective-pom I'm not sure the scm information is correct. >>> >>> I don't know what to make from the scm info, in any case it points to >>> a non-existing tag: >>> >>> <scm> >>> >>> <connection>scm:svn:http://server/svn/project/tags/myparent-4/myproject</connection> >>> >>> <developerConnection>scm:svn:http://server/svn/project/tags/myparent-4/myproject</developerConnection> >>> </scm> >>> >>> The "myproject" at the end seems bad. In any case somehow beta-8 was >>> able to cope with this, wierd. >> >> :-) (in this case IMHO your project is bad : publishing site will >> publish bad source info etc.. changelog plugin can not work etc..) > > The released parent pom contains this scm element : > > <scm> > <connection>scm:svn:http://server/svn/project/tags/myparent-4</connection> > > <developerConnection>scm:svn:http://server/svn/project/tags/myparent-4</developerConnection> > </scm> > > Do you mean this is wrong ? 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
in your case effective pom will be : <scm> <connection>scm:svn:http://server/svn/project/tags/myparent-4/${artifactId}</connection> <developerConnection>scm:svn:http://server/svn/project/tags/myparent-4/${artifactId}</developerConnection> </scm> And IMHO this is not correct for your current project ! SIte informations won't be correct. Your child poms must contains their own scm informations (something like) : <scm> <connection>scm:svn:http://server/svn/project/myparent/trunk/${artifactId}</connection> <developerConnection>scm:svn:http://server/svn/project/myparent/trunk/${artifactId}</developerConnection> </scm> Sure it's a side effect of using remote tagging to have a workaround on the svn > 1.5.0 issue. But you can set remoteTagging to false in the release plugin configuration. > > Thanks, > Jorg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
