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 2013/10/02 01:37:24 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: commit-c79a2a7.patch

Attached a patch that works fine on windows, but perhaps needs some tests on other OSes. Actually, the taken approach should be the most portable as it creates a "pathing jar". See also [here|http://stackoverflow.com/questions/201816/how-to-set-a-long-java-classpath-in-msdos-windows] for details.

> "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
>             Fix For: 1.4.7
>
>         Attachments: BUILDR-439.patch, commit-c79a2a7.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 was sent by Atlassian JIRA
(v6.1#6144)