buildr-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vincent Tence <vte...@pyxis-tech.com>
Subject Re: junit conflict in idea
Date Mon, 03 Mar 2014 15:04:46 GMT
I mean

define 'common' do
   compile.with LOG4J
   test.with 'org.hamcrest:hamcrest-core:jar:1.3', 'com.github.stefanbirkner:system-rules:jar:1.4.0',
'org.junit.contrib:junit-theories:jar:4.11', QUICKCHECK
   package :jar
 end

-- Vincent

> I use a build.yaml file with a line:
> 
> junit: 4.11
> 
> and it works just fine.
> 
> I don't think you need to specify the junit dependency in your buildfile (I never do).
You can try:
> 
> define 'common' do
>    compile.with LOG4J
>    test.with
>    package :jar
>  end
> 
> Cheers,
> -- Vincent
> 
> On 2014-03-03, at 8:49 AM, Jean-Philippe Caruana <jp@target2sell.com> wrote:
> 
>> Le 03/03/2014 14:36, Tammo van Lessen a écrit :
>>> Hi Jean Philippe,
>>> 
>>> If I'm not mistaken, adding the following line to the beginning of your
>>> buildfile should help:
>>> 
>>> Buildr.settings.build['junit'] = '4.11'
>>> 
>>> In order to avoid conflicts, you can reference JUnit.dependencies instead
>>> of your own JUNIT constant.
>> 
>> I didn't know that ! Thanks !
>> But I still have the issue, but my buildfile looks like this now :
>> 
>>  Buildr.settings.build['junit'] = '4.11'
>>  JUNIT = JUnit.dependencies, 'org.hamcrest:hamcrest-core:jar:1.3',
>> 'com.github.stefanbirkner:system-rules:jar:1.4.0',
>> 'org.junit.contrib:junit-theories:jar:4.11', QUICKCHECK
>> 
>> Please note that in eclipse there is no such issue, so I suspect the
>> idea plugin here.
>> 
>> -- 
>> Jean-Philippe Caruana
>> http://www.barreverte.fr
> 


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message