This week's book giveaway is in the Testing forum.
We're giving away four copies of Data Structures the Fun Way: An Amusing Adventure with Coffee-Filled Examples and have Jeremy Kubica on-line!
See this thread for details.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Devaka Cooray
  • Ron McLeod
  • Jeanne Boyarsky
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
  • Tim Holloway
Bartenders:
  • Martijn Verburg
  • Frits Walraven
  • Himai Minh

J2ee remote development

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
can some one please shed some light on the ways to do software development using open source software (apache tomcat, CVS etc.) for J2EE development remotely. The scenario is that there are two teams that are on remote locations and now how can they coordinate the software development? There could be more than two teams later.

thanks in advance for atleast the effort in replying the right way.
thank,
RK
 
Ranch Hand
Posts: 74
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
1. Use CVS as the source control and keep it in a seperate server that is available for all the team
2. Standardise the IDE like Eclipse and Plugins for eclipse
3. Provide document for integrating the ide with CVS
4. Install the app/web server in the server machine
5. Write some script to build the application when ever any change in the source (Auto deploy)
 
Ranch Hand
Posts: 1608
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Baiju Varugese:
1. Use CVS as the source control and keep it in a seperate server that is available for all the team
2. Standardise the IDE like Eclipse and Plugins for eclipse
3. Provide document for integrating the ide with CVS
4. Install the app/web server in the server machine
5. Write some script to build the application when ever any change in the source (Auto deploy)



1. Use Subversion for the Revision Control System (RCS) and a server that is available from all current and future locations - perhaps over VPN. Do not use CVS unless you wish to impose unwarranted and unnecessary burden on your develoeprs.
2. Standardise the IDE e.g. Intellij IDEA so that developers are productive Also standardlise on source code style(CheckStyle, IDEA code analysis), dependency management (Ivy+Ant), unit testing (JUnit, JTiger or TestNG)
5. Use a continuous integration system like Luntbuid.
 
Raj Kotari
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Baiju & Tony,
thanks for the quick reply.
RK,
 
reply
    Bookmark Topic Watch Topic
  • New Topic