<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Hi, I did not get this original mail to me on the list.... did it
make it? Anyway, Jason, thanks for the 'comps' on your mail. In the
various places below I have all the code.<br>
<br>
You can pull the source .zips and compare with the current code
base? It'll need some merging because the code was cut from 1.1 and
the underlying code is now 1.1.1<br>
<br>
I could go through the 'generification' process again though, it's
not overly complex, especially with tools like eclipse. I have
learned a bit more about Generics in the past few years too, so I
may do things a little differently. Also, if we are breaking
backward compatibility, then there are some other issues I would
like to mention, like not properly implementing the Collections
API... ;-)<br>
<br>
Rolf<br>
<br>
On 22/07/2011 11:43 AM, Rolf Lear wrote:
<blockquote cite="mid:4E299ABB.3060704@tuis.net" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Hi all.<br>
<br>
I'm working on making the code available again. There are the
usual issues, on my home server, etc.<br>
<br>
On a more immediate level though, the code I have is based what's
now old JDOM code (1.1). I did my changes a while ago. See the
'JDom and Java5' thread(s) here:<br>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.jdom.org/pipermail/jdom-interest/2008-February/thread.html">http://www.jdom.org/pipermail/jdom-interest/2008-February/thread.html</a><br>
<br>
Then again, not much was changed between 1.1 and now.<br>
<br>
I have re-instated the git.tuis.net website..... Here's the
original mail I wrote, with the updated URL's. Note, I don't have
a git-server running any more, but the code is available using the
http url....<br>
<br>
Rolf<br>
<br>
==================================<br>
<br>
Hi All. <br>
<br>
I have ported JDom to use Java constructs throughout the code. I
have taken great pains to make the ported library as similar to
the existing one as possible. In fact, I believe that, in 99% of
the cases, you will probably be able to take the Java5 version and
simply recompile your code against the new Jar and have no
problems. <br>
<br>
At the same time, the code does a full implementation of Generics,
removes encumbrances required to support old Java versions
(Java1.2, etc.), and generally spruces up some of the ways that
some things are done. <br>
<br>
The porting has necessitated the rewrite of a number of core
sections of code (like ContentList), but there are performance
improvements in there too. <br>
<br>
Obviously this has been an individual effort with all the pitfalls
of 'single-mindedness' in there too. Any criticisms of the code
will be welcomed as the intention is to get a good result. <br>
<br>
I believe all the nice things in Java5 are now available,
especially those using generics where all the methods return
correctly typed data like such that constructs like: <br>
<br>
Element root = document.getRootElement(); <br>
for (Element child : root.getChildren()) { <br>
// do something with element child.... <br>
} <br>
<br>
are now possible. <br>
<br>
At this stage, the work is done, and I am just trying to determine
how much interest there is in such a port. <br>
<br>
I have set up an 'unreliable' server (it is my computer at home on
a residential cable-modem....) at git.tuis.net where you can: <br>
<br>
browse a full repository of the three core JDom projects (jdom,
jdom-test, and jdom-contrib): <br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://git.tuis.net/">http://git.tuis.net/</a> <br>
<br>
read a README I put together: <br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://git.tuis.net/jdom/README.Java5.txt">http://git.tuis.net/jdom/README.Java5.txt</a>
<br>
<br>
Download the actual source code (zipped or not): <br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://git.tuis.net/jdom/src/">http://git.tuis.net/jdom/src/</a>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://git.tuis.net/jdom/jdom.src.tar.gz">http://git.tuis.net/jdom/jdom.src.tar.gz</a>
<br>
<br>
Download the actual jar: <br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://git.tuis.net/jdom/jdom.jar">http://git.tuis.net/jdom/jdom.jar</a>
<br>
<br>
Review the API Docs: <br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://git.tuis.net/jdom/apidocs/">http://git.tuis.net/jdom/apidocs/</a>
<br>
<br>
Those wanting to access the repositories in git format can do so,
or those with CVS can access the same repository using the
(git-based) CVS proxies: <br>
<br>
Thus, if you want to get a hold of the repositories, you can,
using git: <br>
<br>
<!--- this will not work any more <br>
git clone git://git.tuis.net/jdom.git <br>
git clone git://git.tuis.net/jdom-contrib.git <br>
git clone git://git.tuis.net/jdom-test.git <br>
----><br>
<br>
Or, using (slower) http protocol: <br>
<br>
git clone <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://git.tuis.net/git/jdom.git">http://git.tuis.net/git/jdom.git</a>
<br>
git clone <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://git.tuis.net/git/jdom-contrib.git">http://git.tuis.net/git/jdom-contrib.git</a>
<br>
git clone <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://git.tuis.net/git/jdom-test.git">http://git.tuis.net/git/jdom-test.git</a>
<br>
<br>
<br>
<!--- this will not work any more <br>
Alternatively, you can use cvs (note the somewhat strange
CVSROOTs) <br>
cvs -d <a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto::pserver:anonymous@git.tuis.net:/git/jdom.git">":pserver:anonymous@git.tuis.net:/git/jdom.git"</a>
co HEAD -d jdom <br>
cvs -d <a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto::pserver:anonymous@git.tuis.net:/git/jdom-contrib.git">":pserver:anonymous@git.tuis.net:/git/jdom-contrib.git"</a>
co HEAD -d jdom-contrib <br>
cvs -d <a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto::pserver:anonymous@git.tuis.net:/git/jdom-test.git">":pserver:anonymous@git.tuis.net:/git/jdom-test.git"</a>
co HEAD -d jdom-test <br>
----><br>
<br>
Depending on the levels of interest in this there will probably be
the requirement to migrate these repositories to a more reliable
server, etc. We'll cross that bridge if we get to it. <br>
<br>
Rolf <br>
<br>
<br>
<br>
<br>
<br>
<br>
On 22/07/2011 9:26 AM, Noel Grandin wrote:
<blockquote cite="mid:4E297A70.3070507@peralex.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<font face="Tahoma">Hi<br>
<br>
Rolf - How about modifying the package name to be org.jdom2 ?
That should make the people who want a new package name so as
not to step on old code happy.<br>
And can you put the code somewhere accessible?<br>
<br>
Thomas - how would you like to receive changes? As a diff
patch?<br>
<br>
Thanks, Noel Grandin<br>
<br>
</font><br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>