You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@buildr.apache.org by "Tammo van Lessen (JIRA)" <ji...@apache.org> on 2011/07/08 15:04:17 UTC

[jira] [Updated] (BUILDR-439) "The command line is too long" when running TestNG tests

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

Tammo van Lessen updated BUILDR-439:
------------------------------------

    Attachment: BUILDR-439.patch

Patch attached. It at least works on my win7 maschine, but should also work with any other windows version. I didn't test with non-win yet, but I don't expect any issues.

Here is what the patch does:

Like before, the whole command line is generated. If we're under win_os and the command line is longer than 2048 (limit of WinNT, Win2k), the classpath is removed from the command line itself and is instead put in front of a generated temporary batch file as a CLASSPATH env variable. Then the tmp batchfile is handed over for execution.

> "The command line is too long" when running TestNG tests
> --------------------------------------------------------
>
>                 Key: BUILDR-439
>                 URL: https://issues.apache.org/jira/browse/BUILDR-439
>             Project: Buildr
>          Issue Type: Bug
>          Components: Test frameworks
>    Affects Versions: 1.3.5
>         Environment: JRuby 1.4.1 on Win7
>            Reporter: Tammo van Lessen
>            Assignee: Antoine Toulme
>         Attachments: BUILDR-439.patch
>
>
> When running a huge bunch of TestNG test cases (e.g. in the ODE build), buildr creates a command line command that is too long for Windows/JRuby.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira