commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (POOL-167) ObjectTimestampPair - fields tstamp and value "deprecation"
Date Mon, 30 Aug 2010 01:43:53 GMT

     [ https://issues.apache.org/jira/browse/POOL-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Phil Steitz resolved POOL-167.
------------------------------

    Resolution: Fixed

Getters added in r990683.

> ObjectTimestampPair - fields tstamp and value "deprecation"
> -----------------------------------------------------------
>
>                 Key: POOL-167
>                 URL: https://issues.apache.org/jira/browse/POOL-167
>             Project: Commons Pool
>          Issue Type: Bug
>    Affects Versions: Nightly Builds
>            Reporter: Sebb
>            Priority: Minor
>             Fix For: 1.5.5
>
>
> ObjectTimestampPair - fields tstamp and value are marked deprecated:
> "this field will be made private and final in version 2.0"
> Making the fields final is fine, however it does not seem possible to make the fields
private without breaking a lot of existing code which needs read access to the fields.
> One way round this would be to add package-protected getter methods for the fields.
> This would allow the current code to be updated to avoid the deprecations.
> Does that seem like a sensible approach?
> If not, then at least the @deprecated comment ought to be changed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message