Re: Java-dev Digest, Vol 5, Issue 356

I'm not asking for you to comment on unreleased products. Java 1.5 is already shipping; What I'm asking is your "opinion" based on history/precedent of the "likelihood" that such a significant enhancement / backport (assuming they will fix it in 1.6 first and then bring it down) "might" make it into the 1.5 code base before all 1.5 maintenance work stops (which by my reckoning might be sometime in the next 6-18 months).

The answer determines how I proceed with "accommodating/working around" this issue.

There's a difference in a consumer asking "When will Apple's Java-Native next wiz-bang widget be shipping" and a developer inquiring about the life-expectancy of an existing code base from a maintenance point of view.

Thanks.

On Sep 26, 2008, at 9:08 AM, email@hidden wrote:

Mike,

What is the likelihood that such a significant change would make it
into a 1.5 maintenance release before it goes EOL in favor of 1.6?

I'm sorry, but we don't comment on unreleased products. If you've
filed a bug on it at http://bugreporter.apple.com, you should be
notified once a fix has made it into a developer preview.

Mike Swingler
Java Runtime Engineer
Apple Inc.