You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2008/06/07 15:06:14 UTC
[jira] Commented: (MSITE-318) site:deploy unable to utilize UNC
paths
[ 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