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] [Closed] (POOL-226) GenericKeyedObjectPool.ObjectTimestampPair fields could be made final without breaking compat?
Date Wed, 31 Dec 2014 16:38:13 GMT

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

Phil Steitz closed POOL-226.
----------------------------

> GenericKeyedObjectPool.ObjectTimestampPair fields could be made final without breaking
compat?
> ----------------------------------------------------------------------------------------------
>
>                 Key: POOL-226
>                 URL: https://issues.apache.org/jira/browse/POOL-226
>             Project: Commons Pool
>          Issue Type: Improvement
>            Reporter: Sebb
>            Priority: Minor
>             Fix For: 1.6.1
>
>
> The package protected static class GenericKeyedObjectPool.ObjectTimestampPair contains
two fields which are currently deprecated, pending making them final and private.
> Since the fields are package protected, surely they should only be used by Commons Pool
code? Does it make sense that any external code would use the fields? 
> Indeed can they be used?
> If the fields cannot legitimately be used by 3rd party code, then surely there's no need
to wait for a major release to change them?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message