[
https://issues.apache.org/jira/browse/SCM-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961075#comment-17961075
]
ASF GitHub Bot commented on SCM-342:
------------------------------------
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.
> scm:tag should support flat project layout
> ------------------------------------------
>
> Key: SCM-342
> URL: https://issues.apache.org/jira/browse/SCM-342
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-plugin
> Affects Versions: 1.0
> Environment: Windows XP, Eclipse 3.3
> Reporter: Duncan Doyle
> Priority: Major
> Attachments: flatProjectTagPatch.txt
>
>
> I have a Maven2 Flat Project Layout as described here:
> http://maven.apache.org/guides/mini/guide-ide-eclipse.html
> Basically my directory layout is as follows:
> /MavenRoot/pom.xml (this is the SuperPom)
> /Module1/pom.xml
> /Module2/pom.xml
> /Module3/pom.xml
> Modules 1,2 and 3 are specified in the <modules> section of the SuperPom
> (e.g() <module>../Module1</module>). Each POM contains its own CVS connection
> URL.
> When I execute the scm:tag goal on the SuperPom in the MavenRoot project,
> only the MavenRoot project gets tagged. The same behaviour can be seen with
> the scm:update goal, which was fixed by providing a scm:update-subprojects
> goal.
> I would like to see this behaviour fixed in the SCM plugin, while Maven2
> advices a Flat Project Layout when working with Eclipse. At this moment I
> can't use the tag goal at all (it should be executed automatically by
> CruiseControl on a succesfull build).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
