Uploaded image for project: 'Commons Pool'
  1. Commons Pool
  2. POOL-167

ObjectTimestampPair - fields tstamp and value "deprecation"

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • Nightly Builds
    • 1.5.5
    • None

    Description

      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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            sebb Sebb
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: