<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Thank you for the fix. It solves the problem with Saxon9.<br>
I am testing it now.<br>
Leigh.<br>
On 01/28/2012 07:24 AM, Rolf Lear wrote:
<blockquote cite="mid:4F241324.8090406@tuis.net" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="MS Exchange Server version
6.5.7036.0">
<title>Re: [jdom-interest] JDOM 1.x release schedule</title>
<!-- Converted from text/plain format -->
<p><font size="2">Hi all.</font>
</p>
<p><font size="2">I believe 1.1.2 is a more reliable version of
JDOM than 1.1.1. </font>
<br>
<font size="2">Unfortunately there is already one known new
issue 1.1.2 related to </font>
<br>
<font size="2">people using the SAXOutputter (which is used in
XML Transformations).</font>
</p>
<p><font size="2">This issue will be resolved in 1.1.3.</font>
</p>
<p><font size="2">Until 1.1.3 is released though there is a
'hotfix' for this issue here:</font>
<br>
<font size="2"><a moz-do-not-send="true"
href="https://github.com/hunterhacker/jdom/downloads">https://github.com/hunterhacker/jdom/downloads</a></font>
<br>
<font size="2">Download the jdom-1.1.2.hf1.zip file. The direct
link is:</font>
<br>
<font size="2"><a moz-do-not-send="true"
href="https://github.com/downloads/hunterhacker/jdom/jdom-1.1.2.hf1.zip">https://github.com/downloads/hunterhacker/jdom/jdom-1.1.2.hf1.zip</a></font>
</p>
<p><font size="2">This zip file is in the same format that you
would normally download </font>
<br>
<font size="2">from <a class="moz-txt-link-abbreviated" href="http://www.jdom.org">www.jdom.org</a>.</font>
</p>
<p><font size="2">If any other issues come up with 1.1.2 they will
be fixed and released </font>
<br>
<font size="2">as a second hotfix package.</font>
</p>
<p><font size="2">All issues found and fixed before 1 March 2012
will be accumulated and </font>
<br>
<font size="2">released as a 1.1.3 on that date.</font>
</p>
<p><font size="2">If you are currently running with 1.1.2 please
continue to do so. If you </font>
<br>
<font size="2">run in to any issues please report them here on
this list, check the </font>
<br>
<font size="2">open and recently fixed issues on github of
issues found in 1.1.2: </font>
<br>
<font size="2"><a moz-do-not-send="true"
href="https://github.com/hunterhacker/jdom/issues?labels=found+in+1.1.2">https://github.com/hunterhacker/jdom/issues?labels=found+in+1.1.2</a></font>
</p>
<p><font size="2">Despite recent evidence to the contrary, I do
believe that 1.1.2 is more </font>
<br>
<font size="2">stable than 1.1.1.</font>
</p>
<p><font size="2">If you have an issue in 1.1.2 and it has been
resolved in the issues </font>
<br>
<font size="2">list above, then please use the most recent 1.1.2
hotfix Jar from the </font>
<br>
<font size="2">downloads page.</font>
</p>
<p><font size="2">Thanks.</font>
</p>
<p><font size="2">Rolf</font>
</p>
<br>
<p><font size="2">On 25/01/2012 9:42 AM, Rolf Lear wrote:</font>
<br>
<font size="2">></font>
<br>
<font size="2">> Hi All.</font>
<br>
<font size="2">></font>
<br>
<font size="2">> Given the bug fix pending in the JDOM 1.1.x
stream I believe a new release</font>
<br>
<font size="2">> of the JDOM 1.1.x is required.</font>
<br>
<font size="2">></font>
<br>
<font size="2">> On the other hand I do not want to be
releasing 1.1.x versions for every</font>
<br>
<font size="2">> issue that arises.</font>
<br>
<font size="2">></font>
</p>
<p><font size="2">_______________________________________________</font>
<br>
<font size="2">To control your jdom-interest membership:</font>
<br>
<font size="2"><a moz-do-not-send="true"
href="http://www.jdom.org/mailman/options/jdom-interest/youraddr@yourhost.com">http://www.jdom.org/mailman/options/jdom-interest/youraddr@yourhost.com</a></font>
</p>
</blockquote>
<br>
</body>
</html>