Hi Rene,

I applied your tip and still Idea gave me another problem. Then I
started fiddling around and suddenly Idea asked this:

6:31:13 Error running
         Command line is too long. In order to reduce its length
classpath file can be used.
         Would you like to enable classpath file mode for all run
configurations of your project?
         Enable (show balloon)

I enabled it and now test execution in Idea is working. Some research
showed that this option relates to this entry in .iws:

 <component name="PropertiesComponent">
...
    <property name="dynamic.classpath" value="true" />
...
  </component>

My machine runs Windows 7 and I remember that the command line is
limited to 8 or 4 Kb. This article suggest that Idea asks for this
option change when the command line goes beyond 32 kb:

http://stackoverflow.com/questions/4853540/what-does-the-dynamic-classpath-flag-do-intellij-project-settings

My guess is that before a part of the command line just got lost and
this resulted in this weird behaviour.

Regards and thanks for all your help!
Robert

Am 10.08.2013 12:46, schrieb Rene Groeschke:
> Hi Robert,
>
> Robert Kühne wrote:
>> Thanks Peter! Unfortunately another problem came up. As you can see
>> below the Test class is not found. The class junit.framework.Test is
>> meant here. In the three classes where the error pops up the Test class
>> is written as fully qualified. But in the generated Groovy stubs they
>> are not. I guess this is the problem.
>>
>> C:\Users\Robert\.IntelliJIdea12\system\compiler\gradle.gradleec8a628a\.generated\groovyStubs\plugins\tests\org\gradle\api\internal\tasks\testing\junit\ATestClassWithBrokenSuiteMethod.java
>>     Error:Error:line (4)error: cannot find symbol class Test
>> C:\Users\Robert\.IntelliJIdea12\system\compiler\gradle.gradleec8a628a\.generated\groovyStubs\plugins\tests\org\gradle\api\internal\tasks\testing\junit\ATestClassWithSuiteMethod.java
>>     Error:Error:line (4)error: cannot find symbol class Test
>> C:\Users\Robert\.IntelliJIdea12\system\compiler\gradle.gradleec8a628a\.generated\groovyStubs\plugins\tests\org\gradle\api\internal\tasks\testing\junit\ATestSetUpWithBrokenSetUp.java
>>     Error:Error:line (11)error: cannot find symbol class Test
> you can exclude them from stub creation/compilation as they are just
> "resources" for the JunitIntegrationTest but Intellij tries to compile them.
>
> cheers,
> René
>
>
>> Example of a generated stub:
>>
>> package org.gradle.api.internal.tasks.testing.junit;
>>
>> public class ATestClassWithBrokenSuiteMethod extends
>> groovy.lang.GroovyObjectSupport implements groovy.lang.GroovyObject {
>> public static Test suite() {
>> return null;
>> }
>>
>> public static java.lang.RuntimeException getFailure() {
>> return null;
>> }
>>
>> public static void setFailure(java.lang.RuntimeException failure) {
>> return ;
>> }
>>
>> public java.lang.Object getProperty(java.lang.String property) {
>> return null;
>> }
>>
>> public void setProperty(java.lang.String property, java.lang.Object
>> newValue) {
>> return ;
>> }
>>
>> public java.lang.Object invokeMethod(java.lang.String name,
>> java.lang.Object args) {
>> return null;
>> }
>>
>> public groovy.lang.MetaClass getMetaClass() {
>> return null;
>> }
>>
>> public void setMetaClass(groovy.lang.MetaClass metaClass) {
>> return ;
>> }
>>
>> private static java.lang.RuntimeException failure = null;
>> }
>>
>> Thanks for your help!
>>
>> Regards,
>> Robert
>>
>>
>> Am 09.08.2013 23:56, schrieb Peter Niederwieser:
>>> The new IDEA 12 compilation mode no longer supports test->test dependencies.
>>> To get things to work, you'll have to disable Project
>>> Settings->Compiler->Use external build.
>>>
>>> Cheers,
>>> Peter
>>>
>>>
>>>
>>> --
>>> View this message in context: 
>>> http://gradle.1045684.n5.nabble.com/Test-execution-in-Intellij-Idea-tp5711656p5711657.html
>>> Sent from the gradle-dev mailing list archive at Nabble.com.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>     http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to