Jeremy Boynes <[EMAIL PROTECTED]> wrote on 10/02/2006 02:43:22 PM: > On irc this morning the question came up about which version of the > spec the spec/sdo API related to. The conclusion was 2.0.1 + a couple > of methods from 2.1 but not all. > > Is this the case? Yes.
> If so, are we allowed to release a jar which does not correspond to > an official version of the spec? I know this is major problem for > APIs from the JCP. I don't know of anything that says we aren't. > If we are, do we want to do this? Would "good netizenship" imply that > we should keep versions in sync with published versions? We are officially 2.0.1. The only thing we've added from 2.1 is a couple of well marked new methods (names are still subject to change in the 2.1 spec). There is no change to any of the official 2.0.1 behavior. It shouldn't matter that we added the new methods since they won't affect users that don't call them. They are quite useful, however, for our own development. Our next release (M3) will officially move to the 2.1 interfaces, but we won't be fully 2.1 compliant (e.g., some methods will throw UnsupportedOpertationException). For that matter, we're also not fully 2.0.1 compliant now either. > > -- > Jeremy > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
