Setting the SVN tag path to use

[vegemite4me]

Is it possible to set the tag path to use, similar to how you can specify the tagBase configuration value in the Maven Release plugin?

The project I am working on has the following projects:

svn.company.com/repo/trunk/foo
svn.company.com/repo/trunk/foo/foo-a
svn.company.com/repo/trunk/foo/foo-b

Where foo, foo-a and foo-b are three individual projects.

The requirement is to tag them as such:

svn.company.com/repo/tags/foo-1.0
svn.company.com/repo/tags/foo-a-1.0
svn.company.com/repo/tags/foo-b-1.0

Can this release plugin handle that kind of tagging structure?

[townsfolk]

Hmm. It wasn't intended to do that. As described in the documentation the plugin only works if the project structure is under one SCM. Do you checkout the projects at "foo" - so that foo-a, and foo-b are sub directories under "foo"?

If so, then no. As I said, the plugin only works with a single SCM at the project root. So it'll only create a single tag for all 3 projects.

If you checkout the projects individually so the directories look like:

.../foo
.../foo-a
.../foo-b

Then it should work, but you would need to set the tagPrefix property for foo-a and foo-b if you override the project name in your settings.gradle file.
In foo-a/build.gradle

release {
   tagPrefix = "foo"
}

[vegemite4me]

Do you checkout the projects at "foo" - so that foo-a, and foo-b are sub directories under "foo"?
Yes, I checkout at the top level (foo).

I completely understand that the plugin was not intended for this kind of project structure.

This gives me a reason to backup the idea of restructuring the layout in SVN.

Thanks
Robin