[
https://issues.apache.org/jira/browse/SLING-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14517337#comment-14517337
]
Konrad Windszus commented on SLING-4677:
----------------------------------------
See
https://github.com/apache/maven-surefire/blob/master/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java#L1869
on how this is achieved for maven-failsafe-plugin. {{suspend=y}} is not a good
option IMHO for Sling, because you want to start Sling directly (even if no
debugger is attached).
Also maybe it is possible to add an option to not do forking at all. That would
ease to debug from IDEs, where you can easily trigger a Maven Build in debug
mode.
> Allow to start in debug mode through a mojo parameter similar to
> debugForkedProcess
> -----------------------------------------------------------------------------------
>
> Key: SLING-4677
> URL: https://issues.apache.org/jira/browse/SLING-4677
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
> Affects Versions: Slingstart Maven Plugin 1.1.0
> Reporter: Konrad Windszus
>
> It would be good to have a mojo parameter similar to
> https://maven.apache.org/surefire/maven-failsafe-plugin/integration-test-mojo.html#debugForkedProcess
> to ease the debugging of Sling.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
