Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] Use of javax.* in new EE4J projects
It would be great to include JCache in EE4J!

Any API that continues to evolve through the JCP can continue to use javax.* package names as it always has.

We're still working out the rules for existing JCP specs that want to evolve outside of the JCP.  Clearly JCache is an existing JCP spec.

Completely new specs outside of the JCP should not expect to use javax.* package names.

Greg Luck wrote on 11/ 3/17 11:07 AM:
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. 

Regards

Greg Luck




_______________________________________________
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

Back to the top