Hi
Had a call with Mike today about moving JCache
across to EE4J.
We have JCache 1.1 in the JCP review process now and
it should be out in a few weeks’ time. So we could consider
moving after that point.
The biggest issue to me is that, at least currently,
any new APIs will not be allowed to use javax. Today we use
javax.cache. This would mean that JCache 2 would need to change
its package name. We have 13 implementations out there and a
huge amount of user code that uses javax.cache. This would be an
extremely disruptive change.
In our case Oracle is a copyright owner along with
myself for the spec. As an owner, Oracle if they wished, should
be able to allow JCache 2 to continue to use the javax.cache
package even though the process has changed from JCP to the yet
unnamed and to be formed Eclipse Community Process.
Interested in anyone’s thoughts on this.
_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community