As best I can tell - the branch for 1.2 does not yet exist. I like
the idea of 1.2 (Java 1.5 and JAXB) as it is a nice step forward for
us 1.1.x folks and would be happy to see 1.2 come in advance of 2.0.
I fear (perhaps wrongly) that the SPI will change for 2.0 - so that
might limit how quickly we can get 2.0 in the field. A 1.2 with
pretty much the same SPI as 1.1 - would be a neat partial step
forward that could quickly be deployed.
Since 286 branch is using 1.5 and JAXB - it would be a mistake to re-
develop the work - why not try to merge *some* of the 286 branch to
produce a possible 1.2.
Once thing that may or may not be implied in the "1.5" is a re-
factoring of APIs to use 1.5isms - like Generics across the board.
While I find this appealing on the face of it - this kind of
refactoring will make the 286 merge harder and harder - kind of a
long-term step in the wrong direction IMO.
So mebbe the right way to go is to look closely at the 286 branch and
pull in some cool stuff - make this be 1.2 - force Java 1.5 - get us
part way there - and wait for any 1.5 triggered refactoring until
after the merge.
Just thoughts from a non-committer.
Charles Severance
[EMAIL PROTECTED] www.dr-chuck.com
On Jul 17, 2007, at 12:06 AM, [EMAIL PROTECTED] wrote:
Elliot,
We need to hear from Torston, and, hopefully, Stefan on this issue.
Stefan should also comment on the 286 spec's time line.
I'd like to merge the 286 branch with the trunk and then move 286
into the trunk. But if the community is still hot for a 1.2
release, we should do it from the trunk, but try to commit all 1.2
patches to the 286 branch if it is not incompatible with the 286
implementation.
Java 5 and JAXB are being used in the 286 branch, so I do not see
the point in a 1.2 version. We have a stable 1.x line now. We
should move on (IMHO).
/Craig
