[ http://jira.codehaus.org/browse/WAGON-42?page=comments#action_64161 ] 

Joerg Schaible commented on WAGON-42:
-------------------------------------

This might be a manifestation of 
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4403166. Although Sun claims 
the bug is fixed, a lot of people face something different. We had these 
problems with Weblogic! When the server exploded the deployed app, some of the 
nested files exceeded this limit and could no longer be found.

> wagon-scm (svn provider) - large paths under windows breaks download.
> ---------------------------------------------------------------------
>
>          Key: WAGON-42
>          URL: http://jira.codehaus.org/browse/WAGON-42
>      Project: wagon
>         Type: Bug

>   Components: wagon-scm
>     Versions: 1.0-alpha-6
>     Reporter: Joakim Erdfelt
>     Assignee: Henry S. Isidro
>     Priority: Critical
>      Fix For: 1.0-beta-1

>
>   Time Spent: 4 hours
>    Remaining: 0 minutes
>
> I have a deep path in windows, plus a repository housed in svn.
> When performing a 'mvn compile', it fails with not finding the artifact.
> Using mvn --debug shows no error message from wagon-scm (svn).
> If I go into the target/checkout/.... directory, i see an empty directory 
> with the '.svn' working directory.
> performing a 'svn update .' in that directory reveals the reason ...
> [EMAIL PROTECTED] 
> /c/code/mergere/amex/AXP-EntBuildEnv/tools/branches/mergere-discovery-wizard/mergere-discovery-core/target/checkout/org/apache/maven/repository/maven-repository-indexer/1.0-SNAPSHOT
> $ svn update .
> svn: Can't open file 
> '.svn/text-base/maven-repository-indexer-1.0-20060418.201022-1.jar.md5.svn-base':
>  File name too long
> I think a general "if windows, and path exceeds maximum, throw error before 
> attempting process' kind of functionality needs to exist.

-- 
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

Reply via email to