B
Bronco
Guest
Mike has a point. However, personally I find working in multiple projects a bit of a hassle. You have to keep the config's in sync, switch back and forth betweeen the projects. If I setup something I put everything in one project, including testcode, test data, build scripts etc. Also put everything in scm (my motto: if it's not in SCM, it doesn't exist) With Jenkins in place you can unittest/compile your code with every commit to your SCM, and there are plugins for eclipse/jenkins to make those errors visible as well. Andrew's setup works perfectly wel in my experience.
Continue reading...
Continue reading...