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,
Maybe you need developerConnection instead of connection (or both).
-Original Message-
From: Billy Newman [mailto:newman...@gmail.com]
Sent: Wednesday, August 22, 2012 9:56 AM
To: users@maven.apache.org
Subject: Re: Maven release plugin, multiple svn repos?
A little more info
plugin, multiple svn repos?
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
Am I do this right at all. Can you even use the release plugin on projects
that live in different svn repos.
I cannot find an example of this anywhere.
I have never done this, and expect it is not well supported if at all.
You are most likely one of the first people to attempt it.
Wayne
Wayne,
I was starting to wonder about that.
Anyone else confirm that the release plugin will not work across
multiple modules that live in different svn repositories?
This is a huge bummer as the release plugin is an awesome way to
release my project, but this one hang up is going to prevent me
I can confirm this is not possible.
You could also wonder: why should these be released at once?
Why not first release repo1-project, update the versions in repo2 (both
maven-release-plugin and versions-maven-plugin can help here) and then
release the repo2 project?
Even if this kind of
Just because I am checking out modules from different svn repos does not mean
my project structure is broken.
IE if I moved all to the same repo the project would work perfectly as you
pointed out. Just because these dependent modules live in different svn repos
should not make a difference.
