[jdom-interest] Java 1.5 language features.

[Mattias Jiderhamn]

Just make sure you start from the CVS head (i.e. 1.01) and not 1.0.

> That sounds the most likely option.  With no other changes to the API
> than the introduction of generics the new version would be a drop-in
> replacement.
>
> -- 
> Talden
>
> On 2/27/07, Bradley S. Huffman <hip at a.cs.okstate.edu> wrote:
>> Sounds like you and your group have the need and the expertise to
>> develop a Java 5
>> version and contribute it back to the community.  As long as this new
>> version doesn't
>> have any "extra features" not found in the non-generic version, I
>> can't think of a reason
>> anyone would object.
>>
>> Brad
>>
>> Talden writes:
>>
>> > 'fully' compatible is debatable with several hundred 'unchecked'
>> > warnings as a result of using the API.  You're right however, we
>> > absolutely haven't held back from the migration process because of
>> > JDOM.
>> >
>> > Now that the the areas in which we use JDOM are beginning to get a
>> > little more attention the question is being asked - is JDOM going to
>> > advance and if not should we keep using it given the compromises to
>> > our code-standards.
>> >
>> > The code-qualities issues arising from the excessive warnings (or the
>> > risks of suppressing them) are real issues - they are just not about
>> > functionality.  In fact in many ways they're about usability and that
>> > was the real point of JDOM from the beginning right?
>> >
>> > Is there work going on now (not yet released) that would make
>> > introducing a 2.0 (Java 5 + required) and maintaining the old 1.0
>> > (Java 1.4) a difficult endeavor?  Is there an issue with officially
>> > marking the 1.4 support as 'maintenance only'?