Makes sense, I din't have any problem introducing KARAF_OPTS On Friday, December 31, 2010, Andreas Pieber <[email protected]> wrote: > Lets say yes and no :) > > The problem are those line: > > if [ "x$JAVA_OPTS" = "x" ]; then > JAVA_OPTS="$DEFAULT_JAVA_OPTS" > fi > export JAVA_OPTS > > I want to use the DEFAULT_JAVA_OPTS, but extend them instead of replace them; > but I'm not sure if we wan't to do this in general? > > kind regards, > andreas > > On Fri, Dec 31, 2010 at 11:50:30AM +0100, Guillaume Nodet wrote: >> Can't you reuse JAVA_OPTS ? >> >> On Friday, December 31, 2010, Andreas Pieber <[email protected]> wrote: >> > Hey, >> > >> > Currently I have the use case that I have to set additional sys_vars in >> > karaf >> > (those -Dthings). In specific, to set wicket to development mode I have to >> > add a >> > -Dwicket.configuration=development. BUT I don't want to set those options >> > directly in the script (karaf.bat/".sh"). >> > >> > My idea was to add a KARAF_OPTS var which is used during calling the >> > script. >> > Then you can do: >> > >> > export KARAF_OPTS=-Dwicket.configuration=development >> > bin/karaf >> > >> > The changes are quite trivial (see patch; applies to karaf-2.1.x; but >> > should >> > also apply to master IMHO). If you do not export KARAF_OPTS the part is >> > simply >> > empty and will not change the behaviour, otherwise you can add system >> > props as you >> > like. >> > >> > Is there a better way? WDYT? >> > >> > kind regards, >> > andreas >> > >> > >> >> -- >> Cheers, >> Guillaume Nodet >> ------------------------ >> Blog: http://gnodet.blogspot.com/ >> ------------------------ >> Open Source SOA >> http://fusesource.com >
-- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
