Hi Michael,
Michael Giannakopoulos wrote:
> Hello Andrian,
>
> Thanks for the quick and effective reply... Say we changed the files so as
> to apply to the standard of JRE 1.6... Then Apache Commons Library would
> became broken as far as the previous versions of JRE are concerned?
the HEAD rev
That is correct. Some of the commons libraries have existed for a long time,
and they are written to work with older JRE versions for backward
compatibility. Newer releases are written for newer JREs.
-Adrian
--- On Wed, 12/29/10, Michael Giannakopoulos wrote:
> Hello Andrian,
>
> Thanks for
Hello Andrian,
Thanks for the quick and effective reply... Say we changed the files so as
to apply to the standard of JRE 1.6... Then Apache Commons Library would
became broken as far as the previous versions of JRE are concerned?
The project was written for a JRE earlier than 1.5. Change your Eclipse
project settings to use a compiler prior to 1.5.
-Adrian
On 12/29/2010 12:18 PM, Michael Giannakopoulos wrote:
Hello to all of you guys,
I would like to ask a trivial for most of you question... As i see the
source code in
Hello to all of you guys,
I would like to ask a trivial for most of you question... As i see the
source code in Eclipse is full of warnings because IDE is complaining that
references to generic types should be parameterized... Wouldn't it be more
correct if we add to all generic types after their
