Jenkins build is back to normal : TomEE » master-deploy #800

[Apache Jenkins Server]

See 

Build failed in Jenkins: TomEE » master-build-quick #256

[Apache Jenkins Server]

See 


Changes:

[Cesar Hernandez] TOMEE-3814 improved server ssl documented configuration


--
[...truncated 811.17 KB...]
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
No mail will be sent out, as 'TomEE » master-build-quick » TomEE :: TomEE :: 
Mojarra #256' does not have a result yet. Please make sure you set a proper 
result in case of pipeline/build scripts.
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
No mail will be sent out, as 'TomEE » master-build-quick » TomEE :: Server :: 
REST #256' does not have a result yet. Please make sure you set a proper result 
in case of pipeline/build scripts.
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; cannot locate jdk_1.8_latest
ERROR: builds33 is offline; cannot locate maven_latest
ERROR: builds33 is offline; 

Build failed in Jenkins: TomEE » master-deploy #799

[Apache Jenkins Server]

See 


Changes:

[Cesar Hernandez] TOMEE-3814 improved server ssl documented configuration


--
[...truncated 615.07 KB...]
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
No mail will be sent out, as 'TomEE » master-deploy » TomEE :: BOMs :: TomEE 
Plus #799' does not have a result yet. Please make sure you set a proper result 
in case of pipeline/build scripts.
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
No mail will be sent out, as 'TomEE » master-deploy » TomEE :: Server :: 
ActiveMQ #799' does not have a result yet. Please make sure you set a proper 
result in case of pipeline/build scripts.
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
No mail will be sent out, as 'TomEE » master-deploy » TomEE :: Utils #799' 
does not have a result yet. Please make sure you set a proper result in case of 
pipeline/build scripts.
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
No mail will be sent out, as 'TomEE » master-deploy » TomEE :: Server :: 
BoneCP #799' does not have a result yet. Please make sure you set a proper 
result in case of pipeline/build scripts.
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
No mail will be sent out, as 'TomEE » master-deploy » TomEE :: Maven Plugins 
:: Util #799' does not have a result yet. Please make sure you set a proper 
result in case of pipeline/build scripts.
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
No mail will be sent out, as 'TomEE » master-deploy » TomEE :: Container :: 
JUnit 5 :: Backward Compatibility #799' does not have a result yet. Please make 
sure you set a proper result in case of pipeline/build scripts.
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
No mail will be sent out, as 'TomEE » master-deploy » TomEE :: BOMs :: TomEE 
WebProfile #799' does not have a result yet. Please make sure you set a proper 
result in case of pipeline/build scripts.
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
No mail will be sent out, as 'TomEE » master-deploy » TomEE :: Utils :: 
LiveReload #799' does not have a result yet. Please make sure you set a proper 
result in case of pipeline/build scripts.
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
No mail will be sent out, as 'TomEE » master-deploy » TomEE :: TomEE :: 
Webapp #799' does not have a result yet. Please make sure you set a proper 
result in case of pipeline/build scripts.
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
No mail will be sent out, as 'TomEE » master-deploy » TomEE :: iTests :: 
JAX-RS #799' does not have a result yet. Please make sure you set a proper 
result in case of pipeline/build scripts.
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
No mail will be sent out, as 'TomEE » master-deploy » TomEE :: Maven Plugins 
:: OpenEJB Embedded Maven Plugin #799' does not have a result yet. Please make 
sure you set a proper result in case of pipeline/build scripts.
ERROR: builds23 is offline; cannot locate jdk_1.8_latest
ERROR: builds23 is offline; cannot locate maven_3.6.3
No mail will be sent out, as 'TomEE » master-deploy » TomEE :: TCK :: 
MicroProfile Rest Client TCK #799' does not have a result yet. Please make sure 
you set a proper result in case of pipeline/build 

Jenkins build is back to normal : TomEE » master-deploy » TomEE :: Server :: CXF RS #799

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: iTests :: Server Composer #251

[Apache Jenkins Server]

See 

Build failed in Jenkins: TomEE » pull-request #251

[Apache Jenkins Server]

See 


Changes:

[Cesar Hernandez] TOMEE-3856 upgrade to jackson 2.13.2


--
[...truncated 18.08 MB...]
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
Sending e-mails to: commits@tomee.apache.org
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
No mail will be sent out, as 'TomEE » pull-request » TomEE :: TCK :: 
MicroProfile #251' does not have a result yet. Please make sure you set a 
proper result in case of pipeline/build scripts.
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
Sending e-mails to: commits@tomee.apache.org
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
No mail will be sent out, as 'TomEE » pull-request » TomEE :: Arquillian 
Adaptors Parent :: Sample :: Moviefun #251' does not have a result yet. Please 
make sure you set a proper result in case of pipeline/build scripts.
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
Sending e-mails to: commits@tomee.apache.org
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
Sending e-mails to: commits@tomee.apache.org
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
ERROR: builds42 is offline; cannot locate jdk_1.8_latest
ERROR: builds42 is offline; cannot locate maven_3.3.9
No mail will be sent out, as 'TomEE » pull-request » TomEE :: TCK :: 
MicroProfile Rest Client TCK #251' does not have a result yet. Please make sure 
you set a 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: TomEE :: TomEE Embedded #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » runner #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Maven Plugins :: TomEE Embedded Maven Plugin #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Examples :: Microprofile Fault Tolerance :: Timeout #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Examples :: Microprofile Metrics Histogram #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Server :: CXF RS #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » mp-metrics-gauge #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » MicroProfile :: Examples :: Config #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Examples :: Polling :: Web #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Maven Plugins :: TomEE Maven Plugin #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Connector Examples :: Connector in WAR #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Examples :: Microprofile Fault Tolerance :: Retry #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Examples :: JavaMail API #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Examples :: Custom HealthCheck #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Examples :: Microprofile Metrics Counted #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Connector Examples :: Connector in EAR :: Functional Tests #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Examples :: REST and EJB #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Examples :: Microprofile Fault Tolerance :: Fallback #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Examples :: REST CDI #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Examples :: Simple JMS Context #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Examples :: Microprofile Metrics Timed #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Examples :: REST, Mockito and Application Composer #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Examples :: Simple REST #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Web Examples :: REST Example #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Examples :: Simple JMS #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Examples :: REST XML JSON #251

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » pull-request » TomEE :: Examples :: Multiple Arquillian Adapters #251

