Hi all,
independently of the scope of the upcoming JPA specification I wondered what you're plans are about aligning the specification process of that upcoming version with a more state-of-the art style.
I've seen the CDI guys are leading by quite a bit compared to us (spec in Asciidoc, public repo for spec and API, public repo for TCK) and I wonder whether there might be any good reason for the next JPA spec not to follow that model. I've reserved the "jpa-spec" organization name on GitHub to avoid anyone is hijacking it as this email will become public. Happy to hand over the organization to anyone who wants to be in charge.
As it apparently has been decided that the scope is rather small for this iteration [0] it might be a chance to improve on meta things.
Cheers,
Ollie
[0]
https://java.net/projects/jpa-spec/lists/jsr338-experts/archive/2014-08/message/4
[1]
https://github.com/jpa-spec
--
/**
* @author Oliver Gierke - Senior Software Engineer
*
* @param email ogierke_at_pivotal.io
* @param phone +49-151-50465477
* @param fax +49-351-418898439
* @param skype einsdreizehn
* @see http://www.olivergierke.de
*/