[ 
https://issues.apache.org/jira/browse/SCM-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965071#comment-17965071
 ] 

Olivier Lamy commented on SCM-920:
----------------------------------

This project has moved from Jira to GitHub Issues. This issue was migrated to 
[apache/maven-scm#1144|https://github.com/apache/maven-scm/issues/1144]. Please 
visit the GitHub issue to view further activity, add comments, or subscribe to 
receive notifications.

> Maven SCM plugin issue with flat multi module relative paths
> ------------------------------------------------------------
>
>                 Key: SCM-920
>                 URL: https://issues.apache.org/jira/browse/SCM-920
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>    Affects Versions: 1.11.1
>            Reporter: Javier Peña
>            Priority: Major
>         Attachments: flat-tycho-project-master.zip
>
>
> Hi,
> I am trying to apply the [Tycho Release 
> Workflow|https://wiki.eclipse.org/Tycho/Release_Workflow] and everything goes 
> well as long as i use a tree structure for the project. As soon as I try to 
> use a flat multi module structure the release fails because of the Maven SCM 
> plugin can not find the files.
> Original configuration of the maven-scm-plugin as defined in the workflow is:
> {code:java}
> <configuration>
>         <includes>
>             **/META-INF/MANIFEST.MF,
>             **/feature.xml,
>             */.product,
>             **/category.xml
>         </includes>
>         <excludes>*/target/*</excludes>
>         <message>Changing the Eclipse files versions</message>
> </configuration>
> {code}
>  
> The structure is as follows:
>     build -> pom.xml (parent pom)
>     module1 -> pom.xml
>     module2 -> pom.xml
>  
> First attempt to fix the issue was to use relative paths to the include 
> section so I try the follwoing:
>  
> {code:java}
> <configuration>
>     <includes>
>          ../module1/META-INF/MANIFEST.MF,
>          ../module2/feature.xml,
>          ../module4/*.product,
>          ../module3/category.xml
>     </includes>
>     <excludes>*/target/*</excludes>
>     <message>Changing the Eclipse files versions</message>
> </configuration>
> {code}
>   maven-scm-plugin still could not find the files.
>  
> Second attempt was to change the basedir instead:
>   
> {code:java}
> <configuration>
>         <basedir>${basedir}/..</basedir>
>         <includes>
>             **/META-INF/MANIFEST.MF,
>             **/feature.xml,
>             */.product,
>             **/category.xml
>         </includes>
>         <excludes>*/target/*</excludes>
>         <message>Changing the Eclipse files versions</message>
> </configuration>
> {code}
>  
> This got me an step further because the files where found by the plugin the 
> problem was that maven-scm-plugin was adding the build folder incorrectly in 
> front of the path of the files being added. This was the output:
> {code:java}
> Executing: /bin/sh c cd '/srv/tools/jenkins/jobs/SSP(dev)/workspace/build/..' 
> && 'git' 'add' '-' 'build/module3/category.xml' 'build/module2/feature.xml' 
> 'build/module1/META-INF/MANIFEST.MF' 'build/module4/xyz.product'
> {code}
>   
> After this I tried to also configured the workingDirectory but it only made 
> it worst.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to