[
https://issues.apache.org/jira/browse/DERBY-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406088#comment-13406088
]
Knut Anders Hatlen commented on DERBY-5840:
-------------------------------------------
Thanks for cleaning this up, Rick. Looks like a good first step on the way to
making use of Java 5 language features.
I saw similar warnings a while ago when I looked into changing the source level
of the client code to 1.5 (with the ultimate goal of being able to push the
java.sql.Wrapper.unwrap() overrides to the base implementation classes, which
would allow us to simplify the class hierarchy). What I noticed, though, was
that changing the source level also made the compiler emit lots of deprecation
warnings, primarily for deprecated methods in java.util.Date. Those methods
were also deprecated in Java 1.4, so it wasn't obvious to me why changing the
source level would make the warnings show up.
> Clean up compiler warnings introduced by using Java 5 language features
> -----------------------------------------------------------------------
>
> Key: DERBY-5840
> URL: https://issues.apache.org/jira/browse/DERBY-5840
> Project: Derby
> Issue Type: Improvement
> Components: Miscellaneous
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
> Attachments: derby-5840-01-aa-compatibilityTests.diff
>
>
> Using Java 5 language features forces us to compile code at level 5 or
> higher. At this level, the compiler raises warnings not seen at lower levels.
> This issue is a place to discuss and attach cleanup to eliminate these
> warnings.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