[Apache Jenkins Server]

See 

[tomee] branch regenerate_boms_after_dep_upgrade created (now bdd317f)

[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 bdd317f  Minor: Regenerated BOMs for 
c447cdf84fecde27471febbb26476381a1c3cc03

No new revisions were added by this update.

[jira] [Work logged] (TOMEE-3814) Commented SSL Connector fix for tomee server.xml

[ASF GitHub Bot (Jira)]

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

ASF GitHub Bot logged work on TOMEE-3814:
-

Author: ASF GitHub Bot
Created on: 16/Mar/22 20:01
Start Date: 16/Mar/22 20:01
Worklog Time Spent: 10m 
  Work Description: cesarhernandezgt merged pull request #816:
URL: https://github.com/apache/tomee/pull/816


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@tomee.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
---

Worklog Id: (was: 742734)
Time Spent: 1h  (was: 50m)

> Commented SSL Connector fix for tomee server.xml 
> -
>
> Key: TOMEE-3814
> URL: https://issues.apache.org/jira/browse/TOMEE-3814
> Project: TomEE
>  Issue Type: Documentation
>Affects Versions: 8.0.8
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Attachments: Screen Shot 2022-02-16 at 13.27.14.png
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> Current server.xml contains the following commented out SSL connector:
>  
> {code:java}
> 
> {code}
>  
>  
> The configuration for 
> {code:java}
> xpoweredBy="false" server="Apache TomEE{code}
>  is misleading since for this to work needs to be set in the "Connector" tag:
>  
>  
> {code:java}
>  
> {code}
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Work logged] (TOMEE-3814) Commented SSL Connector fix for tomee server.xml

[ASF GitHub Bot (Jira)]

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

ASF GitHub Bot logged work on TOMEE-3814:
-

Author: ASF GitHub Bot
Created on: 16/Mar/22 20:01
Start Date: 16/Mar/22 20:01
Worklog Time Spent: 10m 
  Work Description: cesarhernandezgt commented on pull request #816:
URL: https://github.com/apache/tomee/pull/816#issuecomment-1069561853


   Thanks for the review @rzo1. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@tomee.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
---

Worklog Id: (was: 742732)
Time Spent: 50m  (was: 40m)

> Commented SSL Connector fix for tomee server.xml 
> -
>
> Key: TOMEE-3814
> URL: https://issues.apache.org/jira/browse/TOMEE-3814
> Project: TomEE
>  Issue Type: Documentation
>Affects Versions: 8.0.8
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Attachments: Screen Shot 2022-02-16 at 13.27.14.png
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> Current server.xml contains the following commented out SSL connector:
>  
> {code:java}
> 
> {code}
>  
>  
> The configuration for 
> {code:java}
> xpoweredBy="false" server="Apache TomEE{code}
>  is misleading since for this to work needs to be set in the "Connector" tag:
>  
>  
> {code:java}
>  
> {code}
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[tomee] branch master updated: TOMEE-3814 improved server ssl documented configuration

[cesarhernandezgt]

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

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


The following commit(s) were added to refs/heads/master by this push:
 new cf7d6cf  TOMEE-3814 improved server ssl documented configuration
 new c447cdf  Merge pull request #816 from cesarhernandezgt/TOMEE-3814-2
cf7d6cf is described below

commit cf7d6cf1be55c2ce59c3e606206a893d83334331
Author: Cesar Hernandez 
AuthorDate: Wed Feb 16 13:27:56 2022 -0600

TOMEE-3814 improved server ssl documented configuration
---
 .../src/main/java/org/apache/tomee/installer/Installer.java   | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git 
