[
https://issues.apache.org/jira/browse/SCM-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961071#comment-17961071
]
ASF GitHub Bot commented on SCM-342:
------------------------------------
jira-importer commented on issue #551:
URL: https://github.com/apache/maven-scm/issues/551#issuecomment-2964603629
**[Duncan
Doyle](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mccloud)**
commented
So, how would one solve that with the current way that the scm:tag works??
Basically in the case you outlined, one needs to issue 2 mvn scm:tag
commands, if neither pom is a superpom of the other. In that case, my algorithm
would still work.
What is your opinion on how to solve this issue? Basically the main usage
(for me that is) of the scm:tag command is to automatically tag a complete
project using a single command in a nightly build process (e.g. CruiseControl,
Continuum) using the build number as tag. And the single command should work
for both a 'normal' maven layout as well as a flat project layout.
> 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)
