Eclipse shouldn't be seeing these because ivy shouldn't be exporting
them... I recall when I wrote the ivy.xml file I specifically included
two different configs -- one for ANT (execution, task defs) and one
for IDEs and compilation. This used to work but now everything is
copied to lib/ (including ant and junit4-ant, which are not required
at all except for ant buildfile taskdefs.
I see Steve was playing with ivy files -- I've tried to fix it in 5
mins, but failed so far. Steve, do you know how to exclude these two
deps from the default configuration (junit4-stdalone is still used in
ivy dependency collection in the buildfile's taskdef).
<!-- Only needed for ANT taskdefs. -->
<dependency org="org.apache.ant" name="ant" ...
<dependency org="com.carrotsearch.randomizedtesting" name="junit4-ant" ...
Dawid
On Fri, Feb 6, 2015 at 9:21 AM, Uwe Schindler <[email protected]> wrote:
> Moin,
>
>> It's a repackaged, trimmed guava dependency, but it shouldn't be visible;
>> only the test runner should be on test classpath; the ant runner code for
>> randomizedtesting should only be present for the ANT build file.
>
> But Eclipse sees it and sometimes makes those stupid suggestions for
> imports...
>
>> > I suspect the junit4 jar is not on the Maven test classpath because the
>> Maven build uses the surefire plugin as its test runner rather than the
>> junit4
>> runner.
>>
>> Traitors! :)
>>
>> Dawid
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected] For additional
>> commands, e-mail: [email protected]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
