Hi,

I am attempting to release a multi-module project which is set up something like this in an SVN repo:

Parent (pom-only)
|
| _ _Core  (linked via svn:externals to a different SVN location)
|
|_ _  Webapp (linked via svn:externals to a different SVN location)


Now, when I run release:prepare, I notice the top-level 'parent' project gets tagged but not the other ones, which causes the 'release:perform' to fail.

I am wondering if maven-release-plugin (or the underlying SVN provider implementation) could be smart enough to update the svn:externals definitions when tagging the release. Are there any potential issues with this approach that anyone can think of?

Look forward to thoughts?

Thanks,

Rahul

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to