Java Debug options are Pre Java 5.0. Why?

2014-12-19 Thread Paul Spencer
When debugging I noticed the debugger option are Pre Java 5.0. Since Karaf requires Java 7 or greater, why are the old debug options used? I was expecting DEFAULT_JAVA_DEBUG_OPTS = “-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005” sparrow:bin paul$ grep

Karaf EIK classpath for Maven Dependencies

2014-12-19 Thread jochenw
Hello, we are currently experimenting with Karaf EIK (self-built version with sources from github, 3.0.0-SNAPSHOT). The background is that we want to OSGify the GUI or a Web application. The manifest for the war is already set up so it can be deployed in Karaf with Pax-Web, and everything works

Re: Java Debug options are Pre Java 5.0. Why?

2014-12-19 Thread Achim Nierbeck
Yes please, open an issue for this. Regards, Achim 2014-12-19 16:38 GMT+01:00 Paul Spencer pau...@apache.org: When debugging I noticed the debugger option are Pre Java 5.0. Since Karaf requires Java 7 or greater, why are the old debug options used? I was expecting DEFAULT_JAVA_DEBUG_OPTS =

Re: Java Debug options are Pre Java 5.0. Why?

2014-12-19 Thread Jean-Baptiste Onofré
It's historic ;) Please, create a Jira, we gonna fix that. Regards JB On 12/19/2014 04:38 PM, Paul Spencer wrote: When debugging I noticed the debugger option are Pre Java 5.0. Since Karaf requires Java 7 or greater, why are the old debug options used? I was expecting

Declarative Services implementation?

2014-12-19 Thread Scott Lewis
Howdy, In browsing through the bundles used in the default Karaf config (3.0.2), I didn't seem to see an implementation of DS installed by default. 1) Is there a DS implementation as part of one of the existing Karaf features? If so, what feature is that? 2) If there is such a feature,