a/tomee/tomee-common/src/main/java/org/apache/tomee/installer/Installer.java 
b/tomee/tomee-common/src/main/java/org/apache/tomee/installer/Installer.java
index a5e2a60..0b3fa02 100644
--- a/tomee/tomee-common/src/main/java/org/apache/tomee/installer/Installer.java
+++ b/tomee/tomee-common/src/main/java/org/apache/tomee/installer/Installer.java
@@ -560,8 +560,8 @@ public class Installer implements InstallerInterface {
 newServerXml = Installers.replace(newServerXml,
 "",
-"xpoweredBy=\"false\" server=\"Apache TomEE\" />");
+">",
+" xpoweredBy=\"false\" server=\"Apache TomEE\" >");
 } catch (final IOException e) {
 alerts.addError("Error adding server attribute to server.xml 
file", e);
 }

Jenkins build became unstable: TomEE » master-build-full #514

[Apache Jenkins Server]

See 

Jenkins build became unstable: TomEE » master-build-full » TomEE :: TCK :: MicroProfile Metrics TCK #514

[Apache Jenkins Server]

See 

Jenkins build is unstable: TomEE » master-build-quick-9.x #58

[Apache Jenkins Server]

See 

Jenkins build is still unstable: TomEE » master-build-quick-9.x » TomEE :: Server :: EJBd #58

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » master-build-quick-9.x » TomEE :: TomEE :: TomEE Embedded #58

[Apache Jenkins Server]

See 

Jenkins build is back to stable : TomEE » master-build-quick-9.x » TomEE :: TomEE :: Apache TomEE #58

[Apache Jenkins Server]

See 

[jira] [Created] (TOMEE-3856) Uprade to jackson 2.13.2

[Cesar Hernandez (Jira)]

Cesar Hernandez created TOMEE-3856:
--

 Summary: Uprade to jackson 2.13.2
 Key: TOMEE-3856
 URL: https://issues.apache.org/jira/browse/TOMEE-3856
 Project: TomEE
  Issue Type: Dependency upgrade
Affects Versions: 8.0.10
Reporter: Cesar Hernandez
Assignee: Cesar Hernandez
 Fix For: 8.0.11






--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Build failed in Jenkins: TomEE » pull-request #250

[Apache Jenkins Server]

See 


Changes:


--
[...truncated 43.36 KB...]
CONFLICT (content): Merge conflict in examples/resources-jmx-example/pom.xml
Auto-merging examples/resources-declared-in-webapp/pom.xml
CONFLICT (content): Merge conflict in 
examples/resources-declared-in-webapp/pom.xml
Auto-merging examples/reload-persistence-unit-properties/pom.xml
CONFLICT (content): Merge conflict in 
examples/reload-persistence-unit-properties/pom.xml
Auto-merging examples/realm-in-tomee/pom.xml
CONFLICT (content): Merge conflict in examples/realm-in-tomee/pom.xml
Auto-merging examples/projectstage-demo/pom.xml
CONFLICT (content): Merge conflict in examples/projectstage-demo/pom.xml
Auto-merging examples/polling-parent/polling-client/pom.xml
CONFLICT (content): Merge conflict in 
examples/polling-parent/polling-client/pom.xml
Auto-merging examples/pojo-webservice/pom.xml
CONFLICT (content): Merge conflict in examples/pojo-webservice/pom.xml
Auto-merging examples/persistence-fragment/pom.xml
CONFLICT (content): Merge conflict in examples/persistence-fragment/pom.xml
Auto-merging examples/myfaces-codi-demo/pom.xml
CONFLICT (content): Merge conflict in examples/myfaces-codi-demo/pom.xml
Auto-merging examples/mvc-resteasy/pom.xml
CONFLICT (content): Merge conflict in examples/mvc-resteasy/pom.xml
Auto-merging examples/mvc-cxf/pom.xml
CONFLICT (content): Merge conflict in examples/mvc-cxf/pom.xml
Auto-merging examples/mvc-cxf-hibernate/pom.xml
CONFLICT (content): Merge conflict in examples/mvc-cxf-hibernate/pom.xml
Auto-merging examples/multiple-tomee-arquillian/pom.xml
CONFLICT (content): Merge conflict in examples/multiple-tomee-arquillian/pom.xml
Auto-merging examples/multiple-arquillian-adapters/pom.xml
CONFLICT (content): Merge conflict in 
examples/multiple-arquillian-adapters/pom.xml
Auto-merging examples/multi-jpa-provider-testing/pom.xml
CONFLICT (content): Merge conflict in 
examples/multi-jpa-provider-testing/pom.xml
Auto-merging examples/movies-complete/pom.xml
CONFLICT (content): Merge conflict in examples/movies-complete/pom.xml
Removing examples/movies-complete/build.xml
Auto-merging examples/movies-complete-meta/pom.xml
CONFLICT (content): Merge conflict in examples/movies-complete-meta/pom.xml
Removing examples/movies-complete-meta/build.xml
Auto-merging examples/moviefun/pom.xml
CONFLICT (content): Merge conflict in examples/moviefun/pom.xml
Auto-merging examples/moviefun-rest/pom.xml
CONFLICT (content): Merge conflict in examples/moviefun-rest/pom.xml
Auto-merging examples/mbean-auto-registration/pom.xml
CONFLICT (content): Merge conflict in examples/mbean-auto-registration/pom.xml
Auto-merging examples/lookup-of-ejbs/pom.xml
CONFLICT (content): Merge conflict in examples/lookup-of-ejbs/pom.xml
Removing examples/lookup-of-ejbs/build.xml
Auto-merging examples/lookup-of-ejbs-with-descriptor/pom.xml
CONFLICT (content): Merge conflict in 
examples/lookup-of-ejbs-with-descriptor/pom.xml
Removing examples/lookup-of-ejbs-with-descriptor/build.xml
Auto-merging examples/junit5-arquillian-simple-websockets/pom.xml
CONFLICT (content): Merge conflict in 
examples/junit5-arquillian-simple-websockets/pom.xml
Auto-merging examples/junit5-arquillian-multiple-tomee/pom.xml
CONFLICT (content): Merge conflict in 
examples/junit5-arquillian-multiple-tomee/pom.xml
Auto-merging examples/junit5-application-composer/pom.xml
CONFLICT (content): Merge conflict in 
examples/junit5-application-composer/pom.xml
Auto-merging examples/jsf-managedBean-and-ejb/pom.xml
CONFLICT (content): Merge conflict in examples/jsf-managedBean-and-ejb/pom.xml
Auto-merging examples/jsf-cdi-and-ejb/pom.xml
CONFLICT (content): Merge conflict in examples/jsf-cdi-and-ejb/pom.xml
Auto-merging examples/jpa-hibernate/pom.xml
CONFLICT (content): Merge conflict in examples/jpa-hibernate/pom.xml
Auto-merging examples/jpa-hibernate-arquillian/pom.xml
CONFLICT (content): Merge conflict in examples/jpa-hibernate-arquillian/pom.xml
Auto-merging examples/jpa-enumerated/pom.xml
CONFLICT (content): Merge conflict in examples/jpa-enumerated/pom.xml
Removing examples/jpa-enumerated/build.xml
Auto-merging examples/jpa-eclipselink/pom.xml
CONFLICT (content): Merge conflict in examples/jpa-eclipselink/pom.xml
Auto-merging examples/jaxrs-filter/pom.xml
CONFLICT (content): Merge conflict in examples/jaxrs-filter/pom.xml
Auto-merging examples/javamail/pom.xml
CONFLICT (content): Merge conflict in examples/javamail/pom.xml
Auto-merging examples/java-modules/pom.xml
CONFLICT (content): Merge conflict in examples/java-modules/pom.xml
Auto-merging examples/interceptors/pom.xml
CONFLICT (content): Merge conflict in examples/interceptors/pom.xml
Removing examples/interceptors/build.xml
Auto-merging examples/injection-of-env-entry/pom.xml
CONFLICT (content): Merge conflict in examples/injection-of-env-entry/pom.xml
Removing examples/injection-of-env-entry/build.xml
Auto-merging 

[tomee] branch tomee-9.x-initial updated (ca58694 -> 8bcf60d)

[jlmonteiro]

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

jlmonteiro pushed a change to branch tomee-9.x-initial
in repository https://gitbox.apache.org/repos/asf/tomee.git.


from ca58694  Missing dep for addressing
 add eded968  Relocate taglib to jakarta
 add 8bcf60d  Remove all management API

No new revisions were added by this update.

Summary of changes:
 boms/tomee-webprofile/pom.xml  |  11 +++
 container/openejb-core/pom.xml |   1 -
 .../org/apache/openejb/config/SystemAppInfo.java   |  12 ---
 .../java/org/apache/openejb/config/SystemApps.java |   2 -
 .../java/org/apache/openejb/mgmt/MEJBBean.java | 102 -
 deps/taglibs-shade/pom.xml |   8 ++
 server/openejb-server/pom.xml  |   1 -
 tomee/tomee-embedded/pom.xml   |   4 -
 8 files changed, 19 insertions(+), 122 deletions(-)
 delete mode 100644 
container/openejb-core/src/main/java/org/apache/openejb/mgmt/MEJBBean.java

[jira] [Updated] (TOMEE-3849) EclipseLink JPA provider not discoverable in TomEE Plume libraries

[Eric Hamilton (Jira)]

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

Eric Hamilton updated TOMEE-3849:
-
Description: 
A Java web application is unable to use the default EclipseLink JPA provider 
that is included in the TomEE Plume distributable.  JPA is only able to 
discover the OpenJPA provider within the TomEE server libraries.  Attached 
TestWeb application to reproduce the issue.  This configuration was working in 
TomEE Plume 8.0.6, and behavior was changed in 8.0.7.

 

Web application persistence.xml configured with EclipseLink JPA:
{code:java}
  
    org.eclipse.persistence.jpa.PersistenceProvider
{code}
 

JPA fails to load with error:
{code:java}
javax.persistence.PersistenceException: No persistence providers available for 
"TestJPA" after trying the following discovered implementations: 
org.apache.openjpa.persistence.PersistenceProviderImpl{code}
 

Workaround is to copy the the EclipseLink library into the web application 
libraries.  Then JPA will discover both the OpenJPA and EclipseLink providers 
from the Java web application.

  was:
A Java web application is unable to use the default EclipseLink JPA provider 
that is included in the TomEE Plume distributable.  It appears that JPA is only 
able to discover the OpenJPA provider within the TomEE server libraries.  
Attached TestWeb application to reproduce the issue.  This configuration was 
working in TomEE Plume 8.0.6, and behavior was changed in 8.0.7.

 

Web application persistence.xml configured with EclipseLink JPA:
{code:java}
  
    org.eclipse.persistence.jpa.PersistenceProvider
{code}
 

JPA fails to load with error:
{code:java}
javax.persistence.PersistenceException: No persistence providers available for 
"TestJPA" after trying the following discovered implementations: 
org.apache.openjpa.persistence.PersistenceProviderImpl{code}
 

Workaround is to copy the the EclipseLink library into the web application 
libraries.  Then JPA will discover both the OpenJPA and EclipseLink providers 
from the Java web application.


> EclipseLink JPA provider not discoverable in TomEE Plume libraries
> --
>
> Key: TOMEE-3849
> URL: https://issues.apache.org/jira/browse/TOMEE-3849
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 8.0.7, 8.0.8, 8.0.9, 8.0.10
>Reporter: Eric Hamilton
>Priority: Major
>  Labels: JPA, eclipselink, openjpa
> Attachments: TestWeb.zip
>
>
> A Java web application is unable to use the default EclipseLink JPA provider 
> that is included in the TomEE Plume distributable.  JPA is only able to 
> discover the OpenJPA provider within the TomEE server libraries.  Attached 
> TestWeb application to reproduce the issue.  This configuration was working 
> in TomEE Plume 8.0.6, and behavior was changed in 8.0.7.
>  
> Web application persistence.xml configured with EclipseLink JPA:
> {code:java}
>   
>     org.eclipse.persistence.jpa.PersistenceProvider
> {code}
>  
> JPA fails to load with error:
> {code:java}
> javax.persistence.PersistenceException: No persistence providers available 
> for "TestJPA" after trying the following discovered implementations: 
> org.apache.openjpa.persistence.PersistenceProviderImpl{code}
>  
> Workaround is to copy the the EclipseLink library into the web application 
> libraries.  Then JPA will discover both the OpenJPA and EclipseLink providers 
> from the Java web application.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (TOMEE-3849) EclipseLink JPA provider not discoverable in TomEE Plume libraries

[Eric Hamilton (Jira)]

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

Eric Hamilton updated TOMEE-3849:
-
Description: 
A Java web application is unable to use the default EclipseLink JPA provider 
that is included in the TomEE Plume distributable.  It appears that JPA is only 
able to discover the OpenJPA provider within the TomEE server libraries.  
Attached TestWeb application to reproduce the issue.  This configuration was 
working in TomEE Plume 8.0.6, and behavior was changed in 8.0.7.

 

Web application persistence.xml configured with EclipseLink JPA:
{code:java}
  
    org.eclipse.persistence.jpa.PersistenceProvider
{code}
 

JPA fails to load with error:
{code:java}
javax.persistence.PersistenceException: No persistence providers available for 
"TestJPA" after trying the following discovered implementations: 
org.apache.openjpa.persistence.PersistenceProviderImpl{code}
 

Workaround is to copy the the EclipseLink library into the web application 
libraries.  Then JPA will discover both the OpenJPA and EclipseLink providers 
from the Java web application.

  was:
Unable to configure persistence.xml with EclipseLink JPA:
{code:java}
  
    org.eclipse.persistence.jpa.PersistenceProvider
{code}
 

JPA fails to load with error:
{code:java}
javax.persistence.PersistenceException: No persistence providers available for 
"TestJPA" after trying the following discovered implementations: 
org.apache.openjpa.persistence.PersistenceProviderImpl{code}
 

Attached TestWeb application to reproduce issue.  This configuration was 
working in TomEE Plume 8.0.6, and first noticed failures in TomEE Plume 8.0.8.

 

Note:  Removal of the  tag configuration in persistence.xml will not 
produce an error, although it appears to default to OpenJPA as recorded in the 
logs:
{code:java}
null.openjpa.Runtime OpenJPA dynamically loaded a validation provider.{code}
 


> EclipseLink JPA provider not discoverable in TomEE Plume libraries
> --
>
> Key: TOMEE-3849
> URL: https://issues.apache.org/jira/browse/TOMEE-3849
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 8.0.7, 8.0.8, 8.0.9, 8.0.10
>Reporter: Eric Hamilton
>Priority: Major
>  Labels: JPA, eclipselink, openjpa
> Attachments: TestWeb.zip
>
>
> A Java web application is unable to use the default EclipseLink JPA provider 
> that is included in the TomEE Plume distributable.  It appears that JPA is 
> only able to discover the OpenJPA provider within the TomEE server libraries. 
>  Attached TestWeb application to reproduce the issue.  This configuration was 
> working in TomEE Plume 8.0.6, and behavior was changed in 8.0.7.
>  
> Web application persistence.xml configured with EclipseLink JPA:
> {code:java}
>   
>     org.eclipse.persistence.jpa.PersistenceProvider
> {code}
>  
> JPA fails to load with error:
> {code:java}
> javax.persistence.PersistenceException: No persistence providers available 
> for "TestJPA" after trying the following discovered implementations: 
> org.apache.openjpa.persistence.PersistenceProviderImpl{code}
>  
> Workaround is to copy the the EclipseLink library into the web application 
> libraries.  Then JPA will discover both the OpenJPA and EclipseLink providers 
> from the Java web application.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (TOMEE-3849) EclipseLink JPA provider not discoverable in TomEE Plume libraries

[Eric Hamilton (Jira)]

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

Eric Hamilton updated TOMEE-3849:
-
Summary: EclipseLink JPA provider not discoverable in TomEE Plume libraries 
 (was: Unable to configure JPA with EclipseLink in TomEE Plume)

> EclipseLink JPA provider not discoverable in TomEE Plume libraries
> --
>
> Key: TOMEE-3849
> URL: https://issues.apache.org/jira/browse/TOMEE-3849
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 8.0.7, 8.0.8, 8.0.9, 8.0.10
>Reporter: Eric Hamilton
>Priority: Major
>  Labels: JPA, eclipselink, openjpa
> Attachments: TestWeb.zip
>
>
> Unable to configure persistence.xml with EclipseLink JPA:
> {code:java}
>   
>     org.eclipse.persistence.jpa.PersistenceProvider
> {code}
>  
> JPA fails to load with error:
> {code:java}
> javax.persistence.PersistenceException: No persistence providers available 
> for "TestJPA" after trying the following discovered implementations: 
> org.apache.openjpa.persistence.PersistenceProviderImpl{code}
>  
> Attached TestWeb application to reproduce issue.  This configuration was 
> working in TomEE Plume 8.0.6, and first noticed failures in TomEE Plume 8.0.8.
>  
> Note:  Removal of the  tag configuration in persistence.xml will 
> not produce an error, although it appears to default to OpenJPA as recorded 
> in the logs:
> {code:java}
> null.openjpa.Runtime OpenJPA dynamically loaded a validation provider.{code}
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (TOMEE-3849) Unable to configure JPA with EclipseLink in TomEE Plume

[Eric Hamilton (Jira)]

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

Eric Hamilton updated TOMEE-3849:
-
Affects Version/s: 8.0.7

> Unable to configure JPA with EclipseLink in TomEE Plume
> ---
>
> Key: TOMEE-3849
> URL: https://issues.apache.org/jira/browse/TOMEE-3849
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 8.0.7, 8.0.8, 8.0.9, 8.0.10
>Reporter: Eric Hamilton
>Priority: Major
>  Labels: JPA, eclipselink, openjpa
> Attachments: TestWeb.zip
>
>
> Unable to configure persistence.xml with EclipseLink JPA:
> {code:java}
>   
>     org.eclipse.persistence.jpa.PersistenceProvider
> {code}
>  
> JPA fails to load with error:
> {code:java}
> javax.persistence.PersistenceException: No persistence providers available 
> for "TestJPA" after trying the following discovered implementations: 
> org.apache.openjpa.persistence.PersistenceProviderImpl{code}
>  
> Attached TestWeb application to reproduce issue.  This configuration was 
> working in TomEE Plume 8.0.6, and first noticed failures in TomEE Plume 8.0.8.
>  
> Note:  Removal of the  tag configuration in persistence.xml will 
> not produce an error, although it appears to default to OpenJPA as recorded 
> in the logs:
> {code:java}
> null.openjpa.Runtime OpenJPA dynamically loaded a validation provider.{code}
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Work logged] (TOMEE-3846) Inconsistence between tomee flavors comparison in website and actual jars

