I am interested in getting this problem solved.
As a first step, I have downloaded the source code of dom4j and of jaxen on my PC.
I have seen that the bits of the dom4j jar file which are used in the gump builds are different in the CVS HEAD version of dom4j, my guess is that they would be OK for jaxen.
I have also built jaxen using the supplied build.xml,
the file which is at this location : http://www.ibiblio.org/maven/dom4j/jars/dom4j-core-1.4-dev-8.jar
allows to build jaxen properly.
So, would it be possible to alter the location from which the various gump instances pick their dom4j to take it from this maven location.
This would at least allow to build jaxen, and if this works, this would put in the green all the projects which are dependent upon jaxen.
Then later, if I have some time, I will try to investigate how to adapt dom4j and jaxen so that they build properly in gump. I have read about the cyclical dependency issue, maybe it is solvable by changing the build files of both jaxen and dom4j to have targets which allow to build both applications without cyclical dependencies, something like :
DOM4J Part 1 | v Jaxen | v DOM4J Part 2
Cheers,
Antoine
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
