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

"Jeff Campbell (JIRA)" <jira-yCVjj/[email protected]> Thu, 11 Sep 2008 13:44:49 -0500 (CDT)
Newsgroups gmane.comp.jakarta.turbine.maven.mevenide.devel
Message-ID <30084573.1221158689322.JavaMail.haus-jira@codehaus01.managed.contegix.com>
     [ http://jira.codehaus.org/browse/MEVENIDE-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Campbell updated MEVENIDE-435:
-----------------------------------

    Attachment: surefire-argline-debug.zip

Attached is a VERY simple Maven jar project that shows our issues for debugging in NetBeans, with a Maven project that requires the <argLine> to be specified.  The sample project uses jmockit to run a simple mock test.  In this case jmockit requires a <argLine> parameter to run successfully.

Side note (I don't know if this has any impact on a fix)... We do NOT check-in any Netbeans specific files into our source control.  Because 50% of us are using NetBeans, 48% of us are using Eclipse, and 2% are using IntelliJ, we do NOT want to check-in any files that are IDE specific (can get really messy to have a bunch of mixed IDE specific files).  So..... hopefully the fix will allow a raw Maven project to debug the attached Maven project.

> 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
>
>         Attachments: surefire-argline-debug.zip, SurefirePlugin.java
>
>
> 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