Here are a couple of ideas. Download the version of Jetspeed your customer is using and put it into CVS. We manually decompress the war file and import it into CVS. For examle I would import war contents as "test-portal" Check out the newly create CVS module. This becomes your testing web application. Create a context in Tomcat. It could look something like:
<Context path="/test-portal" docBase="c:\\test\\test-portal" debug="0" /> Add the source files, templates etc. Create a custom properties file. eg Test.properties c:\\test\\test-portal\\WEB-INF\\conf\\Test.properties Create a custom .xreg file (maybe more than one) c:\\test\\test-portal\\WEB-INF\\conf\\test-portlets.xreg Create a custom directory for your templates under C:\agassi\novus-portal-3.1\WEB-INF\templates\vm\portlets\html\test Give each developer of "Action" classes their own three letter identifier so there is no name collision of Action classes when invoked thru the assembler. Build portlet actions in separate module. C:\agassi\novus-portal-3.1\WEB-INF\src\com\test\modules\actions Create portlet actions in the your custom package. Put portlet entries in the new xreg file (See existing xreg file for format) Custom properties go in your properties file plus the following ######################################################## ## ## Your Custom Modules ## ######################################################### module.packages=com.test.modules ######################################################## ## ## Your Logging facility ## ## Customer will have to modify this line in TR.props ## services.LoggingService.facilities=system,ecc,service,portal,test ######################################################### services.LoggingService.test.destination.file=/WEB-INF/log/jetspeed_system.log services.LoggingService.test.className=org.apache.turbine.services.logging.FileLogger services.LoggingService.test.destination.console=true services.LoggingService.test.level=DEBUG Create a CVS BRANCH on the new stuff you are adding. Then when you are finished testing you can check out only the branch and you will have a "WAR" version of the new stuff you created. All you have to do is tell the customer to add your custom properties file to their TurbineResource.properties include = Test.properties Your customer could then just unpack the WAR/JAR you containing the BRANCH files over their existing WAR. As long as you don't overwrite any existing files etc you should be good to go. This is one way of doing it. It the portal site is very complex the customer may not want to do this, however we have found it to work well r, Hugh -----Original Message----- From: Wayne A Christian [mailto:[EMAIL PROTECTED]] Sent: Monday, July 29, 2002 4:11 PM To: Jetspeed Users List Subject: how to deploy into jetspeed How does one deploy an already built portal (packaged into a WAR file???) into jetspeed? I know that people who develop their own would use 'ant' on the build.xml file to 'ant deploy', but what if you're delivering something to a customer site. What then? Wayne Christian Sr. Staff Software Engineer Genesys Telecommunications Labs 2100 Gateway Centre Blvd. Suite 300 Morrisville, NC 27560 ? Office: (919) 466-6151 Fax: (919) ? EMail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
