From: Werner Keil <werner.keil_at_gmail.com>
Date: Wed, 18 Jul 2012 14:28:54 +0200

I'm not talking about the EE7 TCK, are you? You said, JPA 2.1 TCK is done,
so you're looking forward to 2.2 TCK which may (if the release train
contains it) be part of EE8.

EE8 is clearly be affected most by the Jigsaw disaster, many things the EE
Umbrella EG and involved companies offering containers were hoping for are
now delayed until at least EE9 if dependencies should be followed as they
were so far.

Thus there's at least an EE version where you may contribute improvements,
if that's what you were talking about?

No joke, it is actually a very sad situation[?]

On Wed, Jul 18, 2012 at 1:39 PM, Oliver Gierke <ogierke_at_vmware.com> wrote:

> Maybe it's me or I am not getting the joke :). How does Jigsaw not making
> into Java 8 relate to the general availability to get access to a specs TCK?
>
> Am 18.07.2012 um 11:47 schrieb Werner Keil:
>
> > Ollie/all,
> >
> > Thanks for your input. As we heard, some crucial part Java 8 has just
> died, so unless EE 8 was to skip 8 and build right onto 9, we're very
> likely to see a "less significant" or mostly "Maintainance" release of Java
> EE, too.
> >
> > If you want to improve things that don't make it into EE7, there might
> be a good chance to do so in 8<347.gif>
> >
> > Regards,
> > --
> > Werner Keil | JCP Executive Committee Member | Eclipse UOMo Lead
> > Twitter @wernerkeil | #Java_Social | #EclipseUOMo | #OpenDDR
> > Skype werner.keil | Google+ gplus.to/wernerkeil
> >
> > * Chip-to-Cloud Security Forum: September 19 2012, Nice, French Riviera.
> Werner Keil, JCP Executive Committee, JSR-321 EG Member will present
> "Trusted Computing API for Java™"
> >
> > * Eclipse Day Delft: September 27 2012, Delft, Netherlands. Werner Keil,
> Eclipse Committer, UOMo Lead, Mærsk Build Manager will present "Triple-E
> class Continuous Delivery with Hudson, Maven and Mylyn"
> >
> >
> > On Wed, Jul 18, 2012 at 11:27 AM, Oliver Gierke <ogierke_at_vmware.com>
> wrote:
> > Is there a chance we get official feedback in this regard? I don't care
> as much about the JPA 2.1 TCK as it's done. Still I'd like to help
> improving the upcoming version of the spec.
> >
> > I think this is crucial as I have seen tickets in implementors bug
> trackers with comments that bugs won't be fixed if the TCK doesn't actually
> bark. This way, it's actually not the spec driving the features/bugs of the
> implementation but a TCK not even members of the expert group get access
> to. This effectively creates a shadow spec which is a sub-optimal thing to
> see I think.
> >
> > Regards,
> > Ollie
> >
> > Am 17.07.2012 um 20:36 schrieb Harald Wellmann:
> >
> > > Am 17.07.2012 11:22, schrieb Oliver Gierke:
> > >>
> > >> Where can one get access to the standalone version of the JPA 2.0
> > >> TCK?
> > >>
> > >
> > > The TCK is still closed source, AFAIK.
> > >
> > > Over the past two years, I've found numerous spec-related bugs in all 3
> > > certified JPA 2.0 implementations (Eclipselink, Hibernate, OpenJPA)
> that
> > > should have been caught by the TCK.
> > >
> > > Some 18 months ago, when there was not even a public mailing list, I
> > > sent a request to the write-only list jsr-317-feedback_at_sun.com to
> > > release the TCK to the public.
> > >
> > > There is also the sad story of a fourth persistence provider who has
> > > given up on certification after trying in vain to get access to the
> TCK:
> > >
> > > http://datanucleus.blogspot.de/2011/01/jpa-tck-request-and-jpa21.html
> > >
> > > It is good to see that the current JCP is more open than former
> > > versions, but of course a community process that really deserves the
> > > name would open source all TCKs for all JSRs, no exceptions.
> > >
> > >> 2. How can we actually help out to improve the TCK?
> > >
> > > Well, we can't as long as the TCK isn't open. That's the main point why
> > > it doesn't make sense to keep it closed.
> > >
> > > The CDI TCK has been Open Source from the very beginning, part of the
> > > same Java EE 6 umbrella release and governed by the same JCP.
> > >
> > > I really don't see why this shouldn't work for JPA just as well.
> > >
> > > Best regards,
> > > Harald
> > >
> > >
> > >
> > >
> > >>
> > >> Cheers, Ollie
> > >>
> > >> [0] https://bugs.eclipse.org/bugs/show_bug.cgi?id=322579 [1]
> > >> https://hibernate.onjira.com/browse/HHH-6896 [2]
> > >> http://jcp.org/en/jsr/detail?id=317
> > >>
> > >
> > >
> >
> > --
> > /**
> > * @author Oliver Gierke - Senior Member Technical Staff
> > *
> > * @param email ogierke_at_vmware.com
> > * @param phone +49-351-30929001
> > * @param fax +49-351-418898439
> > * @param skype einsdreizehn
> > * @see http://www.olivergierke.de
> > */
> >
> >
> >
> >
> >
>
> --
> /**
> * @author Oliver Gierke - Senior Member Technical Staff
> *
> * @param email ogierke_at_vmware.com
> * @param phone +49-351-30929001
> * @param fax +49-351-418898439
> * @param skype einsdreizehn
> * @see http://www.olivergierke.de
> */
>
>