[
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
