[jira] Commented: (MSITE-601) Period added to URL prevents proper cloning with Mercurial

2011-08-02 Thread Leon Blakey (JIRA)

[ 
https://jira.codehaus.org/browse/MSITE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274806#comment-274806
 ] 

Leon Blakey commented on MSITE-601:
---

This is an issue with Google's new namespace overlap though. A projects new 
main repo and main site are at the exact same URL. Its also an issue with 
Google seeing . or / or any extra character for that matter as a separate file 
or mode.

BTW, tried to get that fixed, got denied: 
http://code.google.com/p/support/issues/detail?id=5628

It seems like it would be a lot easier to normalize URL's in the site plugin 
than to convince Google to handle extra character's in a URL.

More importantly: Why does the site plugin *need* to add a /./ to the URL? I 
can't think of a use case for that.

> Period added to URL prevents proper cloning with Mercurial
> --
>
> Key: MSITE-601
> URL: https://jira.codehaus.org/browse/MSITE-601
> Project: Maven 2.x and 3.x Site Plugin
>  Issue Type: Bug
>  Components: site:deploy
>Affects Versions: 3.0-beta-3
> Environment: Javac 7 on Fedora Linux 15, Mercurial 1.9
>Reporter: Leon Blakey
>Priority: Critical
>
> I deploy my Maven site over Mercurial on Google Code. I use this configuration
> {code:xml}
>   
>   
>   MYPROJECT.googlecode.com
>   scm:hg:https://code.google.com/p/MYPROJECT.site/
>   
> {code}
> And a standard  in settings.xml
> {code:xml}
>   
>   MYPROJECT.googlecode.com
>   USERNAME
>   PASSWORD
>   
> {code}
> However when running site:deploy it decides that it should add a dot to the 
> URL, meaning it tries to execute this command
> EXECUTING: /bin/sh -c cd /tmp && hg clone -r tip 
> https://USERNAME:passw...@code.google.com/p/MYPROJECT.site//. 
> /tmp/wagon-scm1348091978.checkout
> Which on Google and other repositories gives a 404 since the file . (look at 
> the end of the URL) doesn't exist. Why is that period there? Is it coming 
> from Maven Site or the Mercurial plugin (I'm assuming here)? Can it get 
> removed>

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (MSITE-601) Period added to URL prevents proper cloning with Mercurial

2011-08-01 Thread Lukas Theussl (JIRA)

[ 
https://jira.codehaus.org/browse/MSITE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274799#comment-274799
 ] 

Lukas Theussl commented on MSITE-601:
-

See linked issues and discussion at 
http://maven.40175.n5.nabble.com/How-to-avoid-part-of-URL-during-site-deployment-td3307034.html.
 As I said there, a dot component is a valid part of a URL, I see no reason for 
a repo or server to throw a 404.

> Period added to URL prevents proper cloning with Mercurial
> --
>
> Key: MSITE-601
> URL: https://jira.codehaus.org/browse/MSITE-601
> Project: Maven 2.x and 3.x Site Plugin
>  Issue Type: Bug
>  Components: site:deploy
>Affects Versions: 3.0-beta-3
> Environment: Javac 7 on Fedora Linux 15, Mercurial 1.9
>Reporter: Leon Blakey
>Priority: Critical
>
> I deploy my Maven site over Mercurial on Google Code. I use this configuration
> {code:xml}
>   
>   
>   MYPROJECT.googlecode.com
>   scm:hg:https://code.google.com/p/MYPROJECT.site/
>   
> {code}
> And a standard  in settings.xml
> {code:xml}
>   
>   MYPROJECT.googlecode.com
>   USERNAME
>   PASSWORD
>   
> {code}
> However when running site:deploy it decides that it should add a dot to the 
> URL, meaning it tries to execute this command
> EXECUTING: /bin/sh -c cd /tmp && hg clone -r tip 
> https://USERNAME:passw...@code.google.com/p/MYPROJECT.site//. 
> /tmp/wagon-scm1348091978.checkout
> Which on Google and other repositories gives a 404 since the file . (look at 
> the end of the URL) doesn't exist. Why is that period there? Is it coming 
> from Maven Site or the Mercurial plugin (I'm assuming here)? Can it get 
> removed>

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (MSITE-601) Period added to URL prevents proper cloning with Mercurial

2011-07-30 Thread Leon Blakey (JIRA)

[ 
https://jira.codehaus.org/browse/MSITE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274676#comment-274676
 ] 

Leon Blakey commented on MSITE-601:
---

Tested snapshot version 3.0-beta-4-20110712.115141-32, still present. It has 
some interesting output though

{quote}
scm:hg:https://code.google.com/p/MYPROJECT.site/ - Session: Opened  
Pushing /home/lordquackstar/pircbotx-hg/target/site
   >>> to scm:hg:https://code.google.com/p/MYPROJECT.site/./
Uploading: ./ to scm:hg:https://code.google.com/p/MYPROJECT.site/

EXECUTING: /bin/sh -c cd /home/lordquackstar/pircbotx-hg/. && hg locate
Removing /tmp/wagon-scm2121267578.checkout
EXECUTING: /bin/sh -c cd /tmp && hg clone -r tip 
https://USERNAME:passw...@code.google.com/p/MYPROJECT.site//./ 
/tmp/wagon-scm2121267578.checkout
{quote}

It seems that somewhere an extra / is added to the URL, then it thinks that its 
pushing to ./ . Thats a really strange way to treat the URL. 

> Period added to URL prevents proper cloning with Mercurial
> --
>
> Key: MSITE-601
> URL: https://jira.codehaus.org/browse/MSITE-601
> Project: Maven 2.x and 3.x Site Plugin
>  Issue Type: Bug
>  Components: site:deploy
>Affects Versions: 3.0-beta-3
> Environment: Javac 7 on Fedora Linux 15, Mercurial 1.9
>Reporter: Leon Blakey
>Priority: Critical
>
> I deploy my Maven site over Mercurial on Google Code. I use this configuration
> {code:xml}
>   
>   
>   MYPROJECT.googlecode.com
>   scm:hg:https://code.google.com/p/MYPROJECT.site/
>   
> {code}
> And a standard  in settings.xml
> {code:xml}
>   
>   MYPROJECT.googlecode.com
>   USERNAME
>   PASSWORD
>   
> {code}
> However when running site:deploy it decides that it should add a dot to the 
> URL, meaning it tries to execute this command
> EXECUTING: /bin/sh -c cd /tmp && hg clone -r tip 
> https://USERNAME:passw...@code.google.com/p/MYPROJECT.site//. 
> /tmp/wagon-scm1348091978.checkout
> Which on Google and other repositories gives a 404 since the file . (look at 
> the end of the URL) doesn't exist. Why is that period there? Is it coming 
> from Maven Site or the Mercurial plugin (I'm assuming here)? Can it get 
> removed>

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (MSITE-601) Period added to URL prevents proper cloning with Mercurial

2011-07-29 Thread Lukas Theussl (JIRA)

[ 
https://jira.codehaus.org/browse/MSITE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274654#comment-274654
 ] 

Lukas Theussl commented on MSITE-601:
-

Can you try maven-site-plugin-3.0-SNAPSHOT?

> Period added to URL prevents proper cloning with Mercurial
> --
>
> Key: MSITE-601
> URL: https://jira.codehaus.org/browse/MSITE-601
> Project: Maven 2.x and 3.x Site Plugin
>  Issue Type: Bug
>  Components: site:deploy
>Affects Versions: 3.0-beta-3
> Environment: Javac 7 on Fedora Linux 15, Mercurial 1.9
>Reporter: Leon Blakey
>Priority: Critical
>
> I deploy my Maven site over Mercurial on Google Code. I use this configuration
> 
>   
>   
>   MYPROJECT.googlecode.com
>   scm:hg:https://code.google.com/p/MYPROJECT.site/
>   
> 
> And a standard  in settings.xml
> 
>   
>   MYPROJECT.googlecode.com
>   USERNAME
>   PASSWORD
>   
> 
> However when running site:deploy it decides that it should add a dot to the 
> URL, meaning it tries to execute this command
> EXECUTING: /bin/sh -c cd /tmp && hg clone -r tip 
> https://USERNAME:passw...@code.google.com/p/MYPROJECT.site//. 
> /tmp/wagon-scm1348091978.checkout
> Which on Google and other repositories gives a 404 since the file . (look at 
> the end of the URL) doesn't exist. Why is that period there? Is it coming 
> from Maven Site or the Mercurial plugin (I'm assuming here)? Can it get 
> removed>

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira