I was completely unaware of
java.lang.Package().getSpecificationVersion(), very interesting! I've
taken a look at the Javadoc but am unable to see how I can override
this. In particular, our algorithm for determining compatibility is
quite different from the default behavior.
Regarding the three-part version number, I was thinking we needed this
to be able to test for compatibility without having to parse an integer
--we need to see if the major versions are the same, greater, less than,
etc. But perhaps this is not needed if our known incompatibilities are
encoded. Let me investigate this, and if at all possible I'll adjust to
a single integer (or String if getSpecificationVersion() makes sense).
Thanks,
David
Daniel John Debrunner wrote:
Jeremy Boynes wrote:
David Van Couvering (JIRA) wrote:
VERSION DETECTION
The Version class will be defined as a common class and is used to
define a version and check for compatibility between a consumer and
the common package. Here is a first pass at the methods on this class.
Do we need a custom implementation or can we use the version information
returned from java.lang.Package().getSpecificationVersion() ?
I agree, or can it be even simpler? Is a three part version number
really required for common components? Could a simple integer suffice?
Dan.
begin:vcard
fn:David W Van Couvering
n:Van Couvering;David W
org:Sun Microsystems, Inc.;Database Technology Group
email;internet:[EMAIL PROTECTED]
title:Senior Staff Software Engineer
tel;work:510-550-6819
tel;cell:510-684-7281
x-mozilla-html:TRUE
version:2.1
end:vcard
