On Tue, 27 Jan 2004, Antoine L�vy-Lambert <[EMAIL PROTECTED]> wrote: > all I would like in a first step is that *someone* (I do not know if > I have the rights to do it, and in any case I do not know how to do > it) replaces the packaged dom4j jar with this one : > http://www.ibiblio.org/maven/dom4j/jars/dom4j-core-1.4-dev-8.jar
We are using the final release of dom4j-1.4 which should be more recent than the version you are talking about. Let me repeat, the dom4j version in packaged-dom4j is no problem for the jaxen build, jdom is. No, you don't have the permissions to change the library used, neither have I for all the machines. They are not centrally stored, you'd need access to all machines running Gump instances. > I do not know where in the gump metadata the location of "static" > jars is defined, in the profile <project name="packaged-dom4j" package="dom4j-1.4"/> together with pkgdir attribute of the workspace. > In any case, if we use this one > http://www.ibiblio.org/maven/dom4j/jars/dom4j-core-1.4-dev-8.jar as > "packaged dom4j" I believe that this part of the inferno will cool > down. There wouldn't be any difference as the build failures of jaxen-from-packaged-dom4j are only related to jdom. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
