Sorry Steve. I did not intend to bring releasing a new version of
GlassFish to question. I do believe we can accomplish the Jakarta
EE release goals without a new version of Eclipse GlassFish.
While we have said, we don't intend to create a new GlassFish
release, there appear to be additional artifacts that we think
will be required, across the projects -- these include revised
JavaDocs, possibly revised API JAR files. Maybe other component
elements.
A plan/recipe for each project needs to be worked out. Overall,
that's not the GlassFish project lead's responsibility, but I
don't know whose it is.
In addition the new TCKs must be delivered -- currently, that
delivery includes a copy of GlassFish since that's the only
currently known compatible implementation that we have to work
with.
All this needs to be pulled together -- in general, this is for
the Jakarta EE 8 project. Of which, the GlassFish project
deliverable (new version or old) is but one part -- Each of the
component projects may also have some work to do.
There isn't a firmly established home for the overall
deliverables and I don't know where these discussions are supposed
to take place.
-- Ed
On 4/16/2019 10:32 AM, Steve Millidge
(Payara) wrote:
All,
I am now confused. Recently I created a
release for GlassFish 5.2 stating it targeted Jakarta EE 8
certification. In the working group meeting it was suggested
that the goal would be to certify Eclipse GlassFish 5.1 as
both Java EE 8 and Jakarta EE 8. I therefore deleted the
release on the project.
So what’s the consensus on which version
will be Jakarta EE 8 compatible?
Steve
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/glassfish-dev