[
https://issues.apache.org/jira/browse/SCM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963722#comment-17963722
]
ASF GitHub Bot commented on SCM-932:
------------------------------------
jira-importer commented on issue #1160:
URL: https://github.com/apache/maven-scm/issues/1160#issuecomment-2964649287
**[Alex
Harui](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aharui)**
commented
Apache Royale is working from a code base donated by a corporation that did
not support Maven. The repo has a bunch of subfolders. Two are used to
pre-process generated source code (from Antlr and some other similar tools).
Those two subfolders seem to need to be released separately before we run 'mvn
release' on the top-level pom. The parent in the pom for these two subfolders
is not the main pom in the repo.
We have so far elected not to move these two subfolders to their own repos
because build technologies other than Maven are supported for legacy reasons.
Running 'mvn release' in the subfolder seems to be working other than this
issue, but we'll see as we go further down the road.
> JGit does not commit files in fileset based in subfolder
> --------------------------------------------------------
>
> Key: SCM-932
> URL: https://issues.apache.org/jira/browse/SCM-932
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-jgit
> Affects Versions: 1.11.2
> Reporter: Alex Harui
> Priority: Major
> Attachments: SCM-932-Test.patch, SCM-932.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If `mvn release` is run in a subfolder, the changed files are relative to the
> subfolder and not the repo root and `maven-scm-provider-jgit` does not
> compute the correct path and thus the files are not added and committed.
> For example, a git repo is created at `repo-root`
> {code:java}
> repo-root/pom.xml
> repo-root/unparented-submodule/pom.xml {code}
> The user does:
> {code:java}
> cd repo-root/unparented-submodule
> mvn release:prepare {code}
> A `git status` will show that `unparented-submodule/pom.xml` is changed and
> not staged for commit. That's because the fileset's basedir is
> `unpainted-submodule` and the relative path is just `pom.xml`.
> `maven-scm-provider-jgit` 1.12.1 tries to stage 'pom.xml' not
> `unparented-submodule/pom.xml` and since repo-root/pom.xml has not changed,
> nothing is in the commit and `unparented-submodule/pom.xml` remains un-staged.
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
