APKLib : when file path max length

[GoogleCodeExporter]

On Windows only.

Compilation of my android project fails, the output error is that it can't find 
some android resources.
After verification, the searched files exists.

If i move my project directory to a simplier path, it works.

After investigation :
- it appears that it happens when the path to the android resources exceeds 255 
characters.
- The android resources come from APKLib dependencies that have been exploded 
in target/../groupId/artifactId/...  (really long path)

Original issue reported on code.google.com by lmichen...@gmail.com on 30 Sep 2013 at 9:45

[GoogleCodeExporter]

I've got the same issue

Original comment by marchelo...@gmail.com on 21 Dec 2013 at 10:04

[GoogleCodeExporter]

Test against 3.8.3-SNAPSHOT

If the failure stills occurs then provide a project or link to a project that 
clearly highlights the failure.

Original comment by william....@xandar.com.au on 17 Feb 2014 at 11:17

[GoogleCodeExporter]

I'm closing this.

In 3.9.0 when have done what we can to limit the likelihood of this happening. 
But it gets down to how deep your folder structures are.

Original comment by william....@xandar.com.au on 27 Feb 2014 at 10:41

• Changed state: Fixed

[GoogleCodeExporter]

What your views regarding Long Path Tool. 

Original comment by almens...@gmail.com on 19 Apr 2014 at 10:56

[GoogleCodeExporter]

Long Path Tool appears to only provide a UI replacement for Windows explorer so 
I don't believe it provides any benefit in this scenario.

Original comment by william....@xandar.com.au on 19 Apr 2014 at 11:53