Github user sergei-ivanov commented on the pull request:
https://github.com/apache/maven-scm/pull/31#issuecomment-178898208
@indrgun
I tested it on a vanilla project, which did not have any major config
alterations for the release plugin.
I wonder if the following bit of configuration kicks in and messes up the
relative paths:
```
<configuration>
<pomFileName>apic_int/comp/ifm_apic_rest/pom.xml</pomFileName>
</configuration>
```
Because you can see that Maven actually changes to that directory, but then
passes to the git command a path to the pom, which is relative to the top-level
project directory.
Does `mvn release:prepare` (not `prepare-with-pom`) work for you with the
same version of m-r-p and the same settings, but without the SCM provider
patch? I have a feeling that the issue you are facing may be of a different
nature than this patch is trying to address.
Alternatively, you may try prefixing the `pomFileName` path with
`${project.basedir}`, which will turn it into an absolute path.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
