Depends on how you organize the team and the work.
- Does the team work on one project
- What kind of team members do you have?
For a marketing internet site your team members
will have a different qualification than for
e.g. business application with uses web technology
- How many developers work together on one topic
Our approach:
- One web server instance for 2-3 developers.
This is not a fixed rule. If the downtime of the
server grows to big for the other workers on this
server the team is split further.
- Minimize the number of machines that run the
server. Ideally there is just one machine.
(install servlet engine and Apache once with several
instances)
- Use version management (cvs) for every part of the
project (config files, jsp's, beans, images, ...)
- Use scripts to setup a web server instance from the
repository with minimal manual interactions.
- Use these script to integrate often (Up to several
times a day)
As we havn't migrated our scripts from JServ to Tomcat
I can't give you specific advice for tomcat.
> -----Ursprüngliche Nachricht-----
> Von: BacardiWasabi [mailto:[EMAIL PROTECTED]]
> Gesendet: Dienstag, 13. November 2001 09:53
> An: Tomcat Users List
> Betreff: Tomcat for Large Team Size
>
>
> Here is my situation
>
> We have a large team size 20-30. We willbe using
> Tomcat 4.0 on 2000.
>
> a) Do u install stand alone tomcat on each developer
> machine? Will it be a good idea? In that case, config
> files (web.xml/servler.xml etc) should be in synch
> with others. This may lead to problems
>
> b) Or Can we have one instance of tomcat running
> central. And each developer sharring one port. so that
> he(developer) can restart/restop that port. How do u
> achieve this
>
> c) Any other good method to implement tomcat on large
> size project
>
> and last any link to good docs on Team Development
> using Tomcat
>
> thanks
>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Find the one for you at Yahoo! Personals
> http://personals.yahoo.com
>
> --
> To unsubscribe: <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>
>
>
>
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
