[jira] [Issue Comment Deleted] (SLING-4677) Allow to start in debug mode through a mojo parameter similar to debugForkedProcess

["Konrad Windszus (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus updated SLING-4677:
-----------------------------------
    Comment: was deleted

(was: It is all in https://fisheye6.atlassian.com/browse/sling/trunk/tooling/maven/slingstart-maven-plugin/src/main/java/org/apache/sling/maven/slingstart/run/ServerConfiguration.java?r1=1673190&r2=1676805#to52. You just set the parameter {{debug}} within the server configuration to {{true}} to start Sling in debug mode (listening on port 8000). To further tweak that you can also set {{debug}} to some arbitrary string. This is then appended to the regular VM options. For a list of possibilities have a look at http://docs.oracle.com/javase/7/docs/technotes/guides/jpda/conninv.html#Invocation.)

> 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
>            Assignee: Konrad Windszus
>             Fix For: Slingstart Maven Plugin 1.1.2
>
>         Attachments: SLING-4677-v1.diff
>
>
> 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)