[jira] Created: (SCM-574) GitCheckInCommand fails on empty changed files list
GitCheckInCommand fails on empty changed files list --- Key: SCM-574 URL: http://jira.codehaus.org/browse/SCM-574 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-git Affects Versions: 1.4 Reporter: Andrey Paramonov Attachments: GitCheckInCommand.patch If there is no file in the Git index "git checkin" returns exit code 1, which causes failed CheckInScmResult. Because of that "mvn release:branch" always fails for Git repositories (see MRELEASE-579). We shouldn't probably call "git checkin" if there is nothing to check in. After I applied the attached patch, "mvn release:branch" succeeded. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-590) release:perform fails on Git repository relative path
[
http://jira.codehaus.org/browse/MRELEASE-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232732#action_232732
]
Andrey Paramonov commented on MRELEASE-590:
---
It's used by _release:prepare_ though.
> release:perform fails on Git repository relative path
> -
>
> Key: MRELEASE-590
> URL: http://jira.codehaus.org/browse/MRELEASE-590
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.0
> Environment: MacOS X 10.6.4, Maven 2.1.0
>Reporter: Andrey Paramonov
>Assignee: Mark Struberg
> Fix For: 2.0
>
> Attachments: pom.xml
>
>
> Running release:perform on relative Git path
> {code}
>
> scm:git:file://.
> scm:git:file://.
> scm:git:file://.
>
> {code}
> fails with the error
> {code}
> [INFO] [release:perform]
> [INFO] Checking out the project to perform the release ...
> [INFO] Executing: /bin/sh -c cd /Users/andrey/projects/demos/gitmaven/target
> && git clone file://. /Users/andrey/projects/demos/gitmaven/target/checkout
> [INFO] Working directory: /Users/andrey/projects/demos/gitmaven/target
> [ERROR] The git-clone command failed.
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] Unable to checkout from SCM
> Provider message:
> The git-clone command failed.
> Command output:
> fatal: '.' does not appear to be a git repository
> fatal: The remote end hung up unexpectedly
> {code}
> It works fine for absolute path though.
> Also to note, when I run the same clone command in the shell, it works
> without any problem
> {code}
> $ git clone file://. /Users/andrey/projects/demos/gitmaven/target/checkout
> Initialized empty Git repository in
> /Users/andrey/projects/demos/gitmaven/target/checkout/.git/
> remote: Counting objects: 100, done.
> remote: Compressing objects: 100% (89/89), done.
> remote: Total 100 (delta 38), reused 0 (delta 0)
> Receiving objects: 100% (100/100), 9.52 KiB, done.
> Resolving deltas: 100% (38/38), done.
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRELEASE-590) release:perform fails on Git repository relative path
[
http://jira.codehaus.org/browse/MRELEASE-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Paramonov closed MRELEASE-590.
-
Resolution: Not A Bug
Fix Version/s: 2.0
Using *localCheckout* parameter fixed the problem
{code}
org.apache.maven.plugins
maven-release-plugin
true
{code}
> release:perform fails on Git repository relative path
> -
>
> Key: MRELEASE-590
> URL: http://jira.codehaus.org/browse/MRELEASE-590
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.0
> Environment: MacOS X 10.6.4, Maven 2.1.0
>Reporter: Andrey Paramonov
>Assignee: Mark Struberg
> Fix For: 2.0
>
> Attachments: pom.xml
>
>
> Running release:perform on relative Git path
> {code}
>
> scm:git:file://.
> scm:git:file://.
> scm:git:file://.
>
> {code}
> fails with the error
> {code}
> [INFO] [release:perform]
> [INFO] Checking out the project to perform the release ...
> [INFO] Executing: /bin/sh -c cd /Users/andrey/projects/demos/gitmaven/target
> && git clone file://. /Users/andrey/projects/demos/gitmaven/target/checkout
> [INFO] Working directory: /Users/andrey/projects/demos/gitmaven/target
> [ERROR] The git-clone command failed.
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] Unable to checkout from SCM
> Provider message:
> The git-clone command failed.
> Command output:
> fatal: '.' does not appear to be a git repository
> fatal: The remote end hung up unexpectedly
> {code}
> It works fine for absolute path though.
> Also to note, when I run the same clone command in the shell, it works
> without any problem
> {code}
> $ git clone file://. /Users/andrey/projects/demos/gitmaven/target/checkout
> Initialized empty Git repository in
> /Users/andrey/projects/demos/gitmaven/target/checkout/.git/
> remote: Counting objects: 100, done.
> remote: Compressing objects: 100% (89/89), done.
> remote: Total 100 (delta 38), reused 0 (delta 0)
> Receiving objects: 100% (100/100), 9.52 KiB, done.
> Resolving deltas: 100% (38/38), done.
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MRELEASE-590) release:perform fails on Git repository relative path
[
http://jira.codehaus.org/browse/MRELEASE-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Paramonov reopened MRELEASE-590:
---
According to the error message, the failed operation was clone, and cloning
from present directory makes perfect sense in Git, and it actually works well
in this plugin when you specify absolute path to the present directory.
According to SCM-444 the present directory syntax also make sense for other
Git/Maven users.
Can you please explain what you mean by Git provider? As I noted before the
following command works fine in Git itself:
git clone file://. target/checkout
and SCM plugin was also updated to support relative paths. Plus, since
release:prepare works as expected, your Git provider definitely supports
relative paths in check in operation. If it doesn't support them in check out,
then it's a bug.
> release:perform fails on Git repository relative path
> -
>
> Key: MRELEASE-590
> URL: http://jira.codehaus.org/browse/MRELEASE-590
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.0
> Environment: MacOS X 10.6.4, Maven 2.1.0
>Reporter: Andrey Paramonov
>Assignee: Mark Struberg
> Attachments: pom.xml
>
>
> Running release:perform on relative Git path
> {code}
>
> scm:git:file://.
> scm:git:file://.
> scm:git:file://.
>
> {code}
> fails with the error
> {code}
> [INFO] [release:perform]
> [INFO] Checking out the project to perform the release ...
> [INFO] Executing: /bin/sh -c cd /Users/andrey/projects/demos/gitmaven/target
> && git clone file://. /Users/andrey/projects/demos/gitmaven/target/checkout
> [INFO] Working directory: /Users/andrey/projects/demos/gitmaven/target
> [ERROR] The git-clone command failed.
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] Unable to checkout from SCM
> Provider message:
> The git-clone command failed.
> Command output:
> fatal: '.' does not appear to be a git repository
> fatal: The remote end hung up unexpectedly
> {code}
> It works fine for absolute path though.
> Also to note, when I run the same clone command in the shell, it works
> without any problem
> {code}
> $ git clone file://. /Users/andrey/projects/demos/gitmaven/target/checkout
> Initialized empty Git repository in
> /Users/andrey/projects/demos/gitmaven/target/checkout/.git/
> remote: Counting objects: 100, done.
> remote: Compressing objects: 100% (89/89), done.
> remote: Total 100 (delta 38), reused 0 (delta 0)
> Receiving objects: 100% (100/100), 9.52 KiB, done.
> Resolving deltas: 100% (38/38), done.
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-590) release:perform fails on Git repository relative path
release:perform fails on Git repository relative path
-
Key: MRELEASE-590
URL: http://jira.codehaus.org/browse/MRELEASE-590
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: perform
Affects Versions: 2.0
Environment: MacOS X 10.6.4, Maven 2.1.0
Reporter: Andrey Paramonov
Attachments: pom.xml
Running release:perform on relative Git path
{code}
scm:git:file://.
scm:git:file://.
scm:git:file://.
{code}
fails with the error
{code}
[INFO] [release:perform]
[INFO] Checking out the project to perform the release ...
[INFO] Executing: /bin/sh -c cd /Users/andrey/projects/demos/gitmaven/target &&
git clone file://. /Users/andrey/projects/demos/gitmaven/target/checkout
[INFO] Working directory: /Users/andrey/projects/demos/gitmaven/target
[ERROR] The git-clone command failed.
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Unable to checkout from SCM
Provider message:
The git-clone command failed.
Command output:
fatal: '.' does not appear to be a git repository
fatal: The remote end hung up unexpectedly
{code}
It works fine for absolute path though.
Also to note, when I run the same clone command in the shell, it works without
any problem
{code}
$ git clone file://. /Users/andrey/projects/demos/gitmaven/target/checkout
Initialized empty Git repository in
/Users/andrey/projects/demos/gitmaven/target/checkout/.git/
remote: Counting objects: 100, done.
remote: Compressing objects: 100% (89/89), done.
remote: Total 100 (delta 38), reused 0 (delta 0)
Receiving objects: 100% (100/100), 9.52 KiB, done.
Resolving deltas: 100% (38/38), done.
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRESOURCES-87) Test resource doesn't override main resource
Test resource doesn't override main resource
Key: MRESOURCES-87
URL: http://jira.codehaus.org/browse/MRESOURCES-87
Project: Maven 2.x Resources Plugin
Issue Type: Bug
Affects Versions: 2.3
Environment: Apache Maven 2.1.0 (r755702; 2009-03-18 15:10:27-0400)
Java version: 1.6.0_07
Reporter: Andrey Paramonov
Priority: Minor
I have two files:
{{src/main/resources/resource.xml}}
{{src/test/resources/resource.xml}}
and following block in the pom.xml:
{code}
src/main/resources
test
src/test/resources
{code}
When I run {{mvn clean package}}, I want the file from {{src/main/resources}}
to be packaged. When I run {{mvn clean package -P test}}, I want the file from
{{src/test/resources}} to be packaged. Unfortunately, that doesn't happen.
However, when I add {{filtering}} to profiled resource:
{code}
src/test/resources
true
{code}
it works. So two questions:
* is it a bug that overriding strategy is triggered by filtering tag?
* if so, which behavior is correct: always override resource or never?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
