Hello, I hope this forum is the right place for this question...
This is the scenario:
Project A-> depends on Project B->depends on ProjectC
Each project has its own /lib and /config.
Up to this point, for successful execution, each project's /lib and /config have to be manually copied into its parent Project. And each project has to be built individually. As you could see, this process is becoming cumbersome as more projects are being added. I've read about Maven but can't quite wrap my head around it, and not sure if Maven will actually help the situation or open up more can of worms.
Could you please recommend a better way? Also, i'm using Netbeans. Any pointers will be greatly appreciated.
Maven handles these types of dependencies very well. It really is worth learning just for this one capability. And the integration with Eclipse keeps getting better; I assume that the same is happening with NetBeans.
After you have read Better Builds with Maven and Maven: The Complete Reference, and have created a few projects that use Maven, write a Maven plugin. Once you have written the plugin you will have a better feeling for how Maven works and it will no longer appear to be a "black box". Also, do your builds from the command line to get used to working with Maven. Only after you become familiar with with running Maven on the command line should you use the Maven capabilities built into your IDE. I keep on having to help too many of my co-workers who refuse to follow this advice and run into issues when the IDE tries to be helpful and instead messes things up.