Konrad Windszus created SLING-4796:
--------------------------------------
Summary: Add a simpler way to debug server-side integration tests
Key: SLING-4796
URL: https://issues.apache.org/jira/browse/SLING-4796
Project: Sling
Issue Type: Improvement
Affects Versions: org.apache.sling.testing.tools 1.0.10
Reporter: Konrad Windszus
Currently you have to tweak the {{jar.executor.vm.options}} to be able to debug
the server-side part of the integration tests.
Actually the java process is forked twice:
# For the surefire-plugin which executes the client (=Maven) part which can be
debugged like described in
http://maven.apache.org/surefire/maven-surefire-plugin/examples/debugging.html
# In the {{JarExecutor}} which starts the Sling server.
To ease debugging of the server side part of test I could think of two
different options.
# Allow to prevent the 2nd forking (so the Sling server would be executed in
the same Java process as the actual test). That would ease debugging as you
could at the same time debug client-side and server-side code
# Come up with an easy option like {{maven.surefire.debug}} which would
automatically listen on a specific port for a debugger.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
