This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
I have started a project with few of my friends. I know in time it will go large and may go out of control. So for better management I want to make separate build environments like 1 for development , one for testing another for production. How to do that ? what kind of hardware / tool do I need ?
It's better to create a product that can be identical in all 3 environments. Otherwise when you have a production error, you're not testing the same app when you go to debug it, and there's a very real danger that sooner or later the wrong edition of a product will be deployed to the wrong environment (speaking from sad experience).
It takes a little more care to create a "universal" app. You can use JNDI and deployment descriptors to setup and inject information into web apps. Configuration files are the usual mode for stand-alone Java apps, with properties files being the favorites.
An IDE is no substitute for an Intelligent Developer.
Here is what we do. We use Subversion to store our source code - everyone checks their changes into it. You could use git or some other source control management system, it doesn't matter which one you use, but you need one. Subversion runs on its own server (not on one of our desktops). Then we have Jenkins which will perform builds from the sources stored in Subversion. Those are our "official" builds which are then possibly subjected to integration testing, and ultimately go into production. We never place into production nay code that a developer compiler or his or her desktop. Again, Jenkins, and the builds that Jenkins performs, runs on its own server. It can be the same machine as where Subversion is hosted.