Setting the SVN tag path to use about gradle-release HOT 2 CLOSED

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"
}

from gradle-release.

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

from gradle-release.