removing build, moving ivy stuff to pvm module

[tom.baeyens]

i'm going to move the ivy.jar and the ivysettings.xml to the pvm. since all other projects have a dependency on pvm anyway, they can reference the pvm module. that way we can still have a common base build file if we want.

is that ok ?

i'm starting this work now so be fast with your feedback and comments :-)

[mvaldes]

Good idea, go ahead so.

regards,
Miguel Valdes

[tom.baeyens]

done.

i have one question for Guillaume or anyone else that might want to have a look at it:

Using the compile target in pvm, the compile configuration is used so it takes in the 'api' configuration of hibernate. And still the dom4j and commons-collections are included, which i think is not supposed to be the case.

Could anyone have a look to see what I'm missing in the ivy files ?

Note: some of the ivy files have been updated, so you might want to remove all non-jar files from your cache after an update of the pvm.

[porcherg]

The compile conf extends runtime.hibernate, and as a result, the dependencies of runtime.hibernate are fetched.

As runtime.hibernate uses the default hibernate conf, dom4j and commons-collections are a dependency of compile.

regards,
Guillaume

[tom.baeyens]

WTF ?!? how could i have overlooked that. THANKS.