Re: [jakartaee-tck-dev] Jakarta Transaction signatures (maybe others)

[Lance Andersen <lance.andersen@xxxxxxxxxx>]

Hi Kevin,

There will  need to be signature files generated against the various Java SE version supported.

Depending on the JDK version used, will determine the signatures to run against.

Best

Lance

On Jun 10, 2020, at 2:40 PM, Kevin Sutter <sutter@xxxxxxxxxx> wrote:

As a reminder, all APIs need to be at the Java SE 8 source and binary levels.  The implementations need to support Java SE 11, but the APIs still need to be at the Java SE 8 level.  I'm not exactly clear on how these signature files get processed for the TCK, but when I see items proposed to be deleted related to Java SE 8 and APIs, it makes me nervous...  Thanks.

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



From:        Tom Jenkinson <tom.jenkinson@xxxxxxxxxx>
To:        Alwin Joseph <alwin.joseph@xxxxxxxxxx>
Cc:        jakartaee-tck developer discussions <jakartaee-tck-dev@xxxxxxxxxxx>
Date:        06/10/2020 11:44
Subject:        [EXTERNAL] Re: [jakartaee-tck-dev] Jakarta Transaction signatures (maybe        others)
Sent by:        jakartaee-tck-dev-bounces@xxxxxxxxxxx

---

I whatever you provided as [1] was not included in your message?

But Glassfish master seems to be using 2.0.0-RC2: https://github.com/eclipse-ee4j/glassfish/blob/master/appserver/pom.xml#L130. That version you can find in staging: https://jakarta.oss.sonatype.org/content/groups/staging/jakarta/transaction/jakarta.transaction-api/2.0.0-RC2/

On Wed, 10 Jun 2020 at 16:03, Alwin Joseph <alwin.joseph@xxxxxxxxxx> wrote:
Hi Tom,
As of now we have generated new signature file to be run in JDK8 as jakarta.transaction.sig_2.0_se8(using [1],  Is this the same jar that is integrated to glassfish ?)
The sig tests currently pass in standalone mode, but fails in jsp & servlet vehicles, this needs to be investigated.

We will remove the javax.* and also update the jakarta.transaction.sig_1.2_se11 as jakarta.transaction.sig_2.0_se11 to be run in JDK11.
Regards,
Alwin
On 10/06/20 7:18 pm, Tom Jenkinson wrote:
Hi,

I am not very familiar with the requirements on signatures, but when I  look at https://www.eclipse.org/lists/jakartaee-spec-project-leads/msg00413.htmland at https://github.com/eclipse-ee4j/jakartaee-tck/tree/master/src/com/sun/ts/tests/signaturetest/signature-repository, for Jakarta Transactions I am thinking:

1. We need to add a jakarta.transaction.sig_2.0_se11 (I am not sure what would go in there though)
2. The following should be removed:
   * jakarta.transaction.sig_1.2_se11
   * javax.transaction.sig_1.2_se8
   * javax.transaction.sig_1.3_se8

Thanks for your assistance,
Tom

_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev



_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev

Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037
Oracle Java Engineering 
1 Network Drive 
Burlington, MA 01803
Lance.Andersen@xxxxxxxxxx