[jpa-spec users] [jsr338-experts] Re: Where is the JPA specification bug tracker heading?

From: Oliver Gierke <>
Date: Fri, 29 Apr 2016 15:46:37 +0200

Hi Werner,

I've been tracking this aspect for a long time already [0] and so far there wasn't any movement (not judging here, just stating facts).

I deliberately included the aspect in my original email as I wondered whether the recent development might have changed the general attitude of Oracle in that area and the migration in infrastructure might be a good chance to actually take that step.



> Am 29.04.2016 um 15:41 schrieb Werner Keil <>:
> Ollie,
> I'm afraid you're scratching a big itch not only of JPA.
> Especially the TCK (unlike CDI, JCache, JavaMoney, Portlet or Unit JSRs) is not Open Source at all including some of the very latest (new) JSRs like MVC or Security 1.0.
> Unlike Java Batch (or JPA in your case), Pivotal has not joined the EG of either, so hard to say, if it plans to leverage them where final.
> Of course there are many in the community, that would rather develop TCKs in the open, but it seems the Spec Lead(s) mostly at Oracle in these cases are reluctant or unable to meet this demand.
> Cheers,
> Werner
> Werner Keil | JCP Executive Committee Member, JSR 363 Co Spec Lead | Eclipse UOMo Lead, Babel Language Champion | Apache Committer
> Twitter @wernerkeil | @UnitAPI | @JSR354 | @AgoravaProj | @DeviceMap | #DevOps | #EclipseUOMo
> Skype werner.keil | Google+
> On Fri, Apr 29, 2016 at 3:27 PM, Oliver Gierke <> wrote:
> Hi all,
> given the recent announcement of the sunset of I was wondering where the spec leads plan to migrate the bug tracker? Are we going full GitHub (including specification sources, TCK etc.) just like other specifications (e.g. CDI) have been for quite some time?
> Cheers,
> Ollie

 * @author Oliver Gierke - Senior Software Engineer
 * @param email
 * @param phone +49-151-50465477
 * @param fax   +49-351-418898439
 * @param skype einsdreizehn
 * @see