Github user sergei-ivanov commented on the issue:
https://github.com/apache/maven-scm/pull/31
@YogiKhan Unfortunately, I haven't got the resources to actively work on
this issue. I've already spent an awful lot of time debugging it, and still
have no clear idea where exact
Github user sergei-ivanov commented on the issue:
https://github.com/apache/maven-scm/pull/31
I need help with that from the Apache team.
In the original version of `GitCheckInCommand`, just before committing, the
list of files to be committed was passed to `git add`. This ensured
Github user sergei-ivanov commented on the issue:
https://github.com/apache/maven-scm/pull/31
@YogiKhan you will need to build this PR branch of `maven-scm`, and then
build `maven-release` project against it. Then you'll need to update the
version of `maven-release-plugin` in
Github user sergei-ivanov commented on the issue:
https://github.com/apache/maven-scm/pull/31
@olamy I've done a rebase onto the latest master and re-pushed the changes
to the PR branch.
_However_, there still exists an unresolved regression (as pointed out by
@in
Github user sergei-ivanov commented on the pull request:
https://github.com/apache/maven-scm/pull/31#issuecomment-178984032
Maven passes `release-pom.xml` and `pom.xml` to the `GitCheckInCommand`.
Previously, it would attempt to `git add` both before doing the `git commit`.
Naturally
Github user sergei-ivanov commented on the pull request:
https://github.com/apache/maven-scm/pull/31#issuecomment-178931065
I haven't tried #26 and I do not think it makes any difference here. I
think the problem is with #31 in the way it tries to calculate the set of files
Github user sergei-ivanov commented on the pull request:
https://github.com/apache/maven-scm/pull/31#issuecomment-178930248
What if you remove the default 'perform' execution completely and instead
append the parameter to `` as
`-DpomFileName=apic_int/comp/ifm_apic_re
Github user sergei-ivanov commented on the pull request:
https://github.com/apache/maven-scm/pull/31#issuecomment-178929085
Actually I thnk you may be onto something here. It looks like the patch may
have a problem with relative paths, when it is not run from the root of the git
Github user sergei-ivanov commented on the pull request:
https://github.com/apache/maven-scm/pull/31#issuecomment-178918591
What is the command line you are using, and what is the directory you are
running it from, and where is the root of your git repo (my guess is
`/scratch
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
Github user sergei-ivanov commented on the pull request:
https://github.com/apache/maven-scm/pull/31#issuecomment-141722548
Rebased the PR on top of the current master
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
GitHub user sergei-ivanov opened a pull request:
https://github.com/apache/maven-scm/pull/31
SCM-706 finer-grained handling of file rename status for gitexe provider...
..., rename source is not added to the set of files for commit operation
anymore
This is an
12 matches
Mail list logo
