You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Torsten Curdt (JIRA)" <ji...@codehaus.org> on 2008/10/06 18:10:08 UTC
[jira] Created: (MRELEASE-381) url syntax not good enough for the
git scm provider
url syntax not good enough for the git scm provider
---------------------------------------------------
Key: MRELEASE-381
URL: http://jira.codehaus.org/browse/MRELEASE-381
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: scm
Affects Versions: 2.0-beta-7
Reporter: Torsten Curdt
The problem is that git supports 2 different URL schemes. For the normal RFC 2396 standard and ssh style. So in theory all these styles should work:
normal anonymous absolute:
{code}git clone git://github.com/olamy/scm-git-test-one-module.git{code}
normal anonymous relative:
{code}git clone git://github.com:olamy/scm-git-test-one-module.git{code}
normal developer absolute:
{code}git clone ssh://git@github.com/olamy/scm-git-test-one-module.git{code}
normal developer relative:
{code}git clone ssh://git@github.com/~git/olamy/scm-git-test-one-module{code}
ssh developer absolute:
{code}git clone git@github.com/olamy/scm-git-test-one-module.git{code}
ssh developer relative:
{code}git clone git@github.com:olamy/scm-git-test-one-module{code}
In reality the ssh:// URL is not always supported. (For example github does not). In fact they suggest to use
normal anonymous absolute:
{code}git://github.com/olamy/scm-git-test-one-module.git{code}
ssh developer relative:
{code}git@github.com:olamy/scm-git-test-one-module.git{code}
For the initial checkout the developer will use the command line and set "git@github.com:olamy/scm-git-test-one-module.git" as the remote address. So subsequent commits and tags (from the plugin) can work just fine as the URL does not need to be specified anymore. But when the release plugin checks out the code it will fail if the proper developer url "ssh://git@github.com/~git/olamy/scm-git-test-one-module" (normal developer relative) is set. (As the maven pom seems to expect that format).
There are 3 ways to fix or work around this:
1) Use the normal anonymous URLs for both connections (developer and anonymous) inside the pom. This will confused developers though as the generated site tells the new developers to use the anonymous URL to checkout the code. They will not be able to push if they do.
2) Have the scm/release plugin ignore the developer URL and use the anonymous URL for the checkout. Again this will be confusing on the generated site as the normal developer rel/abs URLs might not be supported.
3) Somehow store the URL in the format "git@github.com:olamy/scm-git-test-one-module" in the pom. The problem is that the POM expects the normal (RFC 2396) format AFAIU.
--
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-381) url syntax not good enough for the
git scm provider
Posted by "John Hampton (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152175#action_152175 ]
John Hampton commented on MRELEASE-381:
---------------------------------------
I think that 3 is the only correct solution. 1 and 2 do not work for private repositories. Private repositories require the git@github.com:olamy/scm-git-test-one-module for both checkout and checkin.
> url syntax not good enough for the git scm provider
> ---------------------------------------------------
>
> Key: MRELEASE-381
> URL: http://jira.codehaus.org/browse/MRELEASE-381
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: Torsten Curdt
> Assignee: Olivier Lamy
> Priority: Blocker
> Fix For: 2.0-beta-9
>
>
> The problem is that git supports 2 different URL schemes. For the normal RFC 2396 standard and ssh style. So in theory all these styles should work:
> normal anonymous absolute:
> {code}git clone git://github.com/olamy/scm-git-test-one-module.git{code}
> normal anonymous relative:
> {code}git clone git://github.com:olamy/scm-git-test-one-module.git{code}
> normal developer absolute:
> {code}git clone ssh://git@github.com/olamy/scm-git-test-one-module.git{code}
> normal developer relative:
> {code}git clone ssh://git@github.com/~git/olamy/scm-git-test-one-module{code}
> ssh developer absolute:
> {code}git clone git@github.com/olamy/scm-git-test-one-module.git{code}
> ssh developer relative:
> {code}git clone git@github.com:olamy/scm-git-test-one-module{code}
> In reality the ssh:// URL is not always supported. (For example github does not). In fact they suggest to use
> normal anonymous absolute:
> {code}git://github.com/olamy/scm-git-test-one-module.git{code}
> ssh developer relative:
> {code}git@github.com:olamy/scm-git-test-one-module.git{code}
> For the initial checkout the developer will use the command line and set "git@github.com:olamy/scm-git-test-one-module.git" as the remote address. So subsequent commits and tags (from the plugin) can work just fine as the URL does not need to be specified anymore. But when the release plugin checks out the code it will fail if the proper developer url "ssh://git@github.com/~git/olamy/scm-git-test-one-module" (normal developer relative) is set. (As the maven pom seems to expect that format).
> There are 3 ways to fix or work around this:
> 1) Use the normal anonymous URLs for both connections (developer and anonymous) inside the pom. This will confused developers though as the generated site tells the new developers to use the anonymous URL to checkout the code. They will not be able to push if they do.
> 2) Have the scm/release plugin ignore the developer URL and use the anonymous URL for the checkout. Again this will be confusing on the generated site as the normal developer rel/abs URLs might not be supported.
> 3) Somehow store the URL in the format "git@github.com:olamy/scm-git-test-one-module" in the pom. The problem is that the POM expects the normal (RFC 2396) format AFAIU.
--
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-381) url syntax not good enough for the
git scm provider
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153771#action_153771 ]
Olivier Lamy commented on MRELEASE-381:
---------------------------------------
Fixed with scm changes and upgrade to scm 1.1.1.
Tested with the very famous project : http://github.com/olamy/scm-git-test-one-module/.
Torsten can you test it too ?
Thanks.
> url syntax not good enough for the git scm provider
> ---------------------------------------------------
>
> Key: MRELEASE-381
> URL: http://jira.codehaus.org/browse/MRELEASE-381
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: Torsten Curdt
> Assignee: Olivier Lamy
> Priority: Blocker
> Fix For: 2.0-beta-9
>
>
> The problem is that git supports 2 different URL schemes. For the normal RFC 2396 standard and ssh style. So in theory all these styles should work:
> normal anonymous absolute:
> {code}git clone git://github.com/olamy/scm-git-test-one-module.git{code}
> normal anonymous relative:
> {code}git clone git://github.com:olamy/scm-git-test-one-module.git{code}
> normal developer absolute:
> {code}git clone ssh://git@github.com/olamy/scm-git-test-one-module.git{code}
> normal developer relative:
> {code}git clone ssh://git@github.com/~git/olamy/scm-git-test-one-module{code}
> ssh developer absolute:
> {code}git clone git@github.com/olamy/scm-git-test-one-module.git{code}
> ssh developer relative:
> {code}git clone git@github.com:olamy/scm-git-test-one-module{code}
> In reality the ssh:// URL is not always supported. (For example github does not). In fact they suggest to use
> normal anonymous absolute:
> {code}git://github.com/olamy/scm-git-test-one-module.git{code}
> ssh developer relative:
> {code}git@github.com:olamy/scm-git-test-one-module.git{code}
> For the initial checkout the developer will use the command line and set "git@github.com:olamy/scm-git-test-one-module.git" as the remote address. So subsequent commits and tags (from the plugin) can work just fine as the URL does not need to be specified anymore. But when the release plugin checks out the code it will fail if the proper developer url "ssh://git@github.com/~git/olamy/scm-git-test-one-module" (normal developer relative) is set. (As the maven pom seems to expect that format).
> There are 3 ways to fix or work around this:
> 1) Use the normal anonymous URLs for both connections (developer and anonymous) inside the pom. This will confused developers though as the generated site tells the new developers to use the anonymous URL to checkout the code. They will not be able to push if they do.
> 2) Have the scm/release plugin ignore the developer URL and use the anonymous URL for the checkout. Again this will be confusing on the generated site as the normal developer rel/abs URLs might not be supported.
> 3) Somehow store the URL in the format "git@github.com:olamy/scm-git-test-one-module" in the pom. The problem is that the POM expects the normal (RFC 2396) format AFAIU.
--
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-381) url syntax not good enough for the
git scm provider
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150068#action_150068 ]
Olivier Lamy commented on MRELEASE-381:
---------------------------------------
1) Looks to be an easy workaround :-).
2) Here we can think about what do we use the devConnection during release:perform to checkout the tagged sources (using the normal connection could be enough ?)
Others, WDYT ?
> url syntax not good enough for the git scm provider
> ---------------------------------------------------
>
> Key: MRELEASE-381
> URL: http://jira.codehaus.org/browse/MRELEASE-381
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: Torsten Curdt
> Assignee: Olivier Lamy
> Priority: Blocker
> Fix For: 2.0-beta-8
>
>
> The problem is that git supports 2 different URL schemes. For the normal RFC 2396 standard and ssh style. So in theory all these styles should work:
> normal anonymous absolute:
> {code}git clone git://github.com/olamy/scm-git-test-one-module.git{code}
> normal anonymous relative:
> {code}git clone git://github.com:olamy/scm-git-test-one-module.git{code}
> normal developer absolute:
> {code}git clone ssh://git@github.com/olamy/scm-git-test-one-module.git{code}
> normal developer relative:
> {code}git clone ssh://git@github.com/~git/olamy/scm-git-test-one-module{code}
> ssh developer absolute:
> {code}git clone git@github.com/olamy/scm-git-test-one-module.git{code}
> ssh developer relative:
> {code}git clone git@github.com:olamy/scm-git-test-one-module{code}
> In reality the ssh:// URL is not always supported. (For example github does not). In fact they suggest to use
> normal anonymous absolute:
> {code}git://github.com/olamy/scm-git-test-one-module.git{code}
> ssh developer relative:
> {code}git@github.com:olamy/scm-git-test-one-module.git{code}
> For the initial checkout the developer will use the command line and set "git@github.com:olamy/scm-git-test-one-module.git" as the remote address. So subsequent commits and tags (from the plugin) can work just fine as the URL does not need to be specified anymore. But when the release plugin checks out the code it will fail if the proper developer url "ssh://git@github.com/~git/olamy/scm-git-test-one-module" (normal developer relative) is set. (As the maven pom seems to expect that format).
> There are 3 ways to fix or work around this:
> 1) Use the normal anonymous URLs for both connections (developer and anonymous) inside the pom. This will confused developers though as the generated site tells the new developers to use the anonymous URL to checkout the code. They will not be able to push if they do.
> 2) Have the scm/release plugin ignore the developer URL and use the anonymous URL for the checkout. Again this will be confusing on the generated site as the normal developer rel/abs URLs might not be supported.
> 3) Somehow store the URL in the format "git@github.com:olamy/scm-git-test-one-module" in the pom. The problem is that the POM expects the normal (RFC 2396) format AFAIU.
--
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] Issue Comment Edited: (MRELEASE-381) url syntax not good
enough for the git scm provider
Posted by "John Hampton (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152175#action_152175 ]
john@cleanoffer.com edited comment on MRELEASE-381 at 10/28/08 12:12 PM:
------------------------------------------------------------------
I think that 3 is the only correct solution. 1 and 2 do not work for github private repositories. Private repositories require the git@github.com:olamy/scm-git-test-one-module for both checkout and checkin.
was (Author: john@cleanoffer.com):
I think that 3 is the only correct solution. 1 and 2 do not work for private repositories. Private repositories require the git@github.com:olamy/scm-git-test-one-module for both checkout and checkin.
> url syntax not good enough for the git scm provider
> ---------------------------------------------------
>
> Key: MRELEASE-381
> URL: http://jira.codehaus.org/browse/MRELEASE-381
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: Torsten Curdt
> Assignee: Olivier Lamy
> Priority: Blocker
> Fix For: 2.0-beta-9
>
>
> The problem is that git supports 2 different URL schemes. For the normal RFC 2396 standard and ssh style. So in theory all these styles should work:
> normal anonymous absolute:
> {code}git clone git://github.com/olamy/scm-git-test-one-module.git{code}
> normal anonymous relative:
> {code}git clone git://github.com:olamy/scm-git-test-one-module.git{code}
> normal developer absolute:
> {code}git clone ssh://git@github.com/olamy/scm-git-test-one-module.git{code}
> normal developer relative:
> {code}git clone ssh://git@github.com/~git/olamy/scm-git-test-one-module{code}
> ssh developer absolute:
> {code}git clone git@github.com/olamy/scm-git-test-one-module.git{code}
> ssh developer relative:
> {code}git clone git@github.com:olamy/scm-git-test-one-module{code}
> In reality the ssh:// URL is not always supported. (For example github does not). In fact they suggest to use
> normal anonymous absolute:
> {code}git://github.com/olamy/scm-git-test-one-module.git{code}
> ssh developer relative:
> {code}git@github.com:olamy/scm-git-test-one-module.git{code}
> For the initial checkout the developer will use the command line and set "git@github.com:olamy/scm-git-test-one-module.git" as the remote address. So subsequent commits and tags (from the plugin) can work just fine as the URL does not need to be specified anymore. But when the release plugin checks out the code it will fail if the proper developer url "ssh://git@github.com/~git/olamy/scm-git-test-one-module" (normal developer relative) is set. (As the maven pom seems to expect that format).
> There are 3 ways to fix or work around this:
> 1) Use the normal anonymous URLs for both connections (developer and anonymous) inside the pom. This will confused developers though as the generated site tells the new developers to use the anonymous URL to checkout the code. They will not be able to push if they do.
> 2) Have the scm/release plugin ignore the developer URL and use the anonymous URL for the checkout. Again this will be confusing on the generated site as the normal developer rel/abs URLs might not be supported.
> 3) Somehow store the URL in the format "git@github.com:olamy/scm-git-test-one-module" in the pom. The problem is that the POM expects the normal (RFC 2396) format AFAIU.
--
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] Issue Comment Edited: (MRELEASE-381) url syntax not good
enough for the git scm provider
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153771#action_153771 ]
olamy edited comment on MRELEASE-381 at 11/11/08 3:18 AM:
-----------------------------------------------------------------
Fixed with scm changes and upgrade to scm 1.1.1.
Tested with the very famous project : http://github.com/olamy/scm-git-test-one-module/.
Torsten can you test it too ? (All necessary SNAPSHOTS deployed)
Thanks.
was (Author: olamy):
Fixed with scm changes and upgrade to scm 1.1.1.
Tested with the very famous project : http://github.com/olamy/scm-git-test-one-module/.
Torsten can you test it too ?
Thanks.
> url syntax not good enough for the git scm provider
> ---------------------------------------------------
>
> Key: MRELEASE-381
> URL: http://jira.codehaus.org/browse/MRELEASE-381
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: Torsten Curdt
> Assignee: Olivier Lamy
> Priority: Blocker
> Fix For: 2.0-beta-9
>
>
> The problem is that git supports 2 different URL schemes. For the normal RFC 2396 standard and ssh style. So in theory all these styles should work:
> normal anonymous absolute:
> {code}git clone git://github.com/olamy/scm-git-test-one-module.git{code}
> normal anonymous relative:
> {code}git clone git://github.com:olamy/scm-git-test-one-module.git{code}
> normal developer absolute:
> {code}git clone ssh://git@github.com/olamy/scm-git-test-one-module.git{code}
> normal developer relative:
> {code}git clone ssh://git@github.com/~git/olamy/scm-git-test-one-module{code}
> ssh developer absolute:
> {code}git clone git@github.com/olamy/scm-git-test-one-module.git{code}
> ssh developer relative:
> {code}git clone git@github.com:olamy/scm-git-test-one-module{code}
> In reality the ssh:// URL is not always supported. (For example github does not). In fact they suggest to use
> normal anonymous absolute:
> {code}git://github.com/olamy/scm-git-test-one-module.git{code}
> ssh developer relative:
> {code}git@github.com:olamy/scm-git-test-one-module.git{code}
> For the initial checkout the developer will use the command line and set "git@github.com:olamy/scm-git-test-one-module.git" as the remote address. So subsequent commits and tags (from the plugin) can work just fine as the URL does not need to be specified anymore. But when the release plugin checks out the code it will fail if the proper developer url "ssh://git@github.com/~git/olamy/scm-git-test-one-module" (normal developer relative) is set. (As the maven pom seems to expect that format).
> There are 3 ways to fix or work around this:
> 1) Use the normal anonymous URLs for both connections (developer and anonymous) inside the pom. This will confused developers though as the generated site tells the new developers to use the anonymous URL to checkout the code. They will not be able to push if they do.
> 2) Have the scm/release plugin ignore the developer URL and use the anonymous URL for the checkout. Again this will be confusing on the generated site as the normal developer rel/abs URLs might not be supported.
> 3) Somehow store the URL in the format "git@github.com:olamy/scm-git-test-one-module" in the pom. The problem is that the POM expects the normal (RFC 2396) format AFAIU.
--
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] Updated: (MRELEASE-381) url syntax not good enough for the
git scm provider
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy updated MRELEASE-381:
----------------------------------
Fix Version/s: (was: 2.0-beta-8)
2.0-beta-9
> url syntax not good enough for the git scm provider
> ---------------------------------------------------
>
> Key: MRELEASE-381
> URL: http://jira.codehaus.org/browse/MRELEASE-381
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: Torsten Curdt
> Assignee: Olivier Lamy
> Priority: Blocker
> Fix For: 2.0-beta-9
>
>
> The problem is that git supports 2 different URL schemes. For the normal RFC 2396 standard and ssh style. So in theory all these styles should work:
> normal anonymous absolute:
> {code}git clone git://github.com/olamy/scm-git-test-one-module.git{code}
> normal anonymous relative:
> {code}git clone git://github.com:olamy/scm-git-test-one-module.git{code}
> normal developer absolute:
> {code}git clone ssh://git@github.com/olamy/scm-git-test-one-module.git{code}
> normal developer relative:
> {code}git clone ssh://git@github.com/~git/olamy/scm-git-test-one-module{code}
> ssh developer absolute:
> {code}git clone git@github.com/olamy/scm-git-test-one-module.git{code}
> ssh developer relative:
> {code}git clone git@github.com:olamy/scm-git-test-one-module{code}
> In reality the ssh:// URL is not always supported. (For example github does not). In fact they suggest to use
> normal anonymous absolute:
> {code}git://github.com/olamy/scm-git-test-one-module.git{code}
> ssh developer relative:
> {code}git@github.com:olamy/scm-git-test-one-module.git{code}
> For the initial checkout the developer will use the command line and set "git@github.com:olamy/scm-git-test-one-module.git" as the remote address. So subsequent commits and tags (from the plugin) can work just fine as the URL does not need to be specified anymore. But when the release plugin checks out the code it will fail if the proper developer url "ssh://git@github.com/~git/olamy/scm-git-test-one-module" (normal developer relative) is set. (As the maven pom seems to expect that format).
> There are 3 ways to fix or work around this:
> 1) Use the normal anonymous URLs for both connections (developer and anonymous) inside the pom. This will confused developers though as the generated site tells the new developers to use the anonymous URL to checkout the code. They will not be able to push if they do.
> 2) Have the scm/release plugin ignore the developer URL and use the anonymous URL for the checkout. Again this will be confusing on the generated site as the normal developer rel/abs URLs might not be supported.
> 3) Somehow store the URL in the format "git@github.com:olamy/scm-git-test-one-module" in the pom. The problem is that the POM expects the normal (RFC 2396) format AFAIU.
--
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] Updated: (MRELEASE-381) url syntax not good enough for the
git scm provider
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy updated MRELEASE-381:
----------------------------------
Priority: Blocker (was: Major)
Assignee: Olivier Lamy
Fix Version/s: 2.0-beta-8
> url syntax not good enough for the git scm provider
> ---------------------------------------------------
>
> Key: MRELEASE-381
> URL: http://jira.codehaus.org/browse/MRELEASE-381
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: Torsten Curdt
> Assignee: Olivier Lamy
> Priority: Blocker
> Fix For: 2.0-beta-8
>
>
> The problem is that git supports 2 different URL schemes. For the normal RFC 2396 standard and ssh style. So in theory all these styles should work:
> normal anonymous absolute:
> {code}git clone git://github.com/olamy/scm-git-test-one-module.git{code}
> normal anonymous relative:
> {code}git clone git://github.com:olamy/scm-git-test-one-module.git{code}
> normal developer absolute:
> {code}git clone ssh://git@github.com/olamy/scm-git-test-one-module.git{code}
> normal developer relative:
> {code}git clone ssh://git@github.com/~git/olamy/scm-git-test-one-module{code}
> ssh developer absolute:
> {code}git clone git@github.com/olamy/scm-git-test-one-module.git{code}
> ssh developer relative:
> {code}git clone git@github.com:olamy/scm-git-test-one-module{code}
> In reality the ssh:// URL is not always supported. (For example github does not). In fact they suggest to use
> normal anonymous absolute:
> {code}git://github.com/olamy/scm-git-test-one-module.git{code}
> ssh developer relative:
> {code}git@github.com:olamy/scm-git-test-one-module.git{code}
> For the initial checkout the developer will use the command line and set "git@github.com:olamy/scm-git-test-one-module.git" as the remote address. So subsequent commits and tags (from the plugin) can work just fine as the URL does not need to be specified anymore. But when the release plugin checks out the code it will fail if the proper developer url "ssh://git@github.com/~git/olamy/scm-git-test-one-module" (normal developer relative) is set. (As the maven pom seems to expect that format).
> There are 3 ways to fix or work around this:
> 1) Use the normal anonymous URLs for both connections (developer and anonymous) inside the pom. This will confused developers though as the generated site tells the new developers to use the anonymous URL to checkout the code. They will not be able to push if they do.
> 2) Have the scm/release plugin ignore the developer URL and use the anonymous URL for the checkout. Again this will be confusing on the generated site as the normal developer rel/abs URLs might not be supported.
> 3) Somehow store the URL in the format "git@github.com:olamy/scm-git-test-one-module" in the pom. The problem is that the POM expects the normal (RFC 2396) format AFAIU.
--
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-381) url syntax not good enough for the
git scm provider
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy closed MRELEASE-381.
---------------------------------
Resolution: Fixed
> url syntax not good enough for the git scm provider
> ---------------------------------------------------
>
> Key: MRELEASE-381
> URL: http://jira.codehaus.org/browse/MRELEASE-381
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: Torsten Curdt
> Assignee: Olivier Lamy
> Priority: Blocker
> Fix For: 2.0-beta-9
>
>
> The problem is that git supports 2 different URL schemes. For the normal RFC 2396 standard and ssh style. So in theory all these styles should work:
> normal anonymous absolute:
> {code}git clone git://github.com/olamy/scm-git-test-one-module.git{code}
> normal anonymous relative:
> {code}git clone git://github.com:olamy/scm-git-test-one-module.git{code}
> normal developer absolute:
> {code}git clone ssh://git@github.com/olamy/scm-git-test-one-module.git{code}
> normal developer relative:
> {code}git clone ssh://git@github.com/~git/olamy/scm-git-test-one-module{code}
> ssh developer absolute:
> {code}git clone git@github.com/olamy/scm-git-test-one-module.git{code}
> ssh developer relative:
> {code}git clone git@github.com:olamy/scm-git-test-one-module{code}
> In reality the ssh:// URL is not always supported. (For example github does not). In fact they suggest to use
> normal anonymous absolute:
> {code}git://github.com/olamy/scm-git-test-one-module.git{code}
> ssh developer relative:
> {code}git@github.com:olamy/scm-git-test-one-module.git{code}
> For the initial checkout the developer will use the command line and set "git@github.com:olamy/scm-git-test-one-module.git" as the remote address. So subsequent commits and tags (from the plugin) can work just fine as the URL does not need to be specified anymore. But when the release plugin checks out the code it will fail if the proper developer url "ssh://git@github.com/~git/olamy/scm-git-test-one-module" (normal developer relative) is set. (As the maven pom seems to expect that format).
> There are 3 ways to fix or work around this:
> 1) Use the normal anonymous URLs for both connections (developer and anonymous) inside the pom. This will confused developers though as the generated site tells the new developers to use the anonymous URL to checkout the code. They will not be able to push if they do.
> 2) Have the scm/release plugin ignore the developer URL and use the anonymous URL for the checkout. Again this will be confusing on the generated site as the normal developer rel/abs URLs might not be supported.
> 3) Somehow store the URL in the format "git@github.com:olamy/scm-git-test-one-module" in the pom. The problem is that the POM expects the normal (RFC 2396) format AFAIU.
--
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