Hi Jdomers,
Daniel Florey of the slide team says that JDOM has a runtime dependency
to saxpath.
Since saxpath is deprecated and merged under new package names into jaxen,
can you replace the package names of saxpath with their equivalents in
jaxen ?
This will be useful to get a number of open s
Hello Daniel,
does jdom need saxpath at build time or at compile time ?
I had run the build of jakarta-slide without saxpath, and it went well.
So I do not understand why you need saxpath.
Cheers,
Antoine
-
To unsubscribe, e-
Hi,
can you remove your dependency to saxpath from your build file ?
saxpath is now part of jaxen.
I have done your ant build with the jars which are checked into your
repository, without saxpath, and it works.
Here is a tiny patch for your build.xml. If you apply it, you can also
remove the
Antoine Lévy-Lambert wrote:
As a matter of fact, last night build on lsd failed.
The final version : the build on lsd went well last night, the HTML
pages which were generated were not up to date due to a problem
encountered in forrest generation.
Now I have another question :
saxpath is
As a matter of fact, last night build on lsd failed.
According to Stefan Bodewig, [1] this is not due to ant, this is maybe a
special gumpy problem (gumpy is the python version of gump).
I have just let the gump list become aware of the problem.
Cheers,
Antoine
Unico Hommes wrote:
:-) No pro
Hi Unico,
sorry that my suggestions did not work immediately. :-(
Thanks for fixing the problem. :-)
Antoine
[EMAIL PROTECTED] wrote:
unico 2004/03/10 06:17:43
Modified:testsuite build.xml
Log:
make sure property is correct when invoked from main build script
Revision Chan
the location of the jdom.jar built earlier in
the gump run.
Cheers,
Antoine
Unico Hommes wrote:
Hmm, your patches seem to get lost on the mailinglist. Could you send
it to me directly? I will apply it.
Thanks Antione, your efforts are very much appreciated :-)
--
Unico
Antoine Lévy-Lambert
Would someone kindly commit the attached patches :
This will help jakarta-slide build properly with gump.
Cheers,
Antoine
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I see the problem.
Gump is setting the jdom.jar property to the full path of the jar, which
is concretely
/data3/gump/jdom/build/jdom.jar on lsd.student.utwente.nl.
In the testsuite/build.xml, which invoked via from the main build
file, there is this line :
this results in the error :
Cou
Hi Sliders,
can you update the build.xml file located in the testsuite subdir, there
is a leftover of your last change of jdom version,
this is putting the gump build for your software unneedly in the red,
where it should be green like a prairie in Normandie.
Cheers,
Antoine
Index: testsuite/b
Oliver Zeigermann wrote:
In anticipation of the first 1.0 release of JDOM I have replaced the
b9 version with the JDOM HEAD checked out today (called
jdom-20040226-.jar). I have changed the build.xml and all classes that
used the removed methods for XMLOutputter. Changes should be
transparent.
Hi sliders,
On Feb 18, 2004, at 5:50 PM, Jason Hunter wrote:
>As I wrote in a separate mail to a smaller set of addresses, the
setEncoding() method just moved for the Format class. The
functionality is still there.
>
>The setEncoding() method was actually deprecated quite a while ago,
in ea
Hello,
Please read the email of Stefan Bodewig from the gump list.
concerning Velocity, the anakiatask has a class OutputWrapper which extends
org.jdom.output.XMLOutputter
and relies on XMLOutputter supplying the setEncoding method.
Slide has 2 classes which use XMLOutputter#setEncoding
I do
13 matches
Mail list logo
