[arquillian-issues] [JBoss JIRA] (ARQ-1750) Support javaVmArguments configuration option to control forked vm

[Gerhard Poul (JIRA)]

    [ https://issues.jboss.org/browse/ARQ-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12960122#comment-12960122 ] 

Gerhard Poul commented on ARQ-1750:
-----------------------------------

I would've assumed that we use the configuration mechanisms used by liberty itself such as the ones documented in http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/index.jsp?topic=%2Fcom.ibm.websphere.wlp.nd.doc%2Fae%2Ftwlp_tun.html to set mx and debug parameters; what is the added value of having this as part of the arquillian.xml configuration? Do other container implementations already support this?
                
> Support javaVmArguments configuration option to control forked vm
> -----------------------------------------------------------------
>
>                 Key: ARQ-1750
>                 URL: https://issues.jboss.org/browse/ARQ-1750
>             Project: Arquillian
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: WebSphere Containers
>    Affects Versions: was_1.0.0.Alpha2
>            Reporter: Aslak Knutsen
>
> Support configuration option javaVmArguments to add extra information to the launched WLP vm.
> * memory settings
> * debug options
> java [javaVmArguments] -javaagent:lib/bootstrap-agent.jar -jar lib/ws-launch.jar

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira