> I recommend using a clean Tomcat installation that you have full control > over. I usually have a Tomcat for every portal project, e.g. Yep, I use clean Tomcat installation /opt/tomcat is a symlink to /opt/apache-tomcat-5.5.27
> /home/niels/dev/myproject/portal -> the jetspeed portal > /home/niels/dev/myproject/tomcat -> dedicated tomcat installation > It is just a matter of downloading and unzipping tomcat 5.5 and you are > good to go. You can have as many tomcats as you like, as long as you > don't run them at the same time at the same port... Sure! The only one difference is that I use different users for tomcat (nobody) and for code builders (own uid), but they all in same group (devel). And in my case, another one developer can build and deploy J2 code to the same tomcat (f.e. to fix a bug or to add new feature/component). It's also need to change gid for /opt/tomcat (chmod -R g+w *) > Don't forget to adapt you settings.xml for your new tomcat location. Thanks, I'll keep in mind BTW I build Jetspeed successfully using umask to set write permissions for a group. My build script: echo CLEAN THE SOURCE umask ug+rw mvn -e clean >deploy-clean.log echo BEGIN TEST mvn -e -P test >deploy-test.log echo BEGIN TOMCAT DEPLOY mvn -e -P tomcat,full >deploy-tomcat.log echo COMPLETE HTH. Now I try to setup Continuous integration tool. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
