[
https://issues.apache.org/jira/browse/SLING-4796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-4796.
-------------------------------------
Resolution: Won't Fix
> 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
> Priority: Major
>
> 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
(v8.20.10#820010)
