Giacomo Pati wrote: > Ok, I've checked whether the jetty-start.jar can help simplify the > cocoon.sh/cocoon.bat combo. I've come to the conclution that either the > jetty-start.jar nor our Loader class will be able to overcome the pain > to maintain 2 separate start scripts for the two main OS platforms. the > reason is simple. > > There are some properties that NEED to be specified on the command > line anyway to be active: > > -Djava.endorsed.dirs... > -Dcom.sun.management.jmxremote... > -Xdebug... > > and some others, too. > > So, simplifying with the help of the jetty-start.jar/Loader will only > able to cover properties specifyable during the run of a JXM. Sure one > can write a java class that spawns a new JVM thread/process but IMHO > that would not be very smart (2 JVM running just to configure one). > Yes, I guess you're right - so if noone beats me I'll try to get the windows script running again as soon as possible.
Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
