Re: [jakartaee-tck-dev] [External] : Re: Draft pull request for adding M

[Gurunandan Rao <gurunandan.rao@xxxxxxxxxx>]

Hi Scott ,

thanks for raising pull, I have added my comments to the pull.

regards,

Guru

---

From: jakartaee-tck-dev <jakartaee-tck-dev-bounces@xxxxxxxxxxx> on behalf of Scott Marlow <smarlow@xxxxxxxxxx>
Sent: 26 August 2021 19:54
To: jakartaee-tck developer discussions <jakartaee-tck-dev@xxxxxxxxxxx>; Cesar Hernandez <chernandez@xxxxxxxxxxxxx>
Subject: [External] : Re: [jakartaee-tck-dev] Draft pull request for adding Maven pom to each Platform TCK test folder...

 

On 8/25/21 6:17 PM, Cesar Hernandez wrote:

Hi Scott,

Thank you for the details and PR.

I pull your draft PR and got stuck after "maven clean", I opened https://github.com/scottmarlow/jakartaee-tck/pull/3 to have a successful clean.

Hi Cesar,

Thank you for fixing ^, very much appreciated!  I merged your change and the [2] pr now includes it.

Scott

"clean install -DskipTests" currently fails with compilation error "com.sun.ts.lib.harness" does not exist as you described. 

We can discuss more on the September 8th (or 9th depending on your time zone) TCK zoom call [5].  Note that [5] is the TCK call agenda document and contains a link to the (Jakarta EE Specifications) calendar.

+1.

--

Regards

Cesar Hernandez

https://twitter.com/CesarHgt

http://www.tomitribe.com

https://www.tomitribe.io

On Tue, Aug 24, 2021 at 12:49 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:

To (start) addressing issue 51 [1], [2] adds a minimal maven `pom.xml` to each test folder using the existing test directories.  There are missing dependencies currently (so expect build failures), some that need to be discussed as to how to address (e.g. com.sun.javatest).

We are building still with Java SE 8 and will switch to Java SE 11 soon enough. 

If anyone wants to improve the initial pom.xml files, your help is greatly appreciated! 

If anyone wants to help eliminate the Java Test harness (com.sun.javatest [4]) missing dependencies in [2], your help is greatly appreciated!  This is an area that we need to explore to understand more.  Whomever looks at this part, needs to come up with different paths that we can choose from. 

We can discuss more on the September 8th (or 9th depending on your time zone) TCK zoom call [5].  Note that [5] is the TCK call agenda document and contains a link to the (Jakarta EE Specifications) calendar.

The initial refactoring goal is to have a place to explore updating each test folder to be able to run TCK tests against the different EE container test vehicles with JUnit5/TestNG + Arquillian. 

We also will integrate with any EE container tests produced by any of the Spec API teams (e.g. see [6][7] for possible examples).

Scott

[1] https://github.com/eclipse-ee4j/jakartaee-tck/issues/51
[2] https://github.com/eclipse-ee4j/jakartaee-tck/pull/735
[3] https://github.com/eclipse-ee4j/jakartaee-tck/tree/tckrefactor
[4] https://github.com/openjdk/jtharness
[5] https://docs.google.com/document/d/1V1dDLJkd14EDRMPeuI0VzPtU4Lbli8FFBd1pLDLlOrY/edit#
[6] https://github.com/eclipse-ee4j/batch-tck/
[7] https://github.com/eclipse-ee4j/jaxrs-api/pull/1002

_______________________________________________
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