Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Won't Fix
-
1.0-alpha-6
-
None
-
None
Description
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 ...
jerdfelt@EXSISTO /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.
Attachments
Attachments
Issue Links
- depends upon
-
SCM-189 Maven SCM should check if OS is Windows and destination path would exceed Windows maximum before a checkout
- Closed