Hi, I've found the issue. https://issues.apache.org/jira/browse/KARAF-1545
regards, Achim 2015-02-19 11:44 GMT+01:00 Guillaume Nodet <[email protected]>: > 2015-02-19 11:28 GMT+01:00 Stuart McCulloch <[email protected]>: > > > On 19 Feb 2015 10:09, "Guillaume Nodet" <[email protected]> wrote: > > > > > > 2015-02-19 11:01 GMT+01:00 Fabian Lange <[email protected]>: > > > > > > > Hi Guillaume, > > > > > > > > as somebody who put stuff to lib, I discovered that karaf* magic > > myself. > > > > > > > > I think lib/system is more explicit. But then I would prefer if all > > > > jars there are added to the JVM classpath, not only karaf*. > > > > > > > > > > Yes, definitely, sorry to not have been more clear, but that was > > definitely > > > the idea. So instead of having special karaf* jars, it would simply > load > > > all jars in lib/system. > > > > lib/boot might make more sense, to avoid confusion with the existing > > top-level system directory > > > > Agreed, it would be less confusing. > > > > > > > > > > > > Also worth noting: I have not found a nice way to include the JVM > > > > tools.jar (pre Java 9) onto the classpath without patching the > > > > karaf.sh. Not sure if this is a karaf use-case and it could be > simpler > > > > (tools.jar is tricky and actually going away with 9) > > > > > > > > > > I'm sure we can find a solution, but it seems to me that there are > still > > a > > > lot > > > of stuff that is missing or bound to change in Java 9 ... > > > > > > > > > > > > > > Fabian > > > > > > > > On Thu, Feb 19, 2015 at 9:38 AM, Guillaume Nodet <[email protected]> > > wrote: > > > > > I'm thinking about slightly changing the way the lib folder is > > organised > > > > in > > > > > Karaf 4. > > > > > With all previous versions, the lib folder can contains jar with 2 > > > > > different set of jars: > > > > > - karaf*.jar will be loaded when the JVM is started (they are > > appended > > > > to > > > > > the class path of the java command) > > > > > - other jars are loaded by the Main class along with the osgi > > framework > > > > > jar > > > > > > > > > > The convention that jars named karaf*.jar are loaded and available > to > > the > > > > > Main class (for example for jdbc lock access) is not really > explicit > > > > enough > > > > > imho. > > > > > > > > > > I wonder if it would make sense to set up a separate lib/system > > directory > > > > > which would contain those karaf*.jar files (thus avoiding the need > to > > > > > rename them). > > > > > We could keep the lib/ folder for jars that will be loaded by the > > Main > > > > > class, or even move them to a separate directory such as lib/app, > but > > I'm > > > > > not really sure it brings anything. > > > > > > > > > > Thoughts ? > > > > > > > > > > Guillaume > > > > > > > > > > -- > > > > > ------------------------ > > > > > Guillaume Nodet > > > > > ------------------------ > > > > > Red Hat, Open Source Integration > > > > > > > > > > Email: [email protected] > > > > > Web: http://fusesource.com > > > > > Blog: http://gnodet.blogspot.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
