Hi Achim, Karaf does not need to ship this and can leave those questions up to the distributors using the feature.
Fabian On Mon, Oct 31, 2016 at 1:43 PM, Achim Nierbeck <[email protected]> wrote: > hmm ... even though I like the idea ... what Implications does it have for > > a) is it compliant with the ASF license? > b) how about different JVMs and different processors ... don't we need to > provide it for intel, arm, ppc? > > regards, Achim > > > 2016-10-31 13:39 GMT+01:00 Fabian Lange <[email protected]>: > > > Hi Sascha, > > > > i very much like the idea. It can be a very lightweight enhancement to > the > > start scripts, because what it basically does is that it defines a > "search > > list" for "JAVA_HOME". Maybe it is sufficient to add that feature to the > > scripts and every distributor can customize the directory they prefer. > > > > Fabian > > > > -- > > Fabian Lange | Performance Expert > > mobil: +49 (0) 160.3673393 > > > > codecentric AG | Merscheider Straße 1 | 42699 Solingen | Deutschland > > > > Sitz der Gesellschaft: Solingen | HRB 25917| Amtsgericht Wuppertal > > Vorstand: Michael Hochgürtel . Mirko Novakovic . Rainer Vehns > > Aufsichtsrat: Patric Fedlmeier (Vorsitzender) . Klaus Jäger . Jürgen > Schütz > > > > On Mon, Oct 31, 2016 at 1:33 PM, Sascha Vogt <[email protected]> > > wrote: > > > > > Hi all, > > > > > > we're workig on a Karaf based product and have the requirement to use > > > the JVM we ship with the product. We thought that might also be > > > interesting to others, so we wanted to share our proposal / current > > > implementation (and are also willing to provide the required patches). > > > > > > Main idea is to modify the start scripts (including the service > > > wrappers?) to prefer a JVM inside the KARAF_HOME directory (ie. > > > runtime/jvm64, or just plain jvm in KARAF_HOME). Whenever such a > > > directory is present it is prefered over a JAVA_HOME env var or > whatever > > > else is in the path. > > > > > > Reason to also prefer it over JAVA_HOME is because if you run alongside > > > other Java applications on a server, JAVA_HOME might already be set for > > > other applications and the admin cannot change it. > > > > > > At the moment we have implemented the above via custom setenv scripts > we > > > ship which then sets JAVA_HOME to KARAF_HOME/runtime/jvm64. When > > > "wrapper:install" is called, this JAVA_HOME is taken to the wrapper > > > properties. > > > > > > We spoke with the Instana[1] people as their agent is also Karaf based > > > and they were interested in it as well, so we know at least one other > > > Karaf user who would welcome that :) > > > > > > Anyway, any feeback is welcome. Also of course the name of the > > > directory(ies) can be discussed. > > > > > > Greetings > > > -Sascha- > > > > > > [1]https://www.instana.com/ > > > > > > > > > -- > > Apache Member > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & > Project Lead > blog <http://notizblog.nierbeck.de/> > Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> > > Software Architect / Project Manager / Scrum Master >
