A couple of suggestions: 1) All source code must be stored in a source control system (CVS, Subversion, etc.) 2) Everyone checks out the code from the source control system, makes changes, and checks the code back in. 3) Official builds are done directly from the source control system on a machine dedicated to that task. Official builds are never done on a developer's workstation. 4) Developers can use any IDE (or VI if they really want) to edit and test the code, as long as they follow point 2. I, however, am a dictator. I enforce that all developers use the same version of Eclipse with a specific set of plug-ins, and a specific configuration, especially for code formatting and compiler warning levels. I insist that all code checked into the version control system is formatted properly (just hit ctrl-shift-f), that CheckStyle has been run, and that no compiler or CheckStyle warnings are present. This ensures that all code looks reasonably the same, and meets minimal correctness criteria. 5) Developers can deploy the code that they are developing to their own copy of JBoss for their own testing. Note that this is not the production version of JBoss. No developer is ever allowed to update the production version of JBoss. 6) After an official build (see point 3) is done, the build is tested. It helps to have a testing team dedicated to this but in a smaller organization sometimes one or more of the developers must step out of development mode and assume testing mode. If you have developers doing testing, you must make sure that you clearly define what testers do, what developers do, and enforce that while in tester mode that people stick to what tester tasks are. For example, when a tester notices a bug, the tester reports the bug (using Bugzilla or other such tool, for small developments a spreadsheet works fine), the tester never ever fixes the bug. 7) Once the testing is complete and has passed (you need to define what 'passed' means, for example, 'no serious bugs, no more that 5 minor bugs, and 99.99% of the unit tests passed?) then you can deploy the build to the production version of JBoss.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3939562#3939562 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3939562 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
