[
https://issues.apache.org/jira/browse/MNG-6159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6159:
-------------------------------
Fix Version/s: (was: 3.6.x-candidate)
3.6.1
> Child path adjustments break git scm urls
> -----------------------------------------
>
> Key: MNG-6159
> URL: https://issues.apache.org/jira/browse/MNG-6159
> Project: Maven
> Issue Type: Improvement
> Reporter: Christian Aistleitner
> Priority: Minor
> Fix For: 3.6.1
>
> Attachments: 0001-Skip-child-path-adjustments-for-git-scm-urls.patch
>
>
> While child path adjustments make sense for some scms, child path
> adjustment break git scm urls.
> Consider a parent project Foo which is available at
> http://github.com:ExampleOrg/Foo and uses
> [...]
> <developerConnection>scm:git:g...@github.com:ExampleOrg/${project.artifactId}.git</developerConnection>
> [...]
>
> If a project Bar in the repo at http://github.com:ExampleOrg/Bar uses Foo as
> parent and inherits <developerConnection>, it ends up with the value
>
> scm:git:g...@github.com:ExampleOrg/${project.artifactId}.git/Foo
>
> which is not usable due to the child path adjustment.
> While this bit us, we're not alone. Looking at the reported URLs, child path
> adjustments for git scm urls are also caused issues in these places:
> https://github.com/vorburger/MariaDB4j/issues/43
> https://gist.github.com/escowles/f46d158cdaf955e34282
> http://transcripts.jboss.org/channel/irc.freenode.org/%23aerogear/2014/%23aerogear.2014-07-03.log.html
> (search for "not a valid repository name")
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
