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. Mainly why shouldn't I be able to override the release plugin for the repo2 stuff to tag in repo2. Basically repo1 does it's release based on its poms properties, and repo2 child of main overrides main poms release and properties. In the end yes I could release stuff from repo1 then update versions on repo2 and release. But that is really a work around to a limitation on the release plugin. Sent from my iPhone On Aug 22, 2012, at 1:28 PM, "Robert Scholte" <rfscho...@apache.org> wrote: > 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 multitagging would work, I'm sure you'll hit several > more issues during the release-cycle. > If you can't get this project running with a single check out, you won't be > able to 'perform' the release either. > That should be a sign that you have an issue with your project structure. > > The only solution I can think of, is to make a separate project responsible > for checking out both projects and building them. But I wouldn't advice that. > > -Robert > > > Op Wed, 22 Aug 2012 20:45:13 +0200 schreef Billy Newman <newman...@gmail.com>: > >> 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 from >> using it. Unfortunately there is absolutely no way I can get around >> having the modules in different repos as its a security issue with my >> company. >> >> Billy >> >> On Wed, Aug 22, 2012 at 11:45 AM, Wayne Fay <wayne...@gmail.com> wrote: >>>> 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 >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
