It's part of the provisioning of the
container, org.ops4j.pax.exam.CoreOptions.vmOption
Eclipse can do it, too, obviously, but I don't know how. It was
extremely simple in Intellij
- Eric L
On Sat, Nov 11, 2023 at 6:25 PM Steinar Bang wrote:
> (hm... I never responded to this one, looks
(hm... I never responded to this one, looks like...? Sorry about that!)
> Eric Lilja :
> Yeah, as JB mentioned, Karaf mode in Pax Exam is forked so the classpath
> from the test bootstrap itself does not spill over into the container (for
> native pax exam, you can choose between forked mode
Yeah, as JB mentioned, Karaf mode in Pax Exam is forked so the classpath
from the test bootstrap itself does not spill over into the container (for
native pax exam, you can choose between forked mode or not).
Anyway, remote debugging seems to be a bit easier in Intellij (I stopped
using Eclipse
> Jean-Baptiste Onofré :
> As pax-exam can fork the JVM to start Karaf, you need remote debugger.
Hm... but does it fork the JUnit test also?
That's where I'm trying to debug...?
Ah, but you're right! To be able to run the way it does, i.e. access
OSGi services created in karaf as Java
Hi,
As pax-exam can fork the JVM to start Karaf, you need remote debugger.
Is it what you are doing ?
Regards
JB
On Sat, Jun 3, 2023 at 4:41 PM Steinar Bang wrote:
>
> Platform: debian 11.7 "bullseye", amd64
> openjdk-17-jdk:amd64 17.0.6+10-1~deb11u1 (ie. java 17)
> karaf
Platform: debian 11.7 "bullseye", amd64
openjdk-17-jdk:amd64 17.0.6+10-1~deb11u1 (ie. java 17)
karaf 4.4.3
pax-exam 4.13.5
eclipse 2023-03 (4.27.0)
When I set breakpoints in a pax exam test and run the test in debug in
eclipse, the breakpoints are never
