[jdom-interest] [Fwd: More JDOM changes]
jhunter at acm.org
Wed Feb 18 14:50:39 PST 2004
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
early May 2003 per CVS logs. We removed it from CVS recently after the
Beta 10 release (we deprecate for one beta cycle) in preparation for a
clean 1.0 release. So you can either build against Beta 10 or continue
to use HEAD and just change your usage (what I recommend).
Antoine Lévy-Lambert wrote:
> Please read the email of Stefan Bodewig from the gump list.
> concerning Velocity, the anakiatask has a class OutputWrapper which extends
> and relies on XMLOutputter supplying the setEncoding method.
> Slide has 2 classes which use XMLOutputter#setEncoding
> I do not know jdom, but it seems to me that it would be fair to restore
> the setEncoding method in XMLOutputter and give some time to slide and
> velocity to remove the usages of this method.
> Comments ?
>  velocity build failure visible on this URL :
>  source code of AnakiaTask
>  source code of OutputWrapper
>  build failure of http://gump.cocoondev.org/jakarta-slide.html
> -------- Original Message --------
> Subject: More JDOM changes
> Date: Wed, 18 Feb 2004 12:36:34 +0100
> From: Stefan Bodewig <bodewig at apache.org>
> Reply-To: Gump code and data <gump at jakarta.apache.org>
> To: gump at jakarta.apache.org
> it seems as if the JDOM saga continues, XMLOutputter#setEncoding has
> been removed leading to build failures in Velocity and Slide. The
> method has been deprecated in beta10rc1 (maybe even beta9) and people
> are now expected to use the Format instead.
> To control your jdom-interest membership:
More information about the jdom-interest