[
https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333413#comment-333413
]
Ernst de Haan commented on SCM-709:
-----------------------------------
Reproduction steps for my issue:
# Have a small Maven project:
#- root folder is project A, containing modules B and C
#- subfolder B contains module B
#- subfolder C contains module C
#- module C has module B as parent
# Module A defines a Git repository in an {{<scm>}} tag
# Go into module C's subdirectory
# Execute {{mvn release:prepare release:perform}
Expected:
- Tag is created on repository _R_ defined in the {{<scm>}} tag in module A
Actual:
- Tagging fails, because the release plugin attempts to create a tag on _R_/_C_
(where _R_ is the repository defined in the {{<scm>}} tag in module A and _C_
is the name of module C)
Workaround:
- Copy the {{<scm>}} tag from module A's POM to module C's POM
> REGRESSION: git status doesn't work if repository root is not the working
> directory
> -----------------------------------------------------------------------------------
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
> Affects Versions: 1.8, 1.8.1
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Priority: Blocker
> Attachments:
> 0001-use-new-File-.toURI-to-fix-handling-of-paths-with-sp.patch
>
>
> SCM-686 introduced the {{--porcelain}} option to make the {{status}} result
> language independend.
> Without the {{--porcelain}} option files were listed relative to the working
> directory, but with {{--porcelain}} files are listed relative to the
> repository root. In most cases these are the same, but not always.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