[ASF GitHub Bot (Jira)]

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

ASF GitHub Bot logged work on TOMEE-3846:
-

Author: ASF GitHub Bot
Created on: 16/Mar/22 11:15
Start Date: 16/Mar/22 11:15
Worklog Time Spent: 10m 
  Work Description: rzo1 commented on pull request #35:
URL: 
https://github.com/apache/tomee-site-generator/pull/35#issuecomment-1069012431


   > dropped a mail to [d...@tomee.apache.org](mailto:d...@tomee.apache.org)
   
   Thanks, @sultan 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@tomee.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
---

Worklog Id: (was: 742188)
Time Spent: 40m  (was: 0.5h)

> Inconsistence between tomee flavors comparison in website and actual jars
> -
>
> Key: TOMEE-3846
> URL: https://issues.apache.org/jira/browse/TOMEE-3846
> Project: TomEE
>  Issue Type: Documentation
>  Components: Website
>Reporter: Gwénaël Ruelland
>Priority: Major
>  Labels: pull-request-available
> Attachments: image-2022-03-02-08-56-58-642.png, 
> image-2022-03-02-08-57-19-856.png, image-2022-03-02-08-58-10-952.png, 
> image-2022-03-02-09-05-07-006.png, image-2022-03-02-09-05-49-069.png, 
> image-2022-03-02-09-06-20-365.png, image-2022-03-02-09-10-30-996.png, 
> image-2022-03-02-09-11-27-520.png, image-2022-03-02-11-59-07-000.png, 
> image-2022-03-02-11-59-41-196.png, image-2022-03-02-12-19-25-319.png, 
> image-2022-03-02-12-29-28-417.png, image-2022-03-02-12-54-57-355.png, 
> image-2022-03-02-13-12-34-765.png, image-2022-03-03-16-02-35-432.png, 
> image-2022-03-03-16-02-39-953.png, image-2022-03-03-16-03-35-130.png, 
> image-2022-03-03-22-26-57-626.png, image-2022-03-11-10-45-51-121.png
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Website lets us believe that Plus flavor includes Plume flavor. which was the 
> opposite for previous versions, and, Plume does includes eclipselink and 
> mojarra, when Plus does not (and never did). now Plus includes batchee which 
> Plume does not.
> These piece of information could be better transmitted to the website 
> visitors.
> I had trouble figuring out why my java webapp was starting on Plume but not 
> Plus. (because eclipselink is not in Plus)
> Questions : Is it intended to have Plus not containing Eclipselink while 
> Plume not containing batchee ?
> if yes : update website
> if not : update poms 
> 1) Current web site content (partial)
> !image-2022-03-02-08-56-58-642.png|width=815,height=95!
>      [...]
> !image-2022-03-02-08-57-19-856.png|width=818,height=68!
> 2) Actual jars diff between flavors
> !image-2022-03-03-22-26-57-626.png|width=817,height=208!
> 3) Suggested website with 2 tables
> part (a) synthetic table (listening to your comments)
> part (b) detailed table (partially displayed here but complete on git)
> !image-2022-03-03-16-03-35-130.png|width=814,height=559!
> 4) older comparison chart (partial)
> !image-2022-03-02-09-05-49-069.png|width=829,height=43!
> !image-2022-03-02-09-06-20-365.png|width=817,height=172!
> complete capture of old version
> !image-2022-03-02-09-05-07-006.png|width=816,height=597!
> complete capture of suggested version
> !image-2022-03-11-10-45-51-121.png|width=815,height=1512!



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Work logged] (TOMEE-3846) Inconsistence between tomee flavors comparison in website and actual jars

[ASF GitHub Bot (Jira)]

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

ASF GitHub Bot logged work on TOMEE-3846:
-

Author: ASF GitHub Bot
Created on: 16/Mar/22 10:32
Start Date: 16/Mar/22 10:32
Worklog Time Spent: 10m 
  Work Description: sultan commented on pull request #35:
URL: 
https://github.com/apache/tomee-site-generator/pull/35#issuecomment-1068971136


   dropped a mail to d...@tomee.apache.org 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@tomee.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
---

Worklog Id: (was: 742167)
Time Spent: 0.5h  (was: 20m)

> Inconsistence between tomee flavors comparison in website and actual jars
> -
>
> Key: TOMEE-3846
> URL: https://issues.apache.org/jira/browse/TOMEE-3846
> Project: TomEE
>  Issue Type: Documentation
>  Components: Website
>Reporter: Gwénaël Ruelland
>Priority: Major
>  Labels: pull-request-available
> Attachments: image-2022-03-02-08-56-58-642.png, 
> image-2022-03-02-08-57-19-856.png, image-2022-03-02-08-58-10-952.png, 
> image-2022-03-02-09-05-07-006.png, image-2022-03-02-09-05-49-069.png, 
> image-2022-03-02-09-06-20-365.png, image-2022-03-02-09-10-30-996.png, 
> image-2022-03-02-09-11-27-520.png, image-2022-03-02-11-59-07-000.png, 
> image-2022-03-02-11-59-41-196.png, image-2022-03-02-12-19-25-319.png, 
> image-2022-03-02-12-29-28-417.png, image-2022-03-02-12-54-57-355.png, 
> image-2022-03-02-13-12-34-765.png, image-2022-03-03-16-02-35-432.png, 
> image-2022-03-03-16-02-39-953.png, image-2022-03-03-16-03-35-130.png, 
> image-2022-03-03-22-26-57-626.png, image-2022-03-11-10-45-51-121.png
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Website lets us believe that Plus flavor includes Plume flavor. which was the 
> opposite for previous versions, and, Plume does includes eclipselink and 
> mojarra, when Plus does not (and never did). now Plus includes batchee which 
> Plume does not.
> These piece of information could be better transmitted to the website 
> visitors.
> I had trouble figuring out why my java webapp was starting on Plume but not 
> Plus. (because eclipselink is not in Plus)
> Questions : Is it intended to have Plus not containing Eclipselink while 
> Plume not containing batchee ?
> if yes : update website
> if not : update poms 
> 1) Current web site content (partial)
> !image-2022-03-02-08-56-58-642.png|width=815,height=95!
>      [...]
> !image-2022-03-02-08-57-19-856.png|width=818,height=68!
> 2) Actual jars diff between flavors
> !image-2022-03-03-22-26-57-626.png|width=817,height=208!
> 3) Suggested website with 2 tables
> part (a) synthetic table (listening to your comments)
> part (b) detailed table (partially displayed here but complete on git)
> !image-2022-03-03-16-03-35-130.png|width=814,height=559!
> 4) older comparison chart (partial)
> !image-2022-03-02-09-05-49-069.png|width=829,height=43!
> !image-2022-03-02-09-06-20-365.png|width=817,height=172!
> complete capture of old version
> !image-2022-03-02-09-05-07-006.png|width=816,height=597!
> complete capture of suggested version
> !image-2022-03-11-10-45-51-121.png|width=815,height=1512!



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Build failed in Jenkins: TomEE » master-deploy #798

