maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dale King (JIRA)" <>
Subject [jira] Commented: (MNG-3255) Documentation for checking out and build should warn abour long path names on Windows
Date Sun, 06 Jan 2008 19:11:57 GMT


Dale King commented on MNG-3255:

Actually, for the record it really isn't a Subversion issue, but a limitation of Windows.

> Documentation for checking out and build should warn abour long path names on Windows
> -------------------------------------------------------------------------------------
>                 Key: MNG-3255
>                 URL:
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Documentation: Guides
>            Reporter: Dale King
>            Assignee: Vincent Siveton
>             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:
For more information on JIRA, see:


View raw message