-
1. Re: removing build, moving ivy stuff to pvm module
mvaldes Oct 4, 2007 9:02 AM (in response to tom.baeyens)Good idea, go ahead so.
regards,
Miguel Valdes -
2. Re: removing build, moving ivy stuff to pvm module
tom.baeyens Oct 4, 2007 10:45 AM (in response to 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. -
3. Re: removing build, moving ivy stuff to pvm module
porcherg Oct 5, 2007 5:17 AM (in response to tom.baeyens)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 -
4. Re: removing build, moving ivy stuff to pvm module
tom.baeyens Oct 5, 2007 5:42 AM (in response to tom.baeyens)WTF ?!? how could i have overlooked that. THANKS.