[jetty-dev] [jira] (JETTY-991) Starting Jetty in separate JVM

    [ https://jira.codehaus.org/browse/JETTY-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292841#comment-292841 ] 

Larry Shatzer commented on JETTY-991:
-------------------------------------

My workaround now is using Cargo (http://cargo.codehaus.org/), where I can specify the JVM arguments on the command line. I'm not using their Maven plugin, but have a setup class that takes care of installing/configuring/deploying to Jetty and starting it up.
                
> Starting Jetty in separate JVM
> ------------------------------
>
>                 Key: JETTY-991
>                 URL: https://jira.codehaus.org/browse/JETTY-991
>             Project: Jetty
>          Issue Type: New Feature
>          Components: Maven
>    Affects Versions: 6.1.16
>            Reporter: Stevo Slavic
>            Assignee: Jan Bartel
>             Fix For: 7.5.0
>
>
> Please support starting jetty (using jetty-maven-plugin) in separate JVM istance than one Maven build is running in. With jetty-maven-plugin running in separate JVM instance, stopping it should exit JVM instance Jetty was running in. This would enable maven code coverage plugins like maven cobertura plugin to get coverage data on time for maven report generation, as these data get stored on JVM exit event.

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

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email