Hi, is there any experience in developing with jetspeed in an eclipse environment ? Or better, what's the preferred development structure (directories, files, build targets etc.) for separating the individual changes from the default jetspeed distribution (for "fast" upgrade to new jetspeed versions ...)
I know the tutorial uses property merging etc. but it "only" merges into the default war file. How to extensively modify the war file (meaning the underlying sources, images etc.) WITHOUT loosing track of my own changes ? I'm thinking of a separate directory which encapsulates all modifications and add ons (like in the tutorial) and a general directory with the "default" jetspeed distribution, where you can delete stuff you don't need (images etc.). Both should be merged to a common webapp directory, which is the final webapp. Does this make sense ? Or will soon the personal directory look like the default jetspeed one with lot's of merging trouble ? A complete webapp dir under the development root would also be fine for server side debugging. E.g. with the Eclipse Tomcat Launcher plugin you can easily debug a webapp within eclipse but it has to be part of the project (underneath the development root) -> http://www.sysdeo.com/eclipse/tomcatPlugin.html Or just use the default structure and my.properties and mix all together (e.g. modified java sources) as suggested in the Configuration Guide http://jakarta.apache.org/jetspeed/site/config_guide.html ? Any advice appreciated ! Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