[Apache Jenkins Server]

See 


Changes:

[Richard Zowalla] TOMEE-3855: Upgrade Tomcat to 9.0.60


--
[...truncated 913.72 KB...]
[JENKINS] Archiving 

 to 
org.apache.tomee/taglibs-shade/8.0.11-20220316.091316-50/taglibs-shade-8.0.11-20220316.091316-50-sources.jar
[JENKINS] Archiving 

 to 
org.apache.tomee/tomee-security/8.0.11-SNAPSHOT/tomee-security-8.0.11-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.tomee/arquillian-common/8.0.11-SNAPSHOT/arquillian-common-8.0.11-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.tomee/arquillian-common/8.0.11-20220316.093034-50/arquillian-common-8.0.11-20220316.093034-50.jar
[JENKINS] Archiving 

 to 
org.apache.openejb.itests/legacy-server/8.0.11-SNAPSHOT/legacy-server-8.0.11-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.tomee/arquillian-tomee-common/8.0.11-SNAPSHOT/arquillian-tomee-common-8.0.11-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.tomee/arquillian-tomee-common/8.0.11-20220316.093048-50/arquillian-tomee-common-8.0.11-20220316.093048-50.jar
[JENKINS] Archiving 

 to 
org.apache.tomee/microprofile-opentracing-tck/8.0.11-SNAPSHOT/microprofile-opentracing-tck-8.0.11-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.tomee/arquillian-tomee-tests/8.0.11-SNAPSHOT/arquillian-tomee-tests-8.0.11-SNAPSHOT.pom
[JENKINS] Archiving 

 to org.apache.tomee/tomee-util/8.0.11-SNAPSHOT/tomee-util-8.0.11-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.tomee/tomee-util/8.0.11-20220316.092741-50/tomee-util-8.0.11-20220316.092741-50.jar
[JENKINS] Archiving 

 to 
org.apache.tomee/openejb-derbynet/8.0.11-SNAPSHOT/openejb-derbynet-8.0.11-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.tomee/openejb-derbynet/8.0.11-20220316.093424-50/openejb-derbynet-8.0.11-20220316.093424-50.jar
[JENKINS] Archiving 

 to org.apache.tomee/tomee-jdbc/8.0.11-SNAPSHOT/tomee-jdbc-8.0.11-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.tomee/tomee-jdbc/8.0.11-20220316.092140-50/tomee-jdbc-8.0.11-20220316.092140-50.jar
[JENKINS] Archiving 

 to 
org.apache.tomee.bom/tomee-plume/8.0.11-SNAPSHOT/tomee-plume-8.0.11-SNAPSHOT.pom
[Fast Archiver] Compressed 62.30 KB of artifacts by 51.4% relative to #797
[JENKINS] Archiving 

 to 
org.apache.tomee.maven/tomee-embedded-maven-plugin/8.0.11-SNAPSHOT/tomee-embedded-maven-plugin-8.0.11-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.tomee/microprofile-jwt-tck/8.0.11-SNAPSHOT/microprofile-jwt-tck-8.0.11-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.tomee/arquillian-tomee-jaxrs-tests/8.0.11-SNAPSHOT/arquillian-tomee-jaxrs-tests-8.0.11-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.tomee/openejb-itests-client/8.0.11-SNAPSHOT/openejb-itests-client-8.0.11-SNAPSHOT.pom
[JENKINS] Archiving 

Build failed in Jenkins: TomEE » master-deploy » TomEE :: Server :: CXF RS #798

[Apache Jenkins Server]

See 


Changes:


--
[INFO] 
[INFO] --< org.apache.tomee:openejb-cxf-rs >---
[INFO] Building TomEE :: Server :: CXF RS 8.0.11-SNAPSHOT  [39/142]
[INFO] [ jar ]-
[INFO] 
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ openejb-cxf-rs ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
openejb-cxf-rs ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (process-resource-bundles) 
@ openejb-cxf-rs ---
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ 
openejb-cxf-rs ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.6.2:compile (default-compile) @ 
openejb-cxf-rs ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 24 source files to 

[INFO] 
:
 

 uses or overrides a deprecated API.
[INFO] 
:
 Recompile with -Xlint:deprecation for details.
[INFO] 
:
 Some input files use unchecked or unsafe operations.
[INFO] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- dependency-report-plugin:1.0.2:report (default) @ openejb-cxf-rs ---
[INFO] 
[INFO] --- maven-bundle-plugin:3.3.0:manifest (bundle-manifest) @ 
openejb-cxf-rs ---
[WARNING] Manifest org.apache.tomee:openejb-cxf-rs:jar:8.0.11-SNAPSHOT : Unused 
Export-Package instructions: [org.apache.tomee*] 
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:testResources (default-testResources) @ 
openejb-cxf-rs ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 7 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.6.2:testCompile (default-testCompile) @ 
openejb-cxf-rs ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 82 source files to 

[INFO] 
:
 

 uses or overrides a deprecated API.
[INFO] 
:
 Recompile with -Xlint:deprecation for details.
[INFO] 
:
 Some input files use unchecked or unsafe operations.
[INFO] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @ openejb-cxf-rs 
---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:3.0.2:jar (default-jar) @ openejb-cxf-rs ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:3.7.1:attach-descriptor (attach-descriptor) @ 
openejb-cxf-rs ---
[INFO] Skipping because packaging 'jar' is not pom.
[INFO] 
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ 
openejb-cxf-rs ---
[INFO] Installing 

 to 

[tomee] branch master updated: TOMEE-3855: Upgrade Tomcat to 9.0.60

[rzo1]

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

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


The following commit(s) were added to refs/heads/master by this push:
 new c873022  TOMEE-3855: Upgrade Tomcat to 9.0.60
c873022 is described below

commit c873022e15b78073bfe6ea0458e824467cc9b872
Author: Richard Zowalla 
AuthorDate: Wed Mar 16 09:22:34 2022 +0100

TOMEE-3855: Upgrade Tomcat to 9.0.60
---
 pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pom.xml b/pom.xml
index 5531f67..c47a4b7 100644
--- a/pom.xml
+++ b/pom.xml
@@ -145,7 +145,7 @@
 2.0.0
 1.2.6
 
-9.0.59
+9.0.60
 
 3.4.5
 2.10.3

[jira] [Resolved] (TOMEE-3855) Upgrade Tomcat to 9.0.60

[Richard Zowalla (Jira)]

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

Richard Zowalla resolved TOMEE-3855.

Fix Version/s: 8.0.11
   Resolution: Fixed

> Upgrade Tomcat to 9.0.60
> 
>
> Key: TOMEE-3855
> URL: https://issues.apache.org/jira/browse/TOMEE-3855
> Project: TomEE
>  Issue Type: Dependency upgrade
>  Components: TomEE Core Server
>Affects Versions: 8.0.10
>Reporter: Richard Zowalla
>Assignee: Richard Zowalla
>Priority: Major
> Fix For: 8.0.11
>
>
> https://tomcat.apache.org/tomcat-9.0-doc/changelog.html



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (TOMEE-3855) Upgrade Tomcat to 9.0.60

[Richard Zowalla (Jira)]

Richard Zowalla created TOMEE-3855:
--

 Summary: Upgrade Tomcat to 9.0.60
 Key: TOMEE-3855
 URL: https://issues.apache.org/jira/browse/TOMEE-3855
 Project: TomEE
  Issue Type: Dependency upgrade
  Components: TomEE Core Server
Affects Versions: 8.0.10
Reporter: Richard Zowalla
Assignee: Richard Zowalla


https://tomcat.apache.org/tomcat-9.0-doc/changelog.html



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Jenkins build is still unstable: TomEE » master-build-quick-9.x » TomEE :: Server :: EJBd #57

[Apache Jenkins Server]

See 

Jenkins build is unstable: TomEE » master-build-quick-9.x » TomEE :: TomEE :: TomEE Embedded #57

[Apache Jenkins Server]

See 

Jenkins build is back to normal : TomEE » master-build-quick-9.x » TomEE :: Server :: CXF #57

[Apache Jenkins Server]

See 

[tomee-site-generator] branch master updated: TOMEE-3854: Includes some more links from the mailing list thread

[rzo1]

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

rzo1 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomee-site-generator.git


The following commit(s) were added to refs/heads/master by this push:
 new 5006c54  TOMEE-3854: Includes some more links from the mailing list 
thread
5006c54 is described below

commit 5006c54f02804bede84f85f20849e2562b986f2e
Author: Richard Zowalla 
AuthorDate: Wed Mar 16 07:36:03 2022 +0100

TOMEE-3854: Includes some more links from the mailing list thread
---
 .../content/community/contributor-resources.adoc   | 41 --
 1 file changed, 30 insertions(+), 11 deletions(-)

diff --git a/src/main/jbake/content/community/contributor-resources.adoc 
b/src/main/jbake/content/community/contributor-resources.adoc
index 7ff09a8..df0f220 100644
--- a/src/main/jbake/content/community/contributor-resources.adoc
+++ b/src/main/jbake/content/community/contributor-resources.adoc
@@ -12,35 +12,54 @@ This page serves as a link collector to different resources 
available to contrib
 == Repositories
 
 An overview over all TomEE repositories hosted at the ASF infrastructure can 
be found link:https://gitbox.apache.org/repos/asf#tomee[here].
-Most of them are mirrored to 
link:https://github.com/search?q=org%3Aapache+tomee[GitHub]. Some legacy code 
is served from link:http://svn.apache.org/viewvc/tomee/[SVN].
+Most of them are mirrored to 
link:https://github.com/search?q=org%3Aapache+tomee[GitHub].
 
-=== Quick Links
- TomEE 8
+Some legacy code is served from link:http://svn.apache.org/viewvc/tomee/[SVN].
+
+== Quick Links
+=== TomEE 8
 - link:https://github.com/apache/tomee[Main Repository]
 
- TomEE 9
+=== TomEE 9
 - link:https://github.com/apache/tomee-jakarta[TomEE 9.x ] - will be soon 
available in the link:https://github.com/apache/tomee[Main Repository].
 
- Misc
+=== Misc
+
+- link:https://svn.apache.org/repos/asf/tomee/javaee-api/[JavaEE API Uber JAR]
 - link:https://github.com/apache/tomee-jakartaee-api[JakartaEE API Uber JAR]
 - link:https://github.com/apache/tomee-patch-plugin[Patch Plugin]
 - link:https://github.com/apache/tomee-tck[TCK Harness]
 - link:https://github.com/dblevins/sxc[SXC Source Code]
+- link:https://svn.apache.org/repos/asf/tomee/deps/[3rd Party Shaded 
Dependencies (SVN)] - Build for other projects with slight modifications. This 
is currently done in `deps` in the link:https://github.com/apache/tomee[Main 
Repository].
+
+=== Mirror / Release Area
 
- Tools
+- link:https://dist.apache.org/repos/dist/dev/tomee/[dist/dev]
+- link:https://dist.apache.org/repos/dist/release/tomee/[dist/release]
+- link:https://repository.apache.org/[ASF Nexus Repository]
+
+=== Tools
 
 - link:https://github.com/apache/tomee-release-tools[Release Tools]
 
- Website
+=== Website
 
 - link:https://github.com/apache/tomee-site-generator[Website Generator]
 - link:https://github.com/apache/tomee-site-pub[Generated Website Code]
+- 
link:https://matomo.privacy.apache.org/index.php?module=CoreHome=index=yesterday=day=5[Matomo
 Tracking]
 
-== CI / CD
+=== CI / CD
 
 - link:https://ci-builds.apache.org/job/Tomee/[Jenkins Build Server]
+- link:https://tck.work/tomee/projects[TCK Runs & Results by Tomitribe]
+
+=== Misc
+
+- link:https://people.apache.org/committers-by-project.html#tomee[TomEE 
Committers & PMC Overview]
+- link:https://people.apache.org/[ASF Committer Overview]
 
-== Misc
+=== ASF Committer Resources
 
-- 
link:https://matomo.privacy.apache.org/index.php?module=CoreHome=index=yesterday=day=5[ASF
 Matomo Tracking]
-- link:https://tck.work/tomee/projects[TCK Runs & Results by Tomitribe]
\ No newline at end of file
+- link:https://svn.apache.org/repos/private/committers[ASF Committer SVN 
Repository]
+- link:https://id.apache.org/[ASF LDAP Management]
+- link:https://s.apache.org/[ASF URL Shortener]
\ No newline at end of file