[
https://issues.apache.org/jira/browse/BUILDR-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889946#action_12889946
]
Antoine Toulme commented on BUILDR-439:
---------------------------------------
I'm discussing this problem with Tammo. Unfortunately, there is no good way to
fix the problem. The classpath command may be set from the environment, but it
may be ignored afterwards by Windows if its value exceeds 2047 characters
(http://support.microsoft.com/kb/830473).
For now I am suggesting to Tammo to use a smaller M2_REPO path that will help
slim down the issue.
We could define one env variable per dependency as well, but that would make
the command very ugly.
If there is a way to use a file to pass parameters to the java executable, I'd
be interested to hear about it as it sounds like the only real good fix.
> "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.
