Karnati Sudhakar wrote:
I think this is the lamest doubt in the world of J2EE
Nah. We get lots of lamer stuff than that.
Maven is good because once you get a whole raft full of projects going, you don't clutter up your system with duplicate copies of common jars.
Another approach I've used is to create a "lib" project that holds master copies of common jars and have the child projects copy from there when I do a build. I use this approach with Ant sometimes.