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 2010/07/17 15:52:49 UTC
[jira] Reopened: (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 reopened BUILDR-439:
-------------------------------------
Hi,
unfortunately the problem still appears (with Buildr 1.4.2 from today's trunk). I think this time it is due to classpath option, which appears to be too long. I couldn't find any @options setting for java.exe, however it could be possible to set the CLASSPATH environment variable for this 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
> Fix For: 1.4.1
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.