[mevenide-dev] [jira] Commented: (MEVENIDE-435) cannot debug tests when surefire's argLine paramter used in pom

    [ http://jira.codehaus.org/browse/MEVENIDE-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120289 ] 

Milos Kleint commented on MEVENIDE-435:
---------------------------------------

in surefire plugin 2.4 there's a new property ${maven.surefire.debug} which is used to pass debugging params into the forked jvm. These are added to the arg parameter.

> cannot debug tests when surefire's argLine paramter used in pom
> ---------------------------------------------------------------
>
>                 Key: MEVENIDE-435
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-435
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide2-netbeans
>    Affects Versions: NB_2.1.1
>            Reporter: Milos Kleint
>            Assignee: Milos Kleint
>             Fix For: NB_2.4
>
>
> the debug switches are passed to the surefire plugin via the -DargLine=-Xdebug...... property.
> However when user defines the argLine parameter for surefire plugin in the pom, the system property is not being evaluated. 
> There's currently no solution to the problem. One idea that needs some prottyping is to add a method to the embedder that would be able to run the build on top of MavenProject instance instead of a pom file. That we we could dynamically inject the additional debug switches dynamicaly when constructing the MavenProject instance.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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