jira-importer commented on issue #551: URL: https://github.com/apache/maven-scm/issues/551#issuecomment-2964603651
**[Duncan Doyle](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mccloud)** commented OK, I did some testing today using my patch on a Subversion repo ...... and it fails. The problem seems to be that when I specify a connection URL like "scm:svn:svn://localhost/testrepo/trunk/MavenRoot" for the Super Pom project (see the example in my original post), the directory in which the files are put are "/testrepo/tags/{myTag}" and NOT "/testrepo/tags/{myTag}/MavenRoot". I had expected that the SCM plugin would generate the latter structure, but it doesn't. This results in a situation in which the tagging of the second project fails. Its connection URL is "scm:svn:svn//localhost/testrepo/trunk/Module1", and when the tag goal executes (with the patched plugin) it wants to create this structure "/testrepo/tags/{myTag}", which has already been created by the MavenRoot project, so the tagging fails. I did another test in which I put my modules in a RootFolder in Subversion, so the location is "testrepo/trunk/RootFolder". So this RootFolder contains all the modules. I also adjusted the connection URLs in my POMs. When trying to tag this project, the directory was again "/testrepo/tags/{myTag}" and did not preserve the folder structure in the trunk. Why does the plugin not preserve the original folder structure when tagging a project? There seems to be some other issues open on the SCM Subversion which basically have to do with the same problem, the plugin not being able to support a flat project stucture. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
