moved to ivy2.0.0 beta 2

Julio moved us over to ivy 2.0.0 last week; some of the adverse 
consequences of this have only just surfaced
  -ivy doesnt like you redefining the tasks in a different classloader 
(always a risk of a memory leak there)
  -ivy gets very upset if you reload a configuration more than once

The effect was to
  (a) stop you running two targets across all projects, such as in the 
core/ dir, going
ant clean clean

  (b) cause problems if you had external builds that also had ivy files, 
and which the core/build ivy-managed runs picked up.

I've fixed these by not reloading ivy if present, and skipping reloading 
the settings if Ivy is present. We are still likely to break if there 
are external projects in external/ with ivy.xml files, as they need the 
same changes.

There are also some other changes that are less critical
  -the namespace for antlibs that you should use has changed
  -the ivy:configure task is now deprecated, replaced with <ivy:settings>
  -the names of some of the elements in the ivy configuration file has 
changed.

I've applied all the changes I can, don't be afraid to complain if 
things break

-steve


-- 
-----------------------
Hewlett-Packard Limited
Registered Office: Cain Road, Bracknell, Berks RG12 1HN
Registered No: 690597 England

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone