Github user indrgun commented on the pull request:
https://github.com/apache/maven-scm/pull/31#issuecomment-179412574
Without the patch, using version 1.9.1 of maven-scm-api and
maven-scm-provider-gitexe, I am running into git add error that is different:
```
[INFO
Github user indrgun commented on the pull request:
https://github.com/apache/maven-scm/pull/31#issuecomment-178941997
why the git add append the subdir path again to the pom.xml? This does not
happen with maven release prepare goal.
```
[WARNING] Ignoring unrecognized
Github user indrgun commented on the pull request:
https://github.com/apache/maven-scm/pull/31#issuecomment-178940863
You are right the patch #31 does not work probably if the pom.xml is not in
the root directory of git repo.
I removed pomFileName in pom.xml and also in the
Github user indrgun commented on the pull request:
https://github.com/apache/maven-scm/pull/31#issuecomment-178935559
I am getting same error:
```
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd
/scratch/jenkinsci-ws/workspace/apic-int
Github user indrgun commented on the pull request:
https://github.com/apache/maven-scm/pull/31#issuecomment-178930429
There are actually 2 separate patches: patch #31 and patch #26. Which one
has the problem?
I applied your patch #31 and I tried it and got same error
Github user indrgun commented on the pull request:
https://github.com/apache/maven-scm/pull/31#issuecomment-178926905
The command line supplied to Jenkins maven release field in maven project:
"-Dresume=false -Prelease-profile release:prepare-with-pom release:perfor
Github user indrgun commented on the pull request:
https://github.com/apache/maven-scm/pull/31#issuecomment-178907308
I do not specify pomFileName for maven release prepare plugin here.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user indrgun commented on the pull request:
https://github.com/apache/maven-scm/pull/31#issuecomment-178900813
With maven-release-plugin version 2.5 and dependency on
maven-scm-provider-gitexe version 1.9.1 including that configuration (our
pom.xml is not on root of git
Github user indrgun commented on the pull request:
https://github.com/apache/maven-scm/pull/31#issuecomment-178854338
HI sergei,
I patched the latest scm with the patch on top, built it as version
1.9.5-beta-1 and use it with version 2.5 maven release plugin as such
Github user indrgun commented on the pull request:
https://github.com/apache/maven-scm/pull/31#issuecomment-152661620
When can this PR be approved and merged? We have migrated from SVN to
Git/Stash but we can't use release-with-pom anymore and the team is not happy.
---
If
10 matches
Mail list logo
