This has been discussed a lot lately. The reason is to add support for
Java 5 means removing support for people on Java versions previous to
that. You can make two releases, but that has the potential to cause
dependency problems in larger projects. So for now you have a few
warnings as the price for Java 1.4 people to be able to use JDOM. :)

-jh-

Hielke Hoeve wrote:
> Hi there,
>
> I was wondering if there is any reason why JDOM isn't using raw
> typing. I'm making a configuration parser for my own open source
> project but I'm using somewhat strict settings in Eclipse and I have a
> lot of warnings in my project about Lists being a raw type. I could
> add @SuppresWarnings to silence Eclipse about that particular line but
> I'd rather fix the "problem" than hiding it.
>
> If there isn't any reason I was wondering where I could commit or in
> another way present a JDOM version that does. I have attempted to
> alter the nightly build to use typing but it's quite a task.
>
> Greetings,
>
> Hielke Hoeve
> _______________________________________________
> To control your jdom-interest membership:
> http://www.jdom.org/mailman/options/jdom-interest/youraddr@(protected)
>
_______________________________________________
To control your jdom-interest membership:
http://www.jdom.org/mailman/options/jdom-interest/youraddr@(protected)