Jenkins build is still unstable: TomEE » tomee-9.x-build-full #463

[Apache Jenkins Server]

See 

[jira] [Updated] (TOMEE-4158) Jakarta Bean Validation TCK

[Richard Zowalla (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Zowalla updated TOMEE-4158:
---
Fix Version/s: 10.0.0-M2

> Jakarta Bean Validation TCK
> ---
>
> Key: TOMEE-4158
> URL: https://issues.apache.org/jira/browse/TOMEE-4158
> Project: TomEE
>  Issue Type: Sub-task
>Reporter: David Blevins
>Assignee: Jean-Louis Monteiro
>Priority: Major
> Fix For: 10.0.0-M2
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> see https://jakarta.ee/specifications/bean-validation/3.0/ for additional 
> details 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (TOMEE-4158) Jakarta Bean Validation TCK

[Richard Zowalla (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Zowalla resolved TOMEE-4158.

Resolution: Fixed

> Jakarta Bean Validation TCK
> ---
>
> Key: TOMEE-4158
> URL: https://issues.apache.org/jira/browse/TOMEE-4158
> Project: TomEE
>  Issue Type: Sub-task
>Reporter: David Blevins
>Assignee: Jean-Louis Monteiro
>Priority: Major
> Fix For: 10.0.0-M2
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> see https://jakarta.ee/specifications/bean-validation/3.0/ for additional 
> details 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (TOMEE-4165) Jakarta JSON Processing TCK

[Richard Zowalla (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Zowalla resolved TOMEE-4165.

Resolution: Fixed

Current main passes jsonp-tck.

> Jakarta JSON Processing TCK
> ---
>
> Key: TOMEE-4165
> URL: https://issues.apache.org/jira/browse/TOMEE-4165
> Project: TomEE
>  Issue Type: Sub-task
>Reporter: David Blevins
>Assignee: Jean-Louis Monteiro
>Priority: Major
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> see https://jakarta.ee/specifications/jsonp/2.1/ for additional details 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (TOMEE-4165) Jakarta JSON Processing TCK

[Richard Zowalla (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Zowalla updated TOMEE-4165:
---
Fix Version/s: 10.0.0-M2

> Jakarta JSON Processing TCK
> ---
>
> Key: TOMEE-4165
> URL: https://issues.apache.org/jira/browse/TOMEE-4165
> Project: TomEE
>  Issue Type: Sub-task
>Reporter: David Blevins
>Assignee: Jean-Louis Monteiro
>Priority: Major
> Fix For: 10.0.0-M2
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> see https://jakarta.ee/specifications/jsonp/2.1/ for additional details 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (TOMEE-4164) Jakarta JSON Binding TCK

[Richard Zowalla (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Zowalla resolved TOMEE-4164.

Fix Version/s: 10.0.0-M2
   Resolution: Fixed

Current main passes jsonb-tck.

> Jakarta JSON Binding TCK
> 
>
> Key: TOMEE-4164
> URL: https://issues.apache.org/jira/browse/TOMEE-4164
> Project: TomEE
>  Issue Type: Sub-task
>Reporter: David Blevins
>Assignee: Jean-Louis Monteiro
>Priority: Major
> Fix For: 10.0.0-M2
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> see https://jakarta.ee/specifications/jsonb/3.0/ for additional details 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (TOMEE-4325) JAX-RS TCK: Signature Tests

[Richard Zowalla (Jira)]

Richard Zowalla created TOMEE-4325:
--

 Summary: JAX-RS TCK: Signature Tests
 Key: TOMEE-4325
 URL: https://issues.apache.org/jira/browse/TOMEE-4325
 Project: TomEE
  Issue Type: Sub-task
Affects Versions: 10.0.0-M1
Reporter: Richard Zowalla


Signature tests are failing with

 
{code:java}
Missing Fields
 jakarta.ws.rs.core.Cookie:  field public final static int 
jakarta.ws.rs.core.Cookie.DEFAULT_VERSION = 1
affected jakarta.ws.rs.core.NewCookie
 jakarta.ws.rs.core.NewCookie:   field public final static int 
jakarta.ws.rs.core.NewCookie.DEFAULT_MAX_AGE = -1
 Added Fields
 jakarta.ws.rs.core.Cookie:  field public final static int 
jakarta.ws.rs.core.Cookie.DEFAULT_VERSION
affected jakarta.ws.rs.core.NewCookie
 jakarta.ws.rs.core.NewCookie:   field public final static int 
jakarta.ws.rs.core.NewCookie.DEFAULT_MAX_AGE
 duplicate messages suppressed: 2 {code}
However, the API JAR to test contains those fields. Requires some investigation.

 

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (TOMEE-4324) JAX-RS TCK: JsonbContextProviderIT.shouldUseApplicationProvidedJsonbInstance

[Richard Zowalla (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Zowalla updated TOMEE-4324:
---
Summary: JAX-RS TCK: 
JsonbContextProviderIT.shouldUseApplicationProvidedJsonbInstance  (was: JAX-RS 
TCK: )

> JAX-RS TCK: JsonbContextProviderIT.shouldUseApplicationProvidedJsonbInstance
> 
>
> Key: TOMEE-4324
> URL: https://issues.apache.org/jira/browse/TOMEE-4324
> Project: TomEE
>  Issue Type: Sub-task
>Affects Versions: 10.0.0-M1
>Reporter: Richard Zowalla
>Priority: Major
>
> [ERROR] JsonbContextProviderIT.shouldUseApplicationProvidedJsonbInstance:106 
> » Processing No message body writer has been found for class 
> ee.jakarta.tck.ws.rs.spec.contextprovider.JsonbContextProviderIT$POJO, 
> ContentType: application/json



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (TOMEE-4324) JAX-RS TCK:

[Richard Zowalla (Jira)]

Richard Zowalla created TOMEE-4324:
--

 Summary: JAX-RS TCK: 
 Key: TOMEE-4324
 URL: https://issues.apache.org/jira/browse/TOMEE-4324
 Project: TomEE
  Issue Type: Sub-task
Affects Versions: 10.0.0-M1
Reporter: Richard Zowalla


[ERROR] JsonbContextProviderIT.shouldUseApplicationProvidedJsonbInstance:106 » 
Processing No message body writer has been found for class 
ee.jakarta.tck.ws.rs.spec.contextprovider.JsonbContextProviderIT$POJO, 
ContentType: application/json



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (TOMEE-4323) JAX-RS TCK: JAXRSClientIT.featureIsRegisteredTest

[Richard Zowalla (Jira)]

Richard Zowalla created TOMEE-4323:
--

 Summary: JAX-RS TCK: JAXRSClientIT.featureIsRegisteredTest
 Key: TOMEE-4323
 URL: https://issues.apache.org/jira/browse/TOMEE-4323
 Project: TomEE
  Issue Type: Sub-task
Affects Versions: 10.0.0-M1
Reporter: Richard Zowalla


[ERROR] 
JAXRSClientIT.featureIsRegisteredTest:93->JAXRSCommonClient.assertEquals:721 
[Ljava.lang.Object;@2227a6c1 ==> expected:  but was: 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (TOMEE-4322) JAX-RS TCK: JAXRSClientIT.dynamicFeatureIsRegisteredTest

[Richard Zowalla (Jira)]

Richard Zowalla created TOMEE-4322:
--

 Summary: JAX-RS TCK: JAXRSClientIT.dynamicFeatureIsRegisteredTest
 Key: TOMEE-4322
 URL: https://issues.apache.org/jira/browse/TOMEE-4322
 Project: TomEE
  Issue Type: Sub-task
Affects Versions: 10.0.0-M1
Reporter: Richard Zowalla


[ERROR] 
JAXRSClientIT.dynamicFeatureIsRegisteredTest:111->JAXRSCommonClient.assertEquals:721
 [Ljava.lang.Object;@57aa341b ==> expected:  but was: 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (TOMEE-4321) Fix JAX-RS TCK Test Failures

[Richard Zowalla (Jira)]

Richard Zowalla created TOMEE-4321:
--

 Summary: Fix JAX-RS TCK Test Failures
 Key: TOMEE-4321
 URL: https://issues.apache.org/jira/browse/TOMEE-4321
 Project: TomEE
  Issue Type: Bug
Affects Versions: 10.0.0-M1
Reporter: Richard Zowalla


We have setup the JAX-RS TCK (3.1.5) and have some remaining test failures, 
which deserve investigation.

This ticket is used as a summary to track progress on those tests



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Jenkins build is still unstable: TomEE » master-build-full #1358

[Apache Jenkins Server]

See 

Jenkins build became unstable: TomEE » master-build-full » TomEE :: Examples :: Simple Stateful Pojo Callbacks #1358

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » master-build-full » TomEE :: Container :: Core #1358

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » master-build-quick #594

[Apache Jenkins Server]

See 

Jenkins build is back to normal : TomEE » master-build-full-itests #147

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » master-build-quick » TomEE :: Container :: Core #593

[Apache Jenkins Server]

See 

Jenkins build became unstable: TomEE » master-build-quick » TomEE :: Container :: Loader #593

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » master-build-full-tck #136

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » master-build-full-tck » TomEE :: TCK :: MicroProfile Metrics TCK #136

[Apache Jenkins Server]

See 

Jenkins build is still unstable: TomEE » master-build-quick » TomEE :: Container :: Core #592

[Apache Jenkins Server]

See 

Jenkins build is still unstable: TomEE » master-build-quick #592

[Apache Jenkins Server]

See 

(tomee) branch regenerate_boms_after_dep_upgrade deleted (was efac1f77c0)

[github-bot]

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch regenerate_boms_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/tomee.git


 was efac1f77c0 Merge pull request #1123 from 
apache/regenerate_boms_after_dep_upgrade

The revisions that were on this branch are still contained in
other references; therefore, this change does not discard any commits
from the repository.

(tomee) branch regenerate_boms_after_dep_upgrade updated (67addc60d4 -> efac1f77c0)

[github-bot]

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch regenerate_boms_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/tomee.git


from 67addc60d4 Minor: Regenerated BOMs for 
75ec55cb2b2cbc2ff2476989cda5adac07531a30
 add d4080a4061 Minor: Regenerated BOMs for 
35d837c5f3f0d0ff313526fcf64799e6d3dfdea5 (#1122)
 add efac1f77c0 Merge pull request #1123 from 
apache/regenerate_boms_after_dep_upgrade

No new revisions were added by this update.

Summary of changes:

(tomee) 01/01: Merge pull request #1123 from apache/regenerate_boms_after_dep_upgrade

[rzo1]

This is an automated email from the ASF dual-hosted git repository.

rzo1 pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomee.git

commit efac1f77c04b3a84ea3f892e2f067cc1c350ca79
Merge: d4080a4061 67addc60d4
Author: Richard Zowalla <13417392+r...@users.noreply.github.com>
AuthorDate: Mon Apr 22 11:27:32 2024 +0200

Merge pull request #1123 from apache/regenerate_boms_after_dep_upgrade

Regenerated BOMs after dependency upgrades

(tomee) branch main updated (d4080a4061 -> efac1f77c0)

[rzo1]

This is an automated email from the ASF dual-hosted git repository.

rzo1 pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/tomee.git


from d4080a4061 Minor: Regenerated BOMs for 
35d837c5f3f0d0ff313526fcf64799e6d3dfdea5 (#1122)
 add 67addc60d4 Minor: Regenerated BOMs for 
75ec55cb2b2cbc2ff2476989cda5adac07531a30
 new efac1f77c0 Merge pull request #1123 from 
apache/regenerate_boms_after_dep_upgrade

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:

(tomee) branch regenerate_boms_after_dep_upgrade updated (01ca3c9257 -> 67addc60d4)

[github-bot]

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch regenerate_boms_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/tomee.git


omit 01ca3c9257 Minor: Regenerated BOMs for 
35d837c5f3f0d0ff313526fcf64799e6d3dfdea5
 add 75ec55cb2b Align with TomEE 9.x version by removing unnecessary 
excludes
 add 67addc60d4 Minor: Regenerated BOMs for 
75ec55cb2b2cbc2ff2476989cda5adac07531a30

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (01ca3c9257)
\
 N -- N -- N   refs/heads/regenerate_boms_after_dep_upgrade 
(67addc60d4)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 tomee/tomee-microprofile/mp-common/pom.xml | 10 --
 1 file changed, 10 deletions(-)

(tomee) branch main updated: Minor: Regenerated BOMs for 35d837c5f3f0d0ff313526fcf64799e6d3dfdea5 (#1122)

[rzo1]

This is an automated email from the ASF dual-hosted git repository.

rzo1 pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomee.git


The following commit(s) were added to refs/heads/main by this push:
 new d4080a4061 Minor: Regenerated BOMs for 
35d837c5f3f0d0ff313526fcf64799e6d3dfdea5 (#1122)
d4080a4061 is described below

commit d4080a40617e31739d33ed0ad80165bc5d2bd693
Author: github-actions[bot] 
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Mon Apr 22 11:17:42 2024 +0200

Minor: Regenerated BOMs for 35d837c5f3f0d0ff313526fcf64799e6d3dfdea5 (#1122)

Signed-off-by: GitHub 
Co-authored-by: rzo1 
---
 boms/tomee-microprofile/pom.xml | 33 -
 boms/tomee-plume/pom.xml| 33 -
 boms/tomee-plus/pom.xml | 33 -
 3 files changed, 99 deletions(-)

diff --git a/boms/tomee-microprofile/pom.xml b/boms/tomee-microprofile/pom.xml
index bcb0036533..9e8208aeff 100644
--- a/boms/tomee-microprofile/pom.xml
+++ b/boms/tomee-microprofile/pom.xml
@@ -331,17 +331,6 @@
 
   
 
-
-  io.smallrye.reactive
-  mutiny
-  1.8.0
-  
-
-  *
-  *
-
-  
-
 
   io.smallrye
   jandex
@@ -397,17 +386,6 @@
 
   
 
-
-  io.smallrye
-  smallrye-health-api
-  4.0.1
-  
-
-  *
-  *
-
-  
-
 
   io.smallrye
   smallrye-health
@@ -2014,17 +1992,6 @@
 
   
 
-
-  org.glassfish
-  jakarta.json
-  2.0.1
-  
-
-  *
-  *
-
-  
-
 
   org.hsqldb
   hsqldb
diff --git a/boms/tomee-plume/pom.xml b/boms/tomee-plume/pom.xml
index 833afb818f..ffd11ccf2d 100644
--- a/boms/tomee-plume/pom.xml
+++ b/boms/tomee-plume/pom.xml
@@ -331,17 +331,6 @@
 
   
 
-
-  io.smallrye.reactive
-  mutiny
-  1.8.0
-  
-
-  *
-  *
-
-  
-
 
   io.smallrye
   jandex
@@ -397,17 +386,6 @@
 
   
 
-
-  io.smallrye
-  smallrye-health-api
-  4.0.1
-  
-
-  *
-  *
-
-  
-
 
   io.smallrye
   smallrye-health
@@ -2147,17 +2125,6 @@
 
   
 
-
-  org.glassfish
-  jakarta.json
-  2.0.1
-  
-
-  *
-  *
-
-  
-
 
   org.hsqldb
   hsqldb
diff --git a/boms/tomee-plus/pom.xml b/boms/tomee-plus/pom.xml
index 16ae513f4b..4aba4fb895 100644
--- a/boms/tomee-plus/pom.xml
+++ b/boms/tomee-plus/pom.xml
@@ -331,17 +331,6 @@
 
   
 
-
-  io.smallrye.reactive
-  mutiny
-  1.8.0
-  
-
-  *
-  *
-
-  
-
 
   io.smallrye
   jandex
@@ -397,17 +386,6 @@
 
   
 
-
-  io.smallrye
-  smallrye-health-api
-  4.0.1
-  
-
-  *
-  *
-
-  
-
 
   io.smallrye
   smallrye-health
@@ -2147,17 +2125,6 @@
 
   
 
-
-  org.glassfish
-  jakarta.json
-  2.0.1
-  
-
-  *
-  *
-
-  
-
 
   org.hsqldb
   hsqldb

(tomee) branch main updated (35d837c5f3 -> 75ec55cb2b)

[rzo1]

This is an automated email from the ASF dual-hosted git repository.

rzo1 pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/tomee.git


from 35d837c5f3 TOMEE-4320 - TomEE 10 leaks jakarta.json from Smallrye into 
/lib
 add 75ec55cb2b Align with TomEE 9.x version by removing unnecessary 
excludes

No new revisions were added by this update.

Summary of changes:
 tomee/tomee-microprofile/mp-common/pom.xml | 10 --
 1 file changed, 10 deletions(-)

(tomee) branch regenerate_boms_after_dep_upgrade created (now 01ca3c9257)

[github-bot]

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch regenerate_boms_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/tomee.git


  at 01ca3c9257 Minor: Regenerated BOMs for 
35d837c5f3f0d0ff313526fcf64799e6d3dfdea5

No new revisions were added by this update.

[jira] [Resolved] (TOMEE-4320) TomEE 10 leaks jakarta.json from Smallrye into /lib

[Richard Zowalla (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Zowalla resolved TOMEE-4320.

Resolution: Fixed

> TomEE 10 leaks jakarta.json from Smallrye into /lib
> ---
>
> Key: TOMEE-4320
> URL: https://issues.apache.org/jira/browse/TOMEE-4320
> Project: TomEE
>  Issue Type: Bug
>Affects Versions: 10.0.0-M1
>Reporter: Richard Zowalla
>Assignee: Richard Zowalla
>Priority: Major
> Fix For: 10.0.0-M2
>
>
> [~mawiesne] noticed the absence of jakarta.json in TomEE 9.1.3 compared to 
> 9.1.2
> Actually, the fix from 
> [https://github.com/apache/tomee/commit/aba954a0f2fa949d9405a6d47c4d7f8d72190a7a]
>  wasn't ported to TomEE 10.x



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

(tomee) branch main updated: TOMEE-4320 - TomEE 10 leaks jakarta.json from Smallrye into /lib

[rzo1]

This is an automated email from the ASF dual-hosted git repository.

rzo1 pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomee.git


The following commit(s) were added to refs/heads/main by this push:
 new 35d837c5f3 TOMEE-4320 - TomEE 10 leaks jakarta.json from Smallrye into 
/lib
35d837c5f3 is described below

commit 35d837c5f3f0d0ff313526fcf64799e6d3dfdea5
Author: Richard Zowalla 
AuthorDate: Mon Apr 22 11:02:07 2024 +0200

TOMEE-4320 - TomEE 10 leaks jakarta.json from Smallrye into /lib
---
 tomee/tomee-microprofile/mp-common/pom.xml | 8 
 1 file changed, 8 insertions(+)

diff --git a/tomee/tomee-microprofile/mp-common/pom.xml 
b/tomee/tomee-microprofile/mp-common/pom.xml
index cb9d2bf3b5..74e98ded34 100644
--- a/tomee/tomee-microprofile/mp-common/pom.xml
+++ b/tomee/tomee-microprofile/mp-common/pom.xml
@@ -237,6 +237,14 @@
   jakarta.json
   jakarta.json-api
 
+
+  org.glassfish
+  jakarta.json
+
+
+  io.smallrye
+  smallrye-health-api
+
 
   *
   microprofile-health-api

[jira] [Created] (TOMEE-4320) TomEE 10 leaks jakarta.json from Smallrye into /lib

[Richard Zowalla (Jira)]

Richard Zowalla created TOMEE-4320:
--

 Summary: TomEE 10 leaks jakarta.json from Smallrye into /lib
 Key: TOMEE-4320
 URL: https://issues.apache.org/jira/browse/TOMEE-4320
 Project: TomEE
  Issue Type: Bug
Affects Versions: 10.0.0-M1
Reporter: Richard Zowalla
Assignee: Richard Zowalla
 Fix For: 10.0.0-M2


[~mawiesne] noticed the absence of jakarta.json in TomEE 9.1.3 compared to 9.1.2

Actually, the fix from 
[https://github.com/apache/tomee/commit/aba954a0f2fa949d9405a6d47c4d7f8d72190a7a]
 wasn't ported to TomEE 10.x



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Build failed in Jenkins: TomEE » master-build-full-itests #145

[Apache Jenkins Server]

See 


Changes:


--
[...truncated 1.27 MB...]
error: unable to read sha1 file of 
tomee/tomee-microprofile/mp-common/src/main/resources/META-INF/services/jakarta.servlet.ServletContainerInitializer
 (ccc38a2e9cb54f66bbd271582e7b3936cb310d9a)
error: unable to read sha1 file of 
tomee/tomee-microprofile/mp-common/src/main/resources/META-INF/services/jakarta.ws.rs.ext.Providers
 (b7efaf9a188bccb8e781c6b5bdcc5deaf48f8b2a)
error: unable to read sha1 file of 
tomee/tomee-microprofile/mp-common/src/main/resources/META-INF/services/org.eclipse.microprofile.config.spi.ConfigSource
 (2928028438b6ab22f6728d426e4f53513e59e220)
error: unable to read sha1 file of 
tomee/tomee-microprofile/mp-common/src/main/resources/META-INF/services/org.eclipse.microprofile.opentracing.ClientTracingRegistrarProvider
 (485cef5544c7726690e8736493cdeedf3b4bae6d)
error: unable to read sha1 file of 
tomee/tomee-microprofile/mp-common/src/main/resources/io/smallrye/metrics/base-metrics.properties
 (0cc48b9b3b5281d4f1e4a5c03c0725a03f09ee28)
error: unable to read sha1 file of 
tomee/tomee-microprofile/mp-common/src/main/resources/io/smallrye/metrics/vendor-metrics.properties
 (ed922ab3505866d65aab4988a97714ec66dec197)
error: unable to read sha1 file of tomee/tomee-microprofile/pom.xml 
(f49d4b652daf837c4ce72baa95495919cc39794e)
error: unable to read sha1 file of 
tomee/tomee-microprofile/tomee-microprofile-webapp/pom.xml 
(e833cbc3e93df88403d82fdaa190c16ae96ea115)
error: unable to read sha1 file of 
tomee/tomee-microprofile/tomee-microprofile-webapp/src/main/resources/META-INF/LICENSE
 (d02a8ab101dfa5dd183f13ad46d3ddb306227209)
error: unable to read sha1 file of 
tomee/tomee-microprofile/tomee-microprofile-webapp/src/main/resources/META-INF/org.apache.tomee/service-jar.xml
 (dd6c6e5b07f0c543a86d79263d92ec3ca8070d74)
error: unable to read sha1 file of 
tomee/tomee-microprofile/tomee-microprofile-webapp/src/main/resources/juli.properties
 (873ce5065bab3f634a70d47450837afee149a8b2)
error: unable to read sha1 file of tomee/tomee-mojarra/pom.xml 
(6aaa4ced230d50d0e9c5001f2dfc737e9a6d9e7c)
error: unable to read sha1 file of 
tomee/tomee-mojarra/src/main/java/org/apache/tomee/mojarra/TomEEInjectionProvider.java
 (8620a0a80bddf4813ba39f8a9b91e5c3ffbb597e)
error: unable to read sha1 file of 
tomee/tomee-mojarra/src/main/resources/META-INF/services/com.sun.faces.spi.injectionprovider
 (d4ae0cc8ac2679f88b046c93c963d38083713692)
error: unable to read sha1 file of tomee/tomee-myfaces/pom.xml 
(0bb1ae89ad406c12b994bfb6845012d459251db0)
error: unable to read sha1 file of 
tomee/tomee-myfaces/src/main/java/org/apache/tomee/myfaces/TomEEAnnotationProvider.java
 (cc12e36c1374e627e353b8fecd55d14afd709f4c)
error: unable to read sha1 file of 
tomee/tomee-myfaces/src/main/java/org/apache/tomee/myfaces/TomEEAnnotationProviderFactory.java
 (c2acc2d95b6b6119daceb9d95391f7b94335d63b)
error: unable to read sha1 file of 
tomee/tomee-myfaces/src/main/java/org/apache/tomee/myfaces/TomEEFacesConfigResourceProvider.java
 (4ce83073bf65206347362dbffad1ac84ab162494)
error: unable to read sha1 file of 
tomee/tomee-myfaces/src/main/java/org/apache/tomee/myfaces/TomEEFacesConfigResourceProviderFactory.java
 (8fd603f857ff3901426c81cd50b03dc4c04a0d8b)
error: unable to read sha1 file of 
tomee/tomee-myfaces/src/main/java/org/apache/tomee/myfaces/TomEEMyFacesContainerInitializer.java
 (8fd7b530964db4da149ade686c0324f9ef5072c1)
error: unable to read sha1 file of 
tomee/tomee-myfaces/src/main/java/org/apache/tomee/myfaces/TomEEMyFacesContextListener.java
 (48c6694a0d60c11476a5545e88327eba5d78956f)
error: unable to read sha1 file of 
tomee/tomee-myfaces/src/main/java/org/apache/tomee/myfaces/TomEEWorkaroundFacesServlet.java
 (b50a02a387d16b64ef6aa5d861b7e605ea4e2649)
error: unable to read sha1 file of 
tomee/tomee-myfaces/src/main/resources/META-INF/services/org.apache.myfaces.spi.AnnotationProviderFactory
 (32e52858253e699985082ec5b8fbd239d6deccf7)
error: unable to read sha1 file of 
tomee/tomee-myfaces/src/main/resources/META-INF/services/org.apache.myfaces.spi.FacesConfigResourceProviderFactory
 (85d31c3a4e6e9b7b0f131fce7ef39d09b9ac95a5)
error: unable to read sha1 file of tomee/tomee-overlay-runner/pom.xml 
(92beab08f2096d70051cd8b84e4c7ffe8dc002bc)
error: unable to read sha1 file of 
tomee/tomee-overlay-runner/src/main/java/org/apache/tomee/overlay/Deployer.java 
(4d1b12a74ac125e0d4fdebaa92d018b84752d21e)
error: unable to read sha1 file of 
tomee/tomee-overlay-runner/src/main/java/org/apache/tomee/overlay/TomEEOverlayRunner.java
 (43d01c7c0f9754a22d6dd4e1b24995f9e69accaa)
error: unable to read sha1 file of 
tomee/tomee-overlay-runner/src/main/resources/META-INF/services/jakarta.servlet.ServletContainerInitializer
 (d8e25b1c71cdf0a4ee6a35511486fb95676ba419)
error: unable to read sha1 file of 
tomee/tomee-plume-webapp/src/main/assembly/war.xml 

(tomee) branch main updated: Tweak ManagedScheduledExecutorServiceTest timing (which is often causing CI failures) The bad feeling remains that I only fixed 1 of 30 ugly timings :/

[rzo1]

This is an automated email from the ASF dual-hosted git repository.

rzo1 pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomee.git


The following commit(s) were added to refs/heads/main by this push:
 new 1d0d439486 Tweak ManagedScheduledExecutorServiceTest timing (which is 
often causing CI failures) The bad feeling remains that I only fixed 1 of 30 
ugly timings :/
1d0d439486 is described below

commit 1d0d439486c2967183b0c610b7d664fdb6ff0602
Author: Richard Zowalla 
AuthorDate: Mon Apr 22 10:08:05 2024 +0200

Tweak ManagedScheduledExecutorServiceTest timing (which is often causing CI 
failures)
The bad feeling remains that I only fixed 1 of 30 ugly timings :/
---
 .../apache/openejb/threads/ManagedScheduledExecutorServiceTest.java | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git 
a/container/openejb-core/src/test/java/org/apache/openejb/threads/ManagedScheduledExecutorServiceTest.java
 
b/container/openejb-core/src/test/java/org/apache/openejb/threads/ManagedScheduledExecutorServiceTest.java
index 13d902f467..ac87560ea1 100644
--- 
a/container/openejb-core/src/test/java/org/apache/openejb/threads/ManagedScheduledExecutorServiceTest.java
+++ 
b/container/openejb-core/src/test/java/org/apache/openejb/threads/ManagedScheduledExecutorServiceTest.java
@@ -119,15 +119,15 @@ public class ManagedScheduledExecutorServiceTest {
 assertFalse(future.isCancelled());
 
 //Should easily get 5 invocations within 1 second
-counter.await(3, TimeUnit.SECONDS);
+counter.await(5, TimeUnit.SECONDS);
 
 future.cancel(true);
 assertEquals("Counter did not count down in time", 0L, 
counter.getCount());
 
 final boolean done = future.isDone();
-assertTrue(done);
+assertTrue("Future should be done", done);
 final boolean cancelled = future.isCancelled();
-assertTrue(cancelled);
+assertTrue("Future should be cancelled", cancelled);
 }
 
 @Test

[jira] [Work logged] (TOMEE-4166) Jakarta RESTFul Web Services TCK

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-4166?focusedWorklogId=915757=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-915757
 ]

ASF GitHub Bot logged work on TOMEE-4166:
-

Author: ASF GitHub Bot
Created on: 22/Apr/24 07:43
Start Date: 22/Apr/24 07:43
Worklog Time Spent: 10m 
  Work Description: rzo1 commented on PR #1063:
URL: https://github.com/apache/tomee/pull/1063#issuecomment-2068705126

   Just running a build with the updated TCK (the 3.1.5 isn't available yet on 
Maven, raised https://github.com/jakartaee/rest/issues/1260, but if the CI 
looks fine (with the failures expected), we are going to integrate it (and 
exclude the tests for now) -> stay tuned.




Issue Time Tracking
---

Worklog Id: (was: 915757)
Time Spent: 3h 10m  (was: 3h)

> Jakarta RESTFul Web Services TCK
> 
>
> Key: TOMEE-4166
> URL: https://issues.apache.org/jira/browse/TOMEE-4166
> Project: TomEE
>  Issue Type: Sub-task
>Reporter: David Blevins
>Priority: Major
>  Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> see https://jakarta.ee/specifications/restful-ws/3.1/ for additional details 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)