It appears as though Spine 2.0.0+ creates additional folders in the output directory path each consecutive time you export a .json file (which in my iterative workflow, I do a lot).
So this is where my spine file is located:
C:/user/project/assets/scenes/assetname/scene_01/assetname.spine
When I export the first time, a skeleton.json file normally exports successfully in the correct location.
If I still have my scene open, it'll create another project folder in the export path window, like:
C:/Users/user/project/assets/scenes/asset/scene_01/scene_01/skeleton.json
If I export again, it'll look something like:
C:/Users/user/project/assets/scenes/asset/scene_01/scene_01/scene_01/skeleton.json
and so forth...
A coworker has reproduced this issue on a seperate machine using 2.0.02
If I only export once when the file is open, I do not run into this issue.
spine.log:
Spine Launcher 1.8.15-full
Windows 7 x86 6.1
Java 1.7.0-u6-unofficial Oracle Corporation
OpenJDK Server VM
Up to date: 2.0.02
Licensed to: <redacted>
Spine 2.0.02 Professional, LWJGL
NVIDIA Corporation
Quadro 600/PCIe/SSE2
4.4.0
Started.
I should also add this did not happen in version 1.9.17 or before.