Better to present something solid and proper at EclipseCon Europe than forcing a Charade or something incomplete or just vaporware by OC1.
How many products will be Ready that implement either the Full Profile or Web Profile of Jakarta EE 8 by then? ;-)
Remember all those JavaOnes where e.g. JavaFX was presented as the “Next big thing” and it was merely a slightly improved Swing fork only to be completely thrown away and rewritten at least once in a following year?
Speak later,
Werner
The problem is that the Web Profile is defined *relative to* the full
platform. Without a full platform, you have nothing to base the Web
Profile on.
David Blevins wrote on 8/6/19 3:21 PM:
>> On Aug 6, 2019, at 2:32 PM, Kevin Sutter <sutter@xxxxxxxxxx> wrote:
>>
>> What about if we would limit our focus to just Jakarta EE 8 Web Profile?
>
> That's an *extremely* compelling idea.
>
> Given how intertwined the Full and WebProfile TCK is (the same), it may not pan out, but that doesn't mean we couldn't prioritize Web Profile specs first. If we're clever, maybe there's something we can do about the TCK issue, such as simply name it "jakartaee-webprofile-tck" and declare it can only be used for web profile certification despite having more tests.
>
> Also brainstorming out loud. Certainly worth talking about at tomorrow's spec meeting.
>
> -David
>
>
>
> _______________________________________________
> jakarta.ee-spec.committee mailing list
> jakarta.ee-spec.committee@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
>
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee