A little more info. It looks to be failing on the tag. I have tried a bunch of different configurations for the <scm> tag and I cannot get it to work. Bascially it should create a tag in both repos (repo1, and repo2) .
Any help/ideas would greatly appreciated. Thanks in advance! On Tue, Aug 21, 2012 at 7:24 PM, Billy Newman <newman...@gmail.com> wrote: > I have a multi module project that covers 2 svn repositories: > > svn/repo1/personal/billy/(trunk/branches/tags) > svn/repo2/personal/billy/(trunk/branches/tags) > > repo1 > --> pom.xml (main pom) > ----> module 1 > ----> pom.xml (module 1 pom) > > repo2 > --> pom.xml (child of main) > ---->module 2 > ----> pom.xml (module 2 pom) > > in the main pom I setup the release plugin as follows: > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-release-plugin</artifactId> > <version>2.3.2</version> > <configuration> > <commitByProject>true</commitByProject> > </configuration> > </plugin> > > All seems to work until the very end. It looks like the release > plugin is trying to tag to svn/repo1/personal/billy/ and cannot. > Maybe I am configuring the scm tag incorreclty. > > In my main pom (repo1) > <scm> > > <connection>scm:svn:http://svn.repo.net/svn/repo1/personal/billy/trunk</connection> > </scm> > > In repo 2 pom (child of repo1 pom), this on points to repo2 > <scm> > > <connection>scm:svn:http://svn.repo.net/svn/repo2/personal/billy/trunk</connection> > </scm> > > Is that correct? The release plugin also changes the scm tag in weird > ways that do not makes sense to me (which makes me think the scm tag > is what I am not setting up correclty) > > Any ideas/suggestions? > > Thanks, > Billy --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
