[jdom-interest] jdom 2.0 with generics
olivier.jaquemet at jalios.com
Thu Jul 21 08:23:51 PDT 2011
To that regard, I like the approach taken by several libraries when
making important change with backward compatibility, specially for
They change the package name ! That way, the only thing required for the
developper wanting to use the new version is a simple modification of
the import directive + the generics modification is required. And code
using the older library can be left untouched.
For example, apache commons lang 3.0 which has been release two days ago
is using this approach.
import org.apache.commons.lang -> import org.apache.commons.lang3
It allows older version of the library to seat next to the new one
without any glitches.
So +1 for JDom 2 with generics with a package name change.
On 21/07/2011 17:05, J Dalton wrote:
> If it breaks backward compatibility, surely those who do not
> want to (or are unable to) change their code could continue
> to use the earlier versions.
> That JDOM doesn't use generics has unfortunately become
> an argument against using JDOM.
> -- Jeff
> 2011/7/21 Thomas Scheffler<thomas.scheffler at uni-jena.de>:
>> Am 21.07.2011 15:01, schrieb Noel Grandin:
>>> Would there be any interest in doing a JDOM 2.0 targeting java 1.5+, but
>>> changing return types to use generics?
>>> I'd be happy to produce some patches, they're pretty straightforward.
>>> And I know I'd appreciate cleaning up some of code with better type
>> this topic has been around some time now. And the main concern was that this
>> change would break backward compatibility. Beside that using generics would
>> be great, as JAVA 5 itself is unsupported since 2009 now.
>> So if current code runs without changes: +1 from me.
>> To control your jdom-interest membership:
> To control your jdom-interest membership:
Olivier Jaquemet<olivier.jaquemet at jalios.com>
Ingénieur R&D Jalios S.A. - http://www.jalios.com/
More information about the jdom-interest