[jira] (MNG-5605) ssh-wagon hangs
[ https://jira.codehaus.org/browse/MNG-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349961#comment-349961 ] Jason van Zyl commented on MNG-5605: That should, I didn't know if you used it as an extension or dropped the JARs in your installation. Nothing else around transport has changed, most notably the Aether code where the error is originating. Honestly this is not high on my priority list (which is not to say there aren't other committers for whom this is important) as I don't use the SSH code path. Ideally if we can get a self-contained test that uses something like MINA SSHD and can demontrate the problem it will be easier to fix, and more importantly stays fixed. > ssh-wagon hangs > --- > > Key: MNG-5605 > URL: https://jira.codehaus.org/browse/MNG-5605 > Project: Maven > Issue Type: Bug > Components: Deployment >Affects Versions: 3.2.1 >Reporter: Frank Cornelis >Priority: Blocker > > When releasing (using maven-release-plugin) via Maven 3.1.1 everything works > as expected. When doing the same via Maven 3.2.1, ssh-wagon all of the sudden > hangs on the second ssh upload. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5663) [regression] resolution of import-scoped transitive dependencies ignores additional repositories
[
https://jira.codehaus.org/browse/MNG-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349969#comment-349969
]
Geoffrey De Smet commented on MNG-5663:
---
Might be the cause of https://issues.jboss.org/browse/DROOLS-553
> [regression] resolution of import-scoped transitive dependencies ignores
> additional repositories
>
>
> Key: MNG-5663
> URL: https://jira.codehaus.org/browse/MNG-5663
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies
>Affects Versions: 3.2.2
>Reporter: Fred Bricon
>
> We (JBoss) use BOM poms extensively, notably in a number of project
> archetypes or project examples available via JBoss Tools and Red Hat
> Developer Studio . Some of these BOM poms (and their dependencies) are
> available from a dedicated Maven repository
> (http://maven.repository.redhat.com/techpreview/all/).
> Maven 3.2.2 introduced a regression that breaks resolution of these BOM
> dependencies, by ignoring additional repositories during artifact resolution.
> {noformat}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> foo
> bar
> 0.0.1-SNAPSHOT
>
>
>
> org.jboss.bom.wfk
>
> jboss-javaee-6.0-with-tools
> 2.4.0-redhat-2
> pom
> import
>
>
>
>
>
> redhat-techpreview-all-repository
>
> http://maven.repository.redhat.com/techpreview/all/
>
>
>
> {noformat}
> yields :
> {noformat}
> ➊bar mvn compile
> [INFO] Scanning for projects...
> Downloading:
> http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-javaee-6.0-with-tools/2.4.0-redhat-2/jboss-javaee-6.0-with-tools-2.4.0-redhat-2.pom
> Downloaded:
> http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-javaee-6.0-with-tools/2.4.0-redhat-2/jboss-javaee-6.0-with-tools-2.4.0-redhat-2.pom
> (8 KB at 5.1 KB/sec)
> Downloading:
> http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-wfk-bom-parent/2.4.0-redhat-2/jboss-wfk-bom-parent-2.4.0-redhat-2.pom
> Downloaded:
> http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-wfk-bom-parent/2.4.0-redhat-2/jboss-wfk-bom-parent-2.4.0-redhat-2.pom
> (7 KB at 6.8 KB/sec)
> Downloading:
> http://repo.maven.apache.org/maven2/org/jboss/spec/jboss-javaee-6.0/3.0.2.Final-redhat-4/jboss-javaee-6.0-3.0.2.Final-redhat-4.pom
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project foo:bar:0.0.1-SNAPSHOT
> (/Users/fbricon/Dev/workspaces/runtime-hosted/bar/pom.xml) has 2 errors
> [ERROR] Non-resolvable import POM: Could not find artifact
> org.jboss.spec:jboss-javaee-6.0:pom:3.0.2.Final-redhat-4 in central
> (http://repo.maven.apache.org/maven2) @
> org.jboss.bom.wfk:jboss-javaee-6.0-with-tools:[unknown-version],
> /Users/fbricon/Dev/maven/repository/org/jboss/bom/wfk/jboss-javaee-6.0-with-tools/2.4.0-redhat-2/jboss-javaee-6.0-with-tools-2.4.0-redhat-2.pom,
> line 42, column 25 -> [Help 2]
> [ERROR] 'dependencies.dependency.version' for
> javax.enterprise:cdi-api:jar is missing. @ line 27, column 15
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> ➊bar
> {noformat}
> This kind of resolution used to work in maven 3.2.1 and before. The missing
> pom is available at
> http://maven.repository.redhat.com/techpreview/all/org/jboss/spec/jboss-javaee-6.0/3.0.2.Final-redhat-4/jboss-javaee-6.0-3.0.2.Final-redhat-4.pom
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MRELEASE-875) release:prepare does not commit pom.xml if not in the git root
[ https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349980#comment-349980 ] Dominik Bartholdi commented on MRELEASE-875: same issue with maven-release-plugin 2.5 and the jgit provider 1.9 only moving the pom.xml to the root of the repo solves the issue > release:prepare does not commit pom.xml if not in the git root > -- > > Key: MRELEASE-875 > URL: https://jira.codehaus.org/browse/MRELEASE-875 > Project: Maven Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.5 > Environment: git 1.9.0 >Reporter: john ten Den > > When the project pom.xml is not in the Git project root (f.e. in the "src" > directory) the pom.xml not committed and pushed (before tagging) > Commit of the pom.xml during release:prepare works fine if it is in the / > (root) of the git repository > Using the pom.xml in a subdirectory worked well with version 2.4.2 using git > 1.7. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5663) [regression] resolution of import-scoped transitive dependencies ignores additional repositories
[
https://jira.codehaus.org/browse/MNG-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349983#comment-349983
]
Mark Ingram commented on MNG-5663:
--
Pull requests:
https://github.com/apache/maven/pull/23
https://github.com/apache/maven-integration-testing/pull/8
Integration tests pass and confirmed that the example POM above works with this
build.
> [regression] resolution of import-scoped transitive dependencies ignores
> additional repositories
>
>
> Key: MNG-5663
> URL: https://jira.codehaus.org/browse/MNG-5663
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies
>Affects Versions: 3.2.2
>Reporter: Fred Bricon
>
> We (JBoss) use BOM poms extensively, notably in a number of project
> archetypes or project examples available via JBoss Tools and Red Hat
> Developer Studio . Some of these BOM poms (and their dependencies) are
> available from a dedicated Maven repository
> (http://maven.repository.redhat.com/techpreview/all/).
> Maven 3.2.2 introduced a regression that breaks resolution of these BOM
> dependencies, by ignoring additional repositories during artifact resolution.
> {noformat}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> foo
> bar
> 0.0.1-SNAPSHOT
>
>
>
> org.jboss.bom.wfk
>
> jboss-javaee-6.0-with-tools
> 2.4.0-redhat-2
> pom
> import
>
>
>
>
>
> redhat-techpreview-all-repository
>
> http://maven.repository.redhat.com/techpreview/all/
>
>
>
> {noformat}
> yields :
> {noformat}
> ➊bar mvn compile
> [INFO] Scanning for projects...
> Downloading:
> http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-javaee-6.0-with-tools/2.4.0-redhat-2/jboss-javaee-6.0-with-tools-2.4.0-redhat-2.pom
> Downloaded:
> http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-javaee-6.0-with-tools/2.4.0-redhat-2/jboss-javaee-6.0-with-tools-2.4.0-redhat-2.pom
> (8 KB at 5.1 KB/sec)
> Downloading:
> http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-wfk-bom-parent/2.4.0-redhat-2/jboss-wfk-bom-parent-2.4.0-redhat-2.pom
> Downloaded:
> http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-wfk-bom-parent/2.4.0-redhat-2/jboss-wfk-bom-parent-2.4.0-redhat-2.pom
> (7 KB at 6.8 KB/sec)
> Downloading:
> http://repo.maven.apache.org/maven2/org/jboss/spec/jboss-javaee-6.0/3.0.2.Final-redhat-4/jboss-javaee-6.0-3.0.2.Final-redhat-4.pom
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project foo:bar:0.0.1-SNAPSHOT
> (/Users/fbricon/Dev/workspaces/runtime-hosted/bar/pom.xml) has 2 errors
> [ERROR] Non-resolvable import POM: Could not find artifact
> org.jboss.spec:jboss-javaee-6.0:pom:3.0.2.Final-redhat-4 in central
> (http://repo.maven.apache.org/maven2) @
> org.jboss.bom.wfk:jboss-javaee-6.0-with-tools:[unknown-version],
> /Users/fbricon/Dev/maven/repository/org/jboss/bom/wfk/jboss-javaee-6.0-with-tools/2.4.0-redhat-2/jboss-javaee-6.0-with-tools-2.4.0-redhat-2.pom,
> line 42, column 25 -> [Help 2]
> [ERROR] 'dependencies.dependency.version' for
> javax.enterprise:cdi-api:jar is missing. @ line 27, column 15
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> ➊bar
> {noformat}
> This kind of resolution used to work in maven 3.2.1 and before. The missing
> pom is available at
> http://maven.repository.redhat.com/techpreview/all/org/jboss/spec/jboss-javaee-6.0/3.0.2.Final-redhat-4/jboss-javaee-6.0-3.0.2.Final-redhat-4.pom
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SCM-765) jgit provider commits changes with system user instead of passed username
[
https://jira.codehaus.org/browse/SCM-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349986#comment-349986
]
Karl-Heinz Marbaise commented on SCM-765:
-
seemed to be fixed by git commit:
[037ba69bced119de1618526e6977940908eeb7bc|https://github.com/apache/maven-scm/commit/037ba69bced119de1618526e6977940908eeb7bc]
> jgit provider commits changes with system user instead of passed username
> -
>
> Key: SCM-765
> URL: https://jira.codehaus.org/browse/SCM-765
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
>Affects Versions: 1.9
>Reporter: Dominik Bartholdi
>Assignee: Dominik Bartholdi
> Fix For: 1.10
>
>
> When using the jgit provider over http, it allows to define username /
> password like this:
> {code}
> mvn release:prepare release:perform -Dresume=false -Dusername=myuser
> -Dpassword=XXX
> {code}
> But the commit will not be done with the given user but with the system user
> who started the process, instead the passed user is only used for transport.
> Well that might be fine in the first thought, but it will mean in the git
> repository it is not recorded who really did make the release.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SCM-765) jgit provider commits changes with system user instead of passed username
[
https://jira.codehaus.org/browse/SCM-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed SCM-765.
---
Resolution: Fixed
> jgit provider commits changes with system user instead of passed username
> -
>
> Key: SCM-765
> URL: https://jira.codehaus.org/browse/SCM-765
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
>Affects Versions: 1.9
>Reporter: Dominik Bartholdi
>Assignee: Dominik Bartholdi
> Fix For: 1.9.1
>
>
> When using the jgit provider over http, it allows to define username /
> password like this:
> {code}
> mvn release:prepare release:perform -Dresume=false -Dusername=myuser
> -Dpassword=XXX
> {code}
> But the commit will not be done with the given user but with the system user
> who started the process, instead the passed user is only used for transport.
> Well that might be fine in the first thought, but it will mean in the git
> repository it is not recorded who really did make the release.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SCM-765) jgit provider commits changes with system user instead of passed username
[
https://jira.codehaus.org/browse/SCM-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349987#comment-349987
]
Dominik Bartholdi commented on SCM-765:
---
yeah, I finally got my commit credentials back working - thanks for checking :)
> jgit provider commits changes with system user instead of passed username
> -
>
> Key: SCM-765
> URL: https://jira.codehaus.org/browse/SCM-765
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
>Affects Versions: 1.9
>Reporter: Dominik Bartholdi
>Assignee: Dominik Bartholdi
> Fix For: 1.9.1
>
>
> When using the jgit provider over http, it allows to define username /
> password like this:
> {code}
> mvn release:prepare release:perform -Dresume=false -Dusername=myuser
> -Dpassword=XXX
> {code}
> But the commit will not be done with the given user but with the system user
> who started the process, instead the passed user is only used for transport.
> Well that might be fine in the first thought, but it will mean in the git
> repository it is not recorded who really did make the release.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
