Build Jira from source. Error: " The filename or extension is too long ".

[Łukasz Sokół]

I have problem with building Jira from source. After 12 minutes, the build failed with following error: "An Ant BuildException has occured: Javadoc failed: java.io.IOException: Cannot run program "C:\Program Files\Java\jdk1.6.0_31\bin\javadoc.exe": CreateProcess error=206, The filename or extension is too long."

I'm trying to move catalogue with javadoc to shortest path and result was the same.

Any idea ?

[Damien Brock]

i faced this issue on windows 7, then i tried Long Path Tool which works very well

[Juan Miller]

Long path tool can solve your problem easily. It can delete, copy, move and bulk rename long path files or locked files easily. Try it, It is very useful.

[bonnie jones]

Hey, I too use the Long Path Tool! :D Works every time :)

[robertvo]

I would suggest you using Long Path Tool to eliminate this issue in other occassions.

[steven kor]

Try " Long Path Tool " useful in situations where you see these error messages: Cannot read from source file or disk, there has been a sharing violation, cannot delete file or folder, the file name you specified is not valid or too long, the source or destination file may be in use and many other file managing errors that you encounter in your computing use.

[Łukasz Sokół]

Do you know where is Build.xml ? In catalogue where is installed Java are several "Build.xml" files and they are very similar.

[Radu Dumitriu]

NTFS has a limit of 255 chars for a file name.

Add 'useexternalfile="yes"' to the javadoc task, it may work.

[JamieA]

That's not really true... NTFS has a 32k limit. Stuff built with the CRT generally have max path of 260 chars. But, do you need to build the javadoc? Probably not...

[Radu Dumitriu]

You are talking about path, not file name, I guess ....

[Łukasz Sokół]

I don't see any build.xml which can used as build script.

I build source in command line.

Jira 5.0, sdk 1.6, Windows 7

[Radu Dumitriu]

It is a maven build AFAIK. You should see what pom fails, most probably it should have a maven-antrun-plugin with something like:

<configuration>
<tasks>
<javadoc ...................>

Or, install a Linux VM and build on it ....

[Łukasz Sokół]

ok I give up. I don't have this text in pom files. May I should add this text...

[JamieA]

@Radu, sorry yes, I didn't read your answer properly.

[eden]

I would suggest Long path Tool to manage your proble,I use long path tool when occur problem to me.

[cristopher]

You can use “Long Path Tool” !It will help you.

[Roksolana]

Long Path Tool help me a lot when i have an issue like file deleting or renaming the file. Also good to use if file name and file extension is too long.

[Samantha Chloe]

“Long Path Tool” is very helpful for this error !
You can use to solve this problem

[johnraf]

“Long Path Tool” is very helpful.

[albina elvira]

I used to have similar problems too, but after using
"long path tool" You can use to solve this problem.

[johnraf]

I used to have similar problems too, but after using
"long path tool" You can use to solve this problem.

[stepan raisa]

“Long Path Tool” is very helpful for this error !
best solution for your problem.

[aiden_carter]

Long path tool is the very good program for error, unlock solution.
Try it and solve your problem.
I used long path tool and I solve my error, unlock problem solution.