Re: [jakartaee-tck-dev] Platform TCK run started

["Kevin Sutter" <sutter@xxxxxxxxxx>]

Any modifications
to the TCK buckets due to the removal of pruned technologies needs to be
thorough vetted.  Each of the respective Project teams needs to be
involved in determining the proper path forward, whether it means to remove
the tests completely or maybe modify them to remove the dependency.  I'm
not sure how Scott is handling this type of effort.  Maybe separate
Issues are required?  At least separate PRs.  And, we need to
ensure that proper representation from each Project is included in the
discussions.

If the TCKs in
question are part of the Platform (ie. EJB or Servlet), then these Issues
and/or PRs should be against the Platform TCK.  But, if the individual
Spec Project owns the TCKs (ie. Mail or CDI) and they get fed into the
Platform TCK, then the Issues and/or PRs should be against the individual
Project TCK repository.

---------------------------------------------------
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:
       Gurkan
Erdogdu <cgurkanerdogdu@xxxxxxxxx>
To:
       jakartaee-tck
developer discussions <jakartaee-tck-dev@xxxxxxxxxxx>
Date:
       06/09/2020
15:10
Subject:
       [EXTERNAL]
Re: [jakartaee-tck-dev] Platform TCK run started
Sent
by:        jakartaee-tck-dev-bounces@xxxxxxxxxxx

---

Also jakartaee-tck suite is not build
JAX_RPC using docker/build_jakartaeetck.sh because of compile time errors.

On Tue, Jun 9, 2020 at 10:46 PM Gurkan
Erdogdu <cgurkanerdogdu@xxxxxxxxx>
wrote:
Hi Kevin
You are right, lots of tests in EJB,
WebServices etc. depends to use JAX-RPC API? How can we adjust these tests?
Do we completely remove them?
Regards.
Gurkan

On Tue, Jun 9, 2020 at 10:32 PM Kevin
Sutter <sutter@xxxxxxxxxx>
wrote:
The jaxrpc test
suite should be removed (since jax-rpc is removed from Jakarta EE 9). 
There may be some dependencies on jax-rpc in other test suites that still
may need adjusting.  For example, Authorization might have a dependency
on JAX-RPC which needs to be removed or adjusted.  The removed technologies
will have a ripple effect across many of the test buckets...

---------------------------------------------------
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:        Gurkan
Erdogdu <cgurkanerdogdu@xxxxxxxxx>
To:        jakartaee-tck
developer discussions <jakartaee-tck-dev@xxxxxxxxxxx>
Date:        06/09/2020
14:21
Subject:        [EXTERNAL]
Re: [jakartaee-tck-dev] Platform TCK run started
Sent by:        jakartaee-tck-dev-bounces@xxxxxxxxxxx

---

I have seen JAX-RPC related errors in the TCK suite. Do we still need to
use JAX_RPC tests (in jaxrpc package)? I think this will be removed in
Jakarta EE9
Gurkan

On Tue, Jun 9, 2020 at 9:38 PM Gurkan Erdogdu <cgurkanerdogdu@xxxxxxxxx>
wrote:
Hi Scott
I am more than happy to help. Now trying to set up a project with TCK sources
in Eclipse.
Regards.
Gurkan

On Tue, Jun 9, 2020 at 8:54 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:
Hi,

We still need a volunteer to work on https://github.com/eclipse-ee4j/jakartaee-tck/issues/209(removing JAXR), as that is unassigned.  If you are available to work on tasks but not that one, we have plenty of other open issues as well.

We just started the nightly Platform TCK run with today's GlassFish master changes (which includes the ORB switch to use jakarta package classes).

https://ci.eclipse.org/jakartaee-tck/job/jakartaeetck-nightly-run-master/41/is the link for the test run.

From a quick glance at the test output, I randomly found a failure in  https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/master/682/testReport/junit/com.sun.ts.tests.compat13.ejb.tx/Client/jakartaeetck_run___compat13___txCompat13Test1which is failing because we still have javax.ejb.SessionBean references in archives that are stored in the TCK sources, such as compat13_ejb_tx.ear

https://github.com/eclipse-ee4j/jakartaee-tck/issues/313is for updating the archives saved in the Platform TCK source.  I asked on the issue why we aren't currently building the archives from source, does anyone know?  

Scott

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

--

Gurkan Erdogdu
http://gurkanerdogdu.blogspot.com


--
Gurkan Erdogdu
http://gurkanerdogdu.blogspot.com_______________________________________________
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

--

Gurkan Erdogdu
http://gurkanerdogdu.blogspot.com


-- 
Gurkan Erdogdu
http://gurkanerdogdu.blogspot.com_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev