buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tammo van Lessen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (BUILDR-439) "The command line is too long" when running TestNG tests
Date Mon, 19 Jul 2010 18:34:50 GMT

    [ https://issues.apache.org/jira/browse/BUILDR-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889962#action_12889962
] 

Tammo van Lessen commented on BUILDR-439:
-----------------------------------------

Setting a shorter M2_REPO via an env variable didn't work yet. First attempt was to set it
via setting(s).yaml, but the repositories.local setting was not taken in to account. The second
attempt was setting the M2_REPO to %M2" on the cmdline:

buildr test M2_REPO=%M2 did not work and neither buildr test M2_REPO="%M2" did.

What works is using "subst" to create a virtual drive letter that is pointing to my repo and
setting M2_REPO to X:

> "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.


Mime
View raw message