[BUILDTOOLS-359] BuildTools crashing when patching Created: 18/Oct/17  Updated: 19/Oct/17  Resolved: 19/Oct/17

Status: Resolved
Project: BuildTools
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Hugo Hammarberg Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: BuildTools, patcher
Environment:

Hardware: Raspberry Pi 3

OS: Raspbian


Attachments: Text File BuildTools.log.txt    

 Description   

When running the BuildTools for the latest revision (or using --rev 1.12.2, it's all the same), it returns with an error when applying a patch on ".AppleDouble" saying "Exception in thread "main" java.io.FileNotFoundException: CraftBukkit/nms-patches/.AppleDouble (Is a directory)".

I've found no way to work around the problem so it's probably an error in the source code.

 

Log is attached



 Comments   
Comment by md_5 [ 19/Oct/17 ]

The latest version should fix the issue without all that

Comment by Hugo Hammarberg [ 19/Oct/17 ]

The steps of solution:

  1. Open a terminal or ssh
  2. sudo nano /etc/netatalk/AppleVolumes.default
  3. Go to the bottom of the file and find the line ":DEFAULT:" and add to the end of that line a comma (",") followed by "noadouble". No parentheses or quotation marks of course.
  4. cd /path/to/spigot/folder
  5. find ./ -depth -name ".DS_Store" -exec rm {} \; 
  6. find ./ -depth -name ".AppleDouble" -exec rm -Rf {} \; 
  7. And that's it. BuildTools.jar should run just fine.
Comment by Hugo Hammarberg [ 19/Oct/17 ]

The filesystem is ext3, not nfs. But it must be because I have netatalk installed, I see that now. Thank you for linking that wikipedia article. I feel awkward not to have looked it up first.

I will find a solution and post it here in the comments so that others who might have the same problem can find it.

Comment by md_5 [ 18/Oct/17 ]

https://en.wikipedia.org/wiki/AppleSingle_and_AppleDouble_formats

Please don’t run buildtools on an nfs drive, not currently supported.

Generated at Thu Mar 27 22:52:51 UTC 2025 using Jira 10.3.3#10030003-sha1:d220e3fefc8dfc6d47f522d3b9a20c1455e12b7b.