Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] EE4J FAQ

In the past, each JSR/technology/feature required the development of a TCK specific to that technology.  CDI has a TCK, JAX-RS has a TCK, JSON-P has a TCK, etc.  All of these TCKs were gathered together to create the CTS bucket for Java EE.  In addition to all of these individual TCKs, the CTS would also contain additional tests for the whole platform to show that these technologies are integrated properly.

One goal/requirement of this move to EE4J is for all TCKs and the complete CTS to run successfully for Java EE 8 using Glassfish as the RI.

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Java EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn:
https://www.linkedin.com/in/kevinwsutter



From:        Martijn Verburg <martijnverburg@xxxxxxxxx>
To:        EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Date:        10/13/2017 07:08 AM
Subject:        Re: [ee4j-community] EE4J FAQ
Sent by:        ee4j-community-bounces@xxxxxxxxxxx




Not sure to be honest.

Cheers,
Martijn


On 13 October 2017 at 12:22, John Hogan <jhogan515@xxxxxxxxx> wrote:
Hello Martin.

By TCK, are they referring to what used to be called the CTS, for Compatibility Test Suite?  If so, I think it would be helpful if they stick with the same acronym/name.  Just my two cents worth.  Thanks.

John Hogan

http://www.oracle.com/technetwork/java/javaee/javaee-faq-jsp-135209.html


On Fri, Oct 13, 2017 at 3:58 AM, Martijn Verburg <martijnverburg@xxxxxxxxx> wrote:
Hi Wayne,

This is great!  Some quick further feedback:

* The term "technology compatibility kits"is used in the first paragraph, would be worth using / defining the TCK acronym there as well.
* The first instance of the Aquarium blog posts mention needs to be linked.
* Might be worth putting javax and other related code mentions in code font so it stands out to readers
* +1 to linking to the license

Thanks again for pulling this together.


Cheers,
Martijn


On 12 October 2017 at 21:30, John D. Ament <john.d.ament@xxxxxxxxx> wrote:


On Oct 12, 2017 4:20 PM, "Wayne Beaton" <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx> wrote:
I'm glad that you find it useful.

I should clarify... I just pushed out the FAQ. Most of the work was done by others.

That explains the tense & subject changes throughout :-)

I would recommend linking to the EPLv2 when you mention licensing.  You may also want to link to some definition of what a TLP is in eclipse terms.



Wayne

_______________________________________________
ee4j-community mailing list

ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/ee4j-community



_______________________________________________
ee4j-community mailing list

ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/ee4j-community



_______________________________________________
ee4j-community mailing list

ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/ee4j-community



_______________________________________________
ee4j-community mailing list

ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/ee4j-community

_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_ee4j-2Dcommunity&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=R9dtOS3afYnRUmu_zogmh0VnVYl2tse_V7QBUA9yr_4&m=zpamIZ86GhMsPUzQ7ut57oPiR9sro-WAgJZZdpQQFXM&s=WwyyVbWru_g2-inoukZvTsrxD1XuAFWsh29pnsUmZ0U&e=




Back to the top