[
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
