macOS NetBeans dependency chain management: Part 2

[wrldwzrd89]

A continuation of this older thread. Remember the dependency chain issues I was having? Well, I found a workaround. It's not ideal, but it does work.

Let's say you have 3 projects:

• Project A, the main project (dependent on project B)
• Project B, a class library (dependent on Project C)
• Project C, a resource library for Project B

So you set up the dependencies, so project A depends on B, which in turn depends on C. Everything compiles okay, but it doesn't run properly. Why? Project C's jar file never gets copied to the libs folder for Project A.

Workaround: Add Project C as a direct dependency of Project A (even though it really isn't), and everything will work as expected.