You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Josh Peters (JIRA)" <ji...@codehaus.org> on 2008/04/24 16:49:46 UTC
[jira] Created: (MSITE-318) site:deploy unable to utilize UNC paths
site:deploy unable to utilize UNC paths
---------------------------------------
Key: MSITE-318
URL: http://jira.codehaus.org/browse/MSITE-318
Project: Maven 2.x Site Plugin
Issue Type: Bug
Components: site:deploy
Affects Versions: 2.0-beta-6
Environment: Windows XP
Reporter: Josh Peters
Priority: Minor
Currently under windows, a UNC path (even one represented as a file:// URL) cannot be written to. There seems to be something in the guts of Ant and Maven that doesn't understand how to treat UNC paths as valid paths.
In an effort to avoid the "wontfix" status: mapping the UNC path as a network drive is effective but terribly kludgey as a long-term solution. Different developers in an organization _may_ have drives already mapped to something else. Given a vanilla Windows network, UNC paths may be the best choice for deploying sites.
Leaving this as a minor bug since it mainly affects internal projects of an organization, but it is an important one as it can keep folks from adopting Maven for use in corporate environments.
--
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: (MSITE-318) site:deploy unable to utilize UNC
paths
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137756#action_137756 ]
Dennis Lundberg commented on MSITE-318:
---------------------------------------
Josh, is it OK with you if we close this issue now?
> site:deploy unable to utilize UNC paths
> ---------------------------------------
>
> Key: MSITE-318
> URL: http://jira.codehaus.org/browse/MSITE-318
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site:deploy
> Affects Versions: 2.0-beta-6
> Environment: Windows XP
> Reporter: Josh Peters
> Priority: Minor
>
> Currently under windows, a UNC path (even one represented as a file:// URL) cannot be written to. There seems to be something in the guts of Ant and Maven that doesn't understand how to treat UNC paths as valid paths.
> In an effort to avoid the "wontfix" status: mapping the UNC path as a network drive is effective but terribly kludgey as a long-term solution. Different developers in an organization _may_ have drives already mapped to something else. Given a vanilla Windows network, UNC paths may be the best choice for deploying sites.
> Leaving this as a minor bug since it mainly affects internal projects of an organization, but it is an important one as it can keep folks from adopting Maven for use in corporate environments.
--
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: (MSITE-318) site:deploy unable to utilize UNC
paths
Posted by "Josh Peters (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132851#action_132851 ]
Josh Peters commented on MSITE-318:
-----------------------------------
One more thing that may be affecting the issue: the server is a Windows 2000 server.
> site:deploy unable to utilize UNC paths
> ---------------------------------------
>
> Key: MSITE-318
> URL: http://jira.codehaus.org/browse/MSITE-318
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site:deploy
> Affects Versions: 2.0-beta-6
> Environment: Windows XP
> Reporter: Josh Peters
> Priority: Minor
>
> Currently under windows, a UNC path (even one represented as a file:// URL) cannot be written to. There seems to be something in the guts of Ant and Maven that doesn't understand how to treat UNC paths as valid paths.
> In an effort to avoid the "wontfix" status: mapping the UNC path as a network drive is effective but terribly kludgey as a long-term solution. Different developers in an organization _may_ have drives already mapped to something else. Given a vanilla Windows network, UNC paths may be the best choice for deploying sites.
> Leaving this as a minor bug since it mainly affects internal projects of an organization, but it is an important one as it can keep folks from adopting Maven for use in corporate environments.
--
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: (MSITE-318) site:deploy unable to utilize UNC
paths
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132853#action_132853 ]
Benjamin Bentmann commented on MSITE-318:
-----------------------------------------
bq. It should be noted that the share name contains a space
Just in case: Did you already try "file://///SERVERNAME/PATH TO FOLDER" as the URL, i.e. with unescaped spaces? I know that's not RFC-compliant but as fas as I can tell Maven is currently not paying too much attention towards URL decoding/encoding when switching from File to URL and vice-versa.
> site:deploy unable to utilize UNC paths
> ---------------------------------------
>
> Key: MSITE-318
> URL: http://jira.codehaus.org/browse/MSITE-318
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site:deploy
> Affects Versions: 2.0-beta-6
> Environment: Windows XP
> Reporter: Josh Peters
> Priority: Minor
>
> Currently under windows, a UNC path (even one represented as a file:// URL) cannot be written to. There seems to be something in the guts of Ant and Maven that doesn't understand how to treat UNC paths as valid paths.
> In an effort to avoid the "wontfix" status: mapping the UNC path as a network drive is effective but terribly kludgey as a long-term solution. Different developers in an organization _may_ have drives already mapped to something else. Given a vanilla Windows network, UNC paths may be the best choice for deploying sites.
> Leaving this as a minor bug since it mainly affects internal projects of an organization, but it is an important one as it can keep folks from adopting Maven for use in corporate environments.
--
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: (MSITE-318) site:deploy unable to utilize UNC paths
Posted by "Josh Peters (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Peters closed MSITE-318.
-----------------------------
Resolution: Won't Fix
Sorry for keeping this issue open after discovering it's a Wagon issue. Marking as "Won't Fix" since the issue isn't in this plugin.
> site:deploy unable to utilize UNC paths
> ---------------------------------------
>
> Key: MSITE-318
> URL: http://jira.codehaus.org/browse/MSITE-318
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site:deploy
> Affects Versions: 2.0-beta-6
> Environment: Windows XP
> Reporter: Josh Peters
> Priority: Minor
>
> Currently under windows, a UNC path (even one represented as a file:// URL) cannot be written to. There seems to be something in the guts of Ant and Maven that doesn't understand how to treat UNC paths as valid paths.
> In an effort to avoid the "wontfix" status: mapping the UNC path as a network drive is effective but terribly kludgey as a long-term solution. Different developers in an organization _may_ have drives already mapped to something else. Given a vanilla Windows network, UNC paths may be the best choice for deploying sites.
> Leaving this as a minor bug since it mainly affects internal projects of an organization, but it is an important one as it can keep folks from adopting Maven for use in corporate environments.
--
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: (MSITE-318) site:deploy unable to utilize UNC
paths
Posted by "Josh Peters (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132850#action_132850 ]
Josh Peters commented on MSITE-318:
-----------------------------------
Here's my "mvn -v"
Maven version: 2.0.9
Java version: 1.6.0_03
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
Maven site plugin version 2.0-beta-6.
Here's an example of the error message I've gotten:
"
[INFO] [site:deploy]
file://///SERVERNAME/PATH%20TO%20FOLDER - Session: Disconnecting
file://///SERVERNAME/PATH%20TO%20FOLDER - Session: Disconnected
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error uploading site
Embedded error: Repository path \\SERVERNAME\PATH%20TO%20FOLDER does not exist, and cannot be created.
"
It should be noted that the share name contains a space. I've tried both "mvn site-deploy" without the folder existing and with it existing.
Thanks for any help. If this is a real bug (and not a ID10T error) I hope it can be fixed :)
> site:deploy unable to utilize UNC paths
> ---------------------------------------
>
> Key: MSITE-318
> URL: http://jira.codehaus.org/browse/MSITE-318
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site:deploy
> Affects Versions: 2.0-beta-6
> Environment: Windows XP
> Reporter: Josh Peters
> Priority: Minor
>
> Currently under windows, a UNC path (even one represented as a file:// URL) cannot be written to. There seems to be something in the guts of Ant and Maven that doesn't understand how to treat UNC paths as valid paths.
> In an effort to avoid the "wontfix" status: mapping the UNC path as a network drive is effective but terribly kludgey as a long-term solution. Different developers in an organization _may_ have drives already mapped to something else. Given a vanilla Windows network, UNC paths may be the best choice for deploying sites.
> Leaving this as a minor bug since it mainly affects internal projects of an organization, but it is an important one as it can keep folks from adopting Maven for use in corporate environments.
--
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: (MSITE-318) site:deploy unable to utilize UNC
paths
Posted by "Josh Peters (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132877#action_132877 ]
Josh Peters commented on MSITE-318:
-----------------------------------
Okay, that does work. It's a shame that the proper encoding is failing, but I can work with this as a temporary fix.
I guess I'll look to file this as a bug in Wagon then.
> site:deploy unable to utilize UNC paths
> ---------------------------------------
>
> Key: MSITE-318
> URL: http://jira.codehaus.org/browse/MSITE-318
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site:deploy
> Affects Versions: 2.0-beta-6
> Environment: Windows XP
> Reporter: Josh Peters
> Priority: Minor
>
> Currently under windows, a UNC path (even one represented as a file:// URL) cannot be written to. There seems to be something in the guts of Ant and Maven that doesn't understand how to treat UNC paths as valid paths.
> In an effort to avoid the "wontfix" status: mapping the UNC path as a network drive is effective but terribly kludgey as a long-term solution. Different developers in an organization _may_ have drives already mapped to something else. Given a vanilla Windows network, UNC paths may be the best choice for deploying sites.
> Leaving this as a minor bug since it mainly affects internal projects of an organization, but it is an important one as it can keep folks from adopting Maven for use in corporate environments.
--
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: (MSITE-318) site:deploy unable to utilize UNC
paths
Posted by "Joerg Schaible (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132833#action_132833 ]
Joerg Schaible commented on MSITE-318:
--------------------------------------
Just as a side note, we deploy our site docs since years with various M2 and site-plugin versions using a file URL for an UNC path. Most people that cannot get this work is because they don't know how to build the URL properly:
file://///machine/share/path
- "file://" is the protocol
- "/" is the shortcut for localhost/
- "//machine/share/path" is the UNC path
> site:deploy unable to utilize UNC paths
> ---------------------------------------
>
> Key: MSITE-318
> URL: http://jira.codehaus.org/browse/MSITE-318
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site:deploy
> Affects Versions: 2.0-beta-6
> Environment: Windows XP
> Reporter: Josh Peters
> Priority: Minor
>
> Currently under windows, a UNC path (even one represented as a file:// URL) cannot be written to. There seems to be something in the guts of Ant and Maven that doesn't understand how to treat UNC paths as valid paths.
> In an effort to avoid the "wontfix" status: mapping the UNC path as a network drive is effective but terribly kludgey as a long-term solution. Different developers in an organization _may_ have drives already mapped to something else. Given a vanilla Windows network, UNC paths may be the best choice for deploying sites.
> Leaving this as a minor bug since it mainly affects internal projects of an organization, but it is an important one as it can keep folks from adopting Maven for use in corporate environments.
--
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: (MSITE-318) site:deploy unable to utilize UNC
paths
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132747#action_132747 ]
Dennis Lundberg commented on MSITE-318:
---------------------------------------
Can you please share with us the configurations that are not working for you.
> site:deploy unable to utilize UNC paths
> ---------------------------------------
>
> Key: MSITE-318
> URL: http://jira.codehaus.org/browse/MSITE-318
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site:deploy
> Affects Versions: 2.0-beta-6
> Environment: Windows XP
> Reporter: Josh Peters
> Priority: Minor
>
> Currently under windows, a UNC path (even one represented as a file:// URL) cannot be written to. There seems to be something in the guts of Ant and Maven that doesn't understand how to treat UNC paths as valid paths.
> In an effort to avoid the "wontfix" status: mapping the UNC path as a network drive is effective but terribly kludgey as a long-term solution. Different developers in an organization _may_ have drives already mapped to something else. Given a vanilla Windows network, UNC paths may be the best choice for deploying sites.
> Leaving this as a minor bug since it mainly affects internal projects of an organization, but it is an important one as it can keep folks from adopting Maven for use in corporate environments.
--
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: (MSITE-318) site:deploy unable to
utilize UNC paths
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132853#action_132853 ]
bentmann edited comment on MSITE-318 at 4/28/08 8:57 AM:
------------------------------------------------------------------
bq. It should be noted that the share name contains a space
Just in case: Did you already try "file://///SERVERNAME/PATH TO FOLDER" as the URL, i.e. with unescaped spaces? I know that's not RFC-compliant but as far as I can tell the [{{FileWagon}}|http://maven.apache.org/wagon/wagon-providers/wagon-file/xref/org/apache/maven/wagon/providers/file/FileWagon.html#100] is currently not paying too much attention towards URL decoding/encoding when switching from File to URL and vice-versa.
was (Author: bentmann):
bq. It should be noted that the share name contains a space
Just in case: Did you already try "file://///SERVERNAME/PATH TO FOLDER" as the URL, i.e. with unescaped spaces? I know that's not RFC-compliant but as fas as I can tell Maven is currently not paying too much attention towards URL decoding/encoding when switching from File to URL and vice-versa.
> site:deploy unable to utilize UNC paths
> ---------------------------------------
>
> Key: MSITE-318
> URL: http://jira.codehaus.org/browse/MSITE-318
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site:deploy
> Affects Versions: 2.0-beta-6
> Environment: Windows XP
> Reporter: Josh Peters
> Priority: Minor
>
> Currently under windows, a UNC path (even one represented as a file:// URL) cannot be written to. There seems to be something in the guts of Ant and Maven that doesn't understand how to treat UNC paths as valid paths.
> In an effort to avoid the "wontfix" status: mapping the UNC path as a network drive is effective but terribly kludgey as a long-term solution. Different developers in an organization _may_ have drives already mapped to something else. Given a vanilla Windows network, UNC paths may be the best choice for deploying sites.
> Leaving this as a minor bug since it mainly affects internal projects of an organization, but it is an important one as it can keep folks from adopting Maven for use in corporate environments.
--
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