Re: [jakartaee-tck-dev] What is the plan for building jaxb-tck?

[Edward Bratt <ed.bratt@xxxxxxxxxx>]

Scott,

Jakarta EE is the generic project name (at least that's how I'm using it
below).

We originally proposed that the very next release of Eclipse GlassFish
(after 5.1) would pass BOTH the Java EE stable TCKs (these are licensed
by Oracle) AND the TCKs built from the contributed source -- in
jakartaee-tck project repositories, and a hand-full of other
repositories (e.g. JavaMail TCK is located in the JavaMail project).

Once that is completed, Jakarta EE has a baseline from which it can
evolve both the run-time implementation, and the Specifications.

Jakarta EE 8 -- is intended to be the same as Java EE 8 -- this would be
a platform that passes both Java EE 8 and Jakarta EE 8 TCKs.

Jakarta EE 9 would build from Jakarta EE 8.

Make sense?

-- Ed


On 3/18/2019 11:40 AM, Scott Marlow wrote:
> Thanks Ed + others for the responses, much appreciated!
>
> On 3/15/19 1:59 PM, Ed Bratt wrote:
>> Hi Scott,
>>
>> We'd be grateful for assistance. I will let Bhat, Ankit and others
>> chime in about where you and/or other community members can best
>> contribute. 
>
> Great, thanks!  Let us know if we should ask our questions here or if
> a phone call meeting would be better for getting more of us familiar
> with the internal workings of the current CTS/TCK building jobs.  I've
> looked at some of them and I cannot tell if there is more than what I
> can view.
>
>> Once all the third party components are approved by the Eclipse EMO,
>> we can start moving the Jenkins work forward. There are other
>> components which will have to be adjusted as the platform moves to
>> higher Java SE versions. No doubt this will be part of the Jakarta EE
>> evolution work.
>
> Do you mean for Jakarta EE 9?
>
> The evolution work will be an interesting ride forward! :)
>
> Thanks,
> Scott