[
http://jira.codehaus.org/browse/MNG-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118837
]
Dale King commented on MNG-3255:
--------------------------------
Of course, it is a SVN issue, but it is one that it likely to hit anyone trying
to check out your code due to the really deep paths.
The error message you get from Subversion is not very helpful in explaining
what the problem is.
So all I'm suggesting is that you add a couple sentences on the page that tells
you how to check out Maven to warn people about this problem under Windows.
> Documentation for checking out and build should warn abour long path names on
> Windows
> -------------------------------------------------------------------------------------
>
> Key: MNG-3255
> URL: http://jira.codehaus.org/browse/MNG-3255
> Project: Maven 2
> Issue Type: Improvement
> Components: Documentation: Guides
> Reporter: Dale King
> Fix For: Documentation Deficit
>
>
> I tried checking out the 2.1 maven code and build to see if a problem I was
> seeing with maven eclipse integration was localized to the that integration
> or was caused by the new maven embedder in 2.1 that they use.
> I was checking out into a directory on my desktop under windows. The checkout
> did not complete and had a message:
> svn: Can't open file
> 'maven-components\maven-core\src\test\resources\org\apache\
> maven\extension\test-extension-repo\org\apache\maven\core\test\test-lifecycle-an
> d-artifactHandler\1\.svn\tmp\text-base\test-lifecycle-and-artifactHandler-1.pom.
> md5.svn-base': The system cannot find the path specified.
> The problem is that while windows allows filenames up to 256 characters the
> maximum path length it allows is 260 characters. When you add that path to
> the path to the desktop directory it was too long.
> I was able to check it out to the root directory without problem.
> The guide to building maven should probably mention that for Windows users in
> the part about checking out the source.
--
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
