Re: [DISCUSS] Drop TomEE 8.x docker images?

[Cesar Hernandez]

+1 to drop TomEE 8 Docker images.

El mié, 10 abr 2024 a las 15:25, Rod Jenkins ()
escribió:

> Given that the voting is going on as we speak, I think that is a good idea.
>
> I will get the current PR merged, then when 9.1.3 is released, I will get
> that updated and moved to latest.
>
>
> Rod.
>
> 
> From: Alex The Rocker 
> Sent: Wednesday, April 10, 2024 12:53 AM
> To: dev@tomee.apache.org 
> Subject: Re: [DISCUSS] Drop TomEE 8.x docker images?
>
> (my two cents)
> wouln't it be better to wait a little bit for 9.1.3 to be released, so
> as to avoid releasing a Docker image with high CVEs ?
>
> Alex
>
> Le mar. 9 avr. 2024 à 23:50, Rod Jenkins  a
> écrit :
> >
> > All,
> >
> > I was looking at the "latest" tag for the official images.  The latest
> tag is pointed to 8.0.16-jre17-Temurim-ubuntu-webprofile.
> >
> > If we are going to drop TomEE 8, then I would suggest using
> 9.1.2-jre17-Temurin-ubuntu-webprofile.
> >
> > Also given Temurin is the default, can we get consensus to drop Semeru?
> This would make a serious dent in our image count.
> >
> > Comment please
> >
> > Thanks,
> > Rod.
> >
> > 
> > From: Rod Jenkins 
> > Sent: Tuesday, April 9, 2024 5:06 AM
> > To: dev@tomee.apache.org 
> > Subject: Re: [DISCUSS] Drop TomEE 8.x docker images?
> >
> > Marcus,
> >
> > Thank you for the PR.  I’ll get that reviewed later today.   I agree
> that we need to reduce the number of images.  This is something that was
> brought up before.
> >
> > We should drop 8.x given its EOL.
> >
> > Thanks,
> > Rod.
> >
> > Sent from my iPhone
> >
> > > On Apr 9, 2024, at 2:35 AM, Markus Jung  wrote:
> > >
> > > Hi all,
> > >
> > >
> > > I just opened a PR to add TomEE 10.0.0-M1 Dockerfiles [1], we're now
> at 80 different variants of docker images being built for tomee:
> > >
> > > $ find . -name Dockerfile | wc -l
> > > 80
> > >
> > > In the future this number could increase even more when we add docker
> images based on Java 21. (Depending on if we continue support for Java 11
> [2])
> > >
> > >
> > > IMO we should drop Dockerfiles for TomEE  8.x, it's EOL and there
> really is no need to continue building docker images for it. WDYT?
> > >
> > >
> > >
> > > Thanks
> > >
> > >
> > > Markus
> > >
> > > [1] https://github.com/tomitribe/docker-tomee/pull/89
> > >
> > > [2] https://lists.apache.org/thread/4qox0vtoyv535w8cfkfqbx8swz95000q
> > >
>


-- 
Atentamente:
César Hernández.

Re: [VOTE] Apache TomEE 9.1.3

[Cesar Hernandez]

+1 thank you.

El mar, 9 abr 2024 a las 23:40, Thomas Andraschko (<
andraschko.tho...@gmail.com>) escribió:

> +1
>
> Alex The Rocker  schrieb am Mi., 10. Apr. 2024,
> 07:23:
>
> > +1 (non-binding)
> >
> > Successfully tested the TomEE 9.1.3 release candidate with TomEE+ with
> > more than 10 different web applications, with both Java 17 and Java 21
> > as the Java runtime (Java sources have been compiled with a JDK 17) on
> > Linux Redhat 8, and using of these various Jakarta EE 9 features:
> >   Servlet, JSP, EJB, CDI, JAX RS, JSON-P, JMS (in some cases with the
> > embedded AMQ and using connection to remote AMQ server in other
> > cases), Websockets, and JavaMail
> > I observed no performance issues, and confirm that CVE fixes and port
> > of TomEE 8's of placeholder support in MDBs.
> >
> > And special thanks to Richard for having ran this Apache TomEE 9.1.3
> > vote : I understand the difficulty to keep 9.x versions maintained
> > until 10.x is released (thanks for its M1 milestone too), I hope there
> > will not be too many critical CVEs coming out on 9.x before 10.x is
> > released...
> >
> > Alex
> >
> > Le lun. 8 avr. 2024 à 14:57, Alex The Rocker  a
> > écrit :
> > >
> > > Thank you very much Richard for this very kind effort !
> > > I have started some validations with this TomEE 9.1.3 candidate
> > > release, so far so good, but I want to run as many tests as possible
> > > with the broadest possible scope.
> > > I should be able to provide a vote Wednesday this week at most.
> > >
> > > Alex
> > >
> > > Le lun. 8 avr. 2024 à 11:34, Richard Zowalla  a
> écrit :
> > > >
> > > > Hello everyone,
> > > >
> > > > This is a vote for the release of Apache TomEE 9.1.3
> > > >
> > > > It contains some version upgrades (cxf, jackson, batchee) and
> security
> > > > backports for the recent Tomcat CVEs.
> > > >
> > > > Here are the hard facts:
> > > >
> > > > ###
> > > >
> > > > Maven Repo:
> > > >
> > https://repository.apache.org/content/repositories/orgapachetomee-1227/
> > > >
> > > > 
> > > > 
> > > > tomee-9.1.3-rc1
> > > > Testing TomEE 9.1.3
> > > > 
> > > >
> > https://repository.apache.org/content/repositories/orgapachetomee-1227/
> > > > 
> > > > 
> > > > 
> > > >
> > > > ###
> > > >
> > > > Binaries & Source:
> > > >
> > > >
> https://dist.apache.org/repos/dist/dev/tomee/staging-1227/tomee-9.1.3/
> > > >
> > > > ###
> > > >
> > > > Tag:
> > > >
> > > > https://github.com/apache/tomee/releases/tag/tomee-project-9.1.3
> > > >
> > > > ###
> > > >
> > > > Release notes:
> > > >
> > > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12354125
> > > >
> > > > ###
> > > >
> > > > Here is an adoc generated version of the changelog as well:
> > > >
> > > > == Dependency upgrade
> > > >
> > > > [.compact]
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4305[TOMEE-4305]
> > > > Backport fix for CVE-2024-23672 for TomEE 9.x
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4306[TOMEE-4306]
> > > > Backport fix for CVE-2024-24549 for TomEE 9.x
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4316[TOMEE-4316]
> > > > BatchEE 1.0.4
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4290[TOMEE-4290]
> > > > Jackson 2.16.2
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4304[TOMEE-4304]
> > > > cxf-core 4.0.4
> > > >
> > > > == New Feature
> > > >
> > > > [.compact]
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-3902[TOMEE-3902]
> > > > Introduce placeholder replacement to enable MDB activation properties
> > > > to be more customizable
> > > >
> > > > == Bug
> > > >
> > > > [.compact]
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4295[TOMEE-4295]
> > > > tomee-embedded-maven-plugin does not register microprofile endpoints
> > > >
> > > >
> > > > ###
> > > >
> > > > Please note:
> > > >
> > > > Grype will report a vulnerability for
> > > >
> > > > apache-mime4j-core  0.8.7  0.8.10java-archive
> GHSA-jw7r-rxff-
> > > > gv24  Medium
> > > >
> > > > which is shaded inside of "geronimo-mail_2.1_spec-1.0.0-M1.jar".
> > > >
> > > > In it's current version, the dependency is _NOT_ used inside of
> > > > geronimo mail impl, so unless you are using the shaded classes
> > > > yourself, we are not affected here.
> > > > There is also another mail thread related to mail.
> > > >
> > > > For signature verification, you can check on the example script here:
> > > > https://gist.github.com/rzo1/9fb1ca0d58e1fc982d596f2a94b10b32
> > > >
> > > > ###
> > > >
> > > > Please VOTE
> > > >
> > > > [+1] go ship it
> > > > [+0] meh, don't care
> > > > [-1] stop, there is a ${showstopper}
> > > >
> > > > The VOTE is open for 72h or as long as needed.
> > > >
> > > > Gruß
> > > > Richard
> > > >
> > > >
> > > > P.S. On a personal note: This will be the last TomEE 9.1.x release I
> > > > will be working on (no backports from my side 

Re: [VOTE] Apache TomEE 10.0.0-M1

[Cesar Hernandez]

+1 thank you.

El lun, 8 abr 2024 a las 1:16, Mark Struberg ()
escribió:

> +1
>
> txs and LieGrue,
> strub
>
>
> > Am 02.04.2024 um 09:47 schrieb Richard Zowalla :
> >
> > Hello everyone,
> >
> > This is a vote for the release of Apache TomEE 10.0.0-M1.
> >
> > It is a first milestone release of TomEE 10 targeting JakartaEE 10.
> > Thanks to everyone who contributed code to make this happen.
> > I would like to emphasise and give a shout out to all our volunteers
> > who have done the hard work for EE10, which is also done in all our
> > upstream dependencies like Tomcat, OWB, CXF, MyFaces, etc.
> >
> > This milestone release is not fully compliant with JakartaEE 10 as we
> > are missing some EE10 compatible versions of our dependencies (most
> > notably CXF 4.1.x which isn't available yet).
> > We do not pass the TCK, nor do we have a fully working TCK setup at the
> > moment. However, our own full build is green [1] and so I am happy to
> > call for a vote to release a first milestone of TomEE 10.
> >
> > Here are the hard facts:
> >
> > ###
> >
> > Maven Repo:
> > https://repository.apache.org/content/repositories/orgapachetomee-1226/
> >
> > 
> > 
> > tomee-10.0.0-M1-rc1
> > Testing TomEE 10.0.0-M1
> > 
> > https://repository.apache.org/content/repositories/orgapachetomee-1226/
> > 
> > 
> > 
> >
> > ###
> >
> > Binaries & Source:
> >
> >
> https://dist.apache.org/repos/dist/dev/tomee/staging-1226/tomee-10.0.0-M1/
> >
> > ###
> >
> > Tag:
> >
> > https://github.com/apache/tomee/releases/tag/tomee-project-10.0.0-M1
> >
> >
> > ###
> >
> > Release notes:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12352714
> >
> > ###
> >
> > Here is an adoc generated version of the changelog as well:
> >
> > == Dependency upgrade
> >
> > [.compact]
> > - link:https://issues.apache.org/jira/browse/TOMEE-4266[TOMEE-4266]
> > ActiveMQ 5.16.7 / 5.18.3
> > - link:https://issues.apache.org/jira/browse/TOMEE-4217[TOMEE-4217]
> > Arquillian 1.7.0.Final
> > - link:https://issues.apache.org/jira/browse/TOMEE-4307[TOMEE-4307]
> > BatchEE 1.0.4
> > - link:https://issues.apache.org/jira/browse/TOMEE-4235[TOMEE-4235]
> > Bouncy Castle 1.75
> > - link:https://issues.apache.org/jira/browse/TOMEE-4243[TOMEE-4243]
> > Bouncy Castle 1.76
> > - link:https://issues.apache.org/jira/browse/TOMEE-4278[TOMEE-4278]
> > Commons CLI 1.6.0
> > - link:https://issues.apache.org/jira/browse/TOMEE-4277[TOMEE-4277]
> > Commons Codec 1.16.0
> > - link:https://issues.apache.org/jira/browse/TOMEE-4274[TOMEE-4274]
> > Commons DBCP 2.11.0
> > - link:https://issues.apache.org/jira/browse/TOMEE-4275[TOMEE-4275]
> > Commons Lang3 3.13.0
> > - link:https://issues.apache.org/jira/browse/TOMEE-4310[TOMEE-4310]
> > Commons Net 3.9.0
> > - link:https://issues.apache.org/jira/browse/TOMEE-4308[TOMEE-4308]
> > Fileupload 2 (Jakarta
> > - link:https://issues.apache.org/jira/browse/TOMEE-4218[TOMEE-4218]
> > HSQLDB 2.7.2
> > - link:https://issues.apache.org/jira/browse/TOMEE-4221[TOMEE-4221]
> > JUnit 5.9.3
> > - link:https://issues.apache.org/jira/browse/TOMEE-4212[TOMEE-4212]
> > Jackson 2.15.0
> > - link:https://issues.apache.org/jira/browse/TOMEE-4216[TOMEE-4216]
> > Jackson 2.15.1
> > - link:https://issues.apache.org/jira/browse/TOMEE-4227[TOMEE-4227]
> > Jackson 2.15.2
> > - link:https://issues.apache.org/jira/browse/TOMEE-4276[TOMEE-4276]
> > Jackson 2.15.3
> > - link:https://issues.apache.org/jira/browse/TOMEE-4208[TOMEE-4208]
> > Johnzon 1.2.20
> > - link:https://issues.apache.org/jira/browse/TOMEE-4228[TOMEE-4228]
> > Johnzon 1.2.21
> > - link:https://issues.apache.org/jira/browse/TOMEE-4205[TOMEE-4205]
> > Jose4j 0.9.3
> > - link:https://issues.apache.org/jira/browse/TOMEE-4279[TOMEE-4279]
> > Log4J2 2.21.1
> > - link:https://issues.apache.org/jira/browse/TOMEE-4296[TOMEE-4296]
> > MicroProfile JWT 2.1
> > - link:https://issues.apache.org/jira/browse/TOMEE-4283[TOMEE-4283]
> > OWB 4.0.1
> > - link:https://issues.apache.org/jira/browse/TOMEE-4282[TOMEE-4282]
> > Tomcat 10.1.16
> > - link:https://issues.apache.org/jira/browse/TOMEE-4309[TOMEE-4309]
> > Tomcat 10.1.20
> > - link:https://issues.apache.org/jira/browse/TOMEE-4280[TOMEE-4280]
> > WSS4J 3.0.2
> > - link:https://issues.apache.org/jira/browse/TOMEE-4313[TOMEE-4313]
> > XBean 4.24
> > - link:https://issues.apache.org/jira/browse/TOMEE-4232[TOMEE-4232]
> > bcprov-jdk15to18-1.74.jar
> > - link:https://issues.apache.org/jira/browse/TOMEE-4220[TOMEE-4220]
> > log4j 2.20.0 (integration)
> > - link:https://issues.apache.org/jira/browse/TOMEE-4311[TOMEE-4311]
> > log4j2 2.23.1
> > - link:https://issues.apache.org/jira/browse/TOMEE-4312[TOMEE-4312]
> > slf4j 2.0.12
> > - link:https://issues.apache.org/jira/browse/TOMEE-4213[TOMEE-4213]
> > snakeyaml version 2.0 mitigate CVE-2022-1471
> > - link:https://issues.apache.org/jira/browse/TOMEE-4219[TOMEE-4219]
> > xbeans 4.23
> >
> > == New Feature
> >
> > [.compact]

Re: Error when starting up TomEE Plus 9.1.2

[Cesar Hernandez]

Hello,

It seems the name changed [1] around Tomcat 10.0.0-M2 milestones.
https://tomcat.apache.org/tomcat-10.0-doc/changelog.html

[1]
Rename org.apache.tomcat.util.digester.Digester$EnvironmentPropertySource
to org.apache.tomcat.util.digester.EnvironmentPropertySource. Patch
provided by Bernd Bohmann. (markt)

El vie, 16 feb 2024 a las 10:59, COURTAULT Francois
() escribió:

> THALES GROUP LIMITED DISTRIBUTION to email recipients
>
> Hello everyone,
>
> A person who has left the company add this line in the catalina.properties
> file:
>
> org.apache.tomcat.util.digester.PROPERTY_SOURCE=org.apache.tomcat.util.digester.Digester$EnvironmentPropertySource
>
> Reading at Tomcat 8.5 doc, I found this
> org.apache.tomcat.util.digester.PROPERTY_SOURCE : Set this to a comma
> separated list of fully qualified name of classes that implement
> org.apache.tomcat.util.IntrospectionUtils.PropertySource.
> Required to have a public constructor with no arguments.
>
> Possible value: org.apache.tomcat.util.digester.EnvironmentPropertySource
> and not org.apache.tomcat.util.digester.Digester$EnvironmentPropertySource
> as the person set it.
>
> org.apache.tomcat.util.digester.EnvironmentPropertySource can be used to
> replace parameters from the process' environment variables, e.g. injected
> ConfigMaps or Secret objects in container based systems like OpenShift or
> Kubernetes.
>
> Do you think that this person has made a mistake?
>
> The funny thing is that with TomEE Plus 8.0.16, the last sections of
> catalina.properties looks like below
> # String cache configuration.
> tomcat.util.buf.StringCache.byte.enabled=true
> #tomcat.util.buf.StringCache.char.enabled=true
> #tomcat.util.buf.StringCache.trainThreshold=50
> #tomcat.util.buf.StringCache.cacheSize=5000
>
> # Disable use of some privilege blocks Tomcat doesn't need since calls to
> the
> # code in question are always already inside a privilege block
> org.apache.el.GET_CLASSLOADER_USE_PRIVILEGED=false
>
> org.apache.tomcat.util.digester.PROPERTY_SOURCE=org.apache.tomcat.util.digester.Digester$EnvironmentPropertySource
> and I got no error 
>
> With TomEEFull 9.1.2, the last section looks like below:
> # String cache configuration.
> tomcat.util.buf.StringCache.byte.enabled=true
> #tomcat.util.buf.StringCache.char.enabled=true
> #tomcat.util.buf.StringCache.trainThreshold=50
> #tomcat.util.buf.StringCache.cacheSize=5000
>
> org.apache.tomcat.util.digester.PROPERTY_SOURCE=org.apache.tomcat.util.digester.Digester$EnvironmentPropertySource
>
> This time I got some errors like
>
>   *   16-Feb-2024 08:35:34.848 SEVERE [main]
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke Error loading property
> source [org.apache.tomcat.util.digester.Digester$EnvironmentPropertySource]
> java.lang.ClassNotFoundException:
> org.apache.tomcat.util.digester.Digester$EnvironmentPropertySource
>
> I don’t understand why I got no error with TomEE Plus 8.0.16 because in
> each case the class
> org.apache.tomcat.util.digester.Digester$EnvironmentPropertySource
> doesn’t exist. I was not able to find it (it should be in the
> tomcat-util-scan.jar).
>
> So my guess is that this guy did a mistake by setting the property
> org.apache.tomcat.util.digester.PROPERTY_SOURCE to
> org.apache.tomcat.util.digester.Digester$EnvironmentPropertySource
> instead of org.apache.tomcat.util.digester.EnvironmentPropertySource.
> Do you agree ?
>
> Best Regards.
>
>
>
>

-- 
Atentamente:
César Hernández.

Re: [VOTE] TomEE 8.0.16 (RC2)

[Cesar Hernandez]

+1

On Thu, Nov 2, 2023 at 05:10 Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:

> +1
>
> Thanks for doing the release, Jonathan!
>
> On Sun, Oct 29, 2023 at 6:35 PM Richard Zowalla  wrote:
>
> > Hi all,
> >
> > This is the second attempt for a vote for a release of Apache TomEE
> > 8.0.16. The first vote was cancelled due to some issues with the BOM
> > modules.
> >
> > I'd like to start with a big thank you and a big applause to Jonathan
> > Fisher. He is rolling out his first release today.
> >
> > Per ASF rules, the actual VOTE needs to be run by a TomEE PMC member,
> > that's why I'm starting it.
> >
> > However, the work has been done by Jonathan, so thank you. Well done.
> >
> > TomEE 8.0.16 is a maintenance release with dependencies
> > upgrades and bug fixes. It also fixes the latest Tomcat vulnerabilities
> > as well as other CVEs.
> >
> > ###
> >
> > Maven Repo:
> > https://repository.apache.org/content/repositories/orgapachetomee-1223/
> >
> > 
> > 
> > tomee-8.0.16-rc2
> > Testing TomEE 8.0.16 RC2
> > 
> > https://repository.apache.org/content/repositories/orgapachetomee-1223/
> > 
> > 
> > 
> >
> > ###
> >
> > Binaries & Source:
> >
> > https://dist.apache.org/repos/dist/dev/tomee/staging-1222/tomee-8.0.16/
> >
> > ###
> >
> > Tag:
> >
> > https://github.com/apache/tomee/releases/tag/tomee-project-8.0.16
> >
> >
> > ###
> >
> > Release notes:
> >
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12353257
> >
> > ###
> >
> > Here is an adoc generated version of the changelog as well:
> >
> > == Dependency upgrade
> >
> > [.compact]
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4266[TOMEE-4266]
> > ActiveMQ 5.16.7 / 5.18.3
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4234[TOMEE-4234]
> > Bouncy Castle 1.75
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4229[TOMEE-4229]
> > CVE-2023-34981
> > <
> https://issues.apache.org/jira/browse/TOMEE-4229%5BTOMEE-4229%5DCVE-2023-34981
> >
> > in TomEE 8.0.15
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4218[TOMEE-4218]
> > HSQLDB 2.7.2
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4221[TOMEE-4221]
> > JUnit 5.9.3
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4216[TOMEE-4216]
> > Jackson 2.15.1
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4227[TOMEE-4227]
> > Jackson 2.15.2
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4228[TOMEE-4228]
> > Johnzon 1.2.21
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4263[TOMEE-4263]
> > Santuario Java (xmlsec) mitigate CVE-2023-44483
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4224[TOMEE-4224]
> > Tomcat 9.0.76
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4237[TOMEE-4237]
> > Tomcat 9.0.79
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4252[TOMEE-4252]
> > Tomcat 9.0.80
> > - link:https://issues.apache.org/jira/browse/TOMEE-4238[TOMEE-4238]
> > Tomcat 9.0.82
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4262[TOMEE-4262]
> > eclipselink 2.7.13
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4220[TOMEE-4220]
> > log4j
> > 
> > 2.20.0 (integration)
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4219[TOMEE-4219]
> > xbeans 4.23
> >
> > == Bug
> >
> > [.compact]
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4222[TOMEE-4222]
> > @LoginToContinue JSR-375 (JavaEE Security API) causes
> > IllegalArgumentException
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4226[TOMEE-4226]
> > DataSource definition fails when @DataSourceDefinition doesn't define
> > url property
> >
> > == Improvement
> >
> > [.compact]
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4031[TOMEE-4031]
> > Improve TomEE Jmx Mbean Support for Parameter Names
> >
> > == Fixed Common Vulnerabilities and Exposures (CVEs)
> >
> > [.compact]
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4234[TOMEE-4234]
> > Bouncy Castle 1.75
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4238[TOMEE-4238]
> > Tomcat 9.0.80
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4227[TOMEE-4227]
> > Jackson 2.15.2
> >  - link:https://issues.apache.org/jira/browse/TOMEE-4229[TOMEE-4229]
> > CVE-2023-34981
> > <
> https://issues.apache.org/jira/browse/TOMEE-4229%5BTOMEE-4229%5DCVE-2023-34981
> >
> > in Apache TomEE 8.0.15
> >
> > 
> >
> > Please VOTE
> >
> > [+1] go ship it
> > [+0] meh, don't care
> > [-1] stop, there is a ${showstopper}
> >
> > The VOTE is open for 72h or as long as needed.
> >
> > Gruß
> > Richard
> >
> >
>

Re: [VOTE] TomEE 9.1.1

[Cesar Hernandez]

+1 thank you!

On Mon, Oct 16, 2023 at 04:30 Richard Zowalla  wrote:

> Thanks for testing, Alex!
>
> Am Montag, dem 16.10.2023 um 12:24 +0200 schrieb Alex The Rocker:
> > +1 (non binding)
> >
> > Ran various tests with web apps based on JAX-WS, JAX-RS, JMS, CDI,
> > Entiy Beans; with some relying on Tomcat SSL connector, etc running
> > with Java 17 on Red Hat Linux 8
> > => Found no regressions, thank you very much for the security fixes !
> >
> > Alex
> >
> > Le jeu. 12 oct. 2023 à 17:14, Alex The Rocker 
> > a écrit :
> > >
> > > Excellent news!
> > > I'm going to run some deep (applicative) tests with this candidate
> > > release and I will provide feedbacks asap
> > >
> > > Le jeu. 12 oct. 2023 à 15:28, Daniel Dias Dos Santos
> > >  a écrit :
> > > >
> > > > Hi
> > > >
> > > > +1
> > > >
> > > > Thanks
> > > >
> > > > On Thu, Oct 12, 2023, 10:26 benedict 
> > > > wrote:
> > > >
> > > > > +1
> > > > >  Ursprüngliche Nachricht Von: Richard Zowalla <
> > > > > r...@apache.org> Datum: 12.10.23  14:59  (GMT+01:00) An:
> > > > > dev@tomee.apache.org Betreff: [VOTE] TomEE 9.1.1 Hi all,this is
> > > > > a vote
> > > > > for a release of Apache TomEE 9.1.1.It is a maintenance release
> > > > > with
> > > > > dependenciesupgrades and bug fixes. The most notible change is
> > > > > dropping our
> > > > > owncxf-shade in favour of CXF 4.0.3It also fixes the latest
> > > > > Tomcat
> > > > > vulnerabilities by backporting andpatching Tomcat inside the
> > > > > TomEE 9
> > > > > build.This release still passes the full EE9.1 TCK (thx to
> > > > > Jean-Louis &
> > > > > Jonfor triggering the builds) as well as the MP 5.0
> > > > > TCK.###Maven Repo:
> > > > >
> https://repository.apache.org/content/repositories/orgapachetomee-1220/
> > > > > tomee-9.1.1-rc1Testing
> > > > > TomEE 9.1.1 RC1
> > > > >
> https://repository.apache.org/content/repositories/orgapachetomee-1220/
> > > > > ###Binaries
> > > > > & Source:
> > > > >
> https://dist.apache.org/repos/dist/dev/tomee/staging-1220/tomee-9.1.1/###Tag:https://github.com/apache/tomee/releases/tag/tomee-project-9.1.1###Release
> > > > > notes:
> > > > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12353331###Here
> > > > > is an adoc generated version of the changelog as well:==
> > > > > Dependency
> > > > > upgrade[.compact] - link:
> > > > >
> https://issues.apache.org/jira/browse/TOMEE-4246[TOMEE-4246]ActiveMQ
> > > > > 5.18.2 - link:
> > > > >
> https://issues.apache.org/jira/browse/TOMEE-4230[TOMEE-4230]Backport
> > > > >  fix
> > > > > for CVE-2023-34981 - link:
> > > > >
> https://issues.apache.org/jira/browse/TOMEE-4239[TOMEE-4239]Backport
> > > > >  fix
> > > > > for CVE-2023-41080 - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-4235[TOMEE-4235]Bouncy
> > > > >  Castle
> > > > > 1.75 - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-4243[TOMEE-4243]Bouncy
> > > > >  Castle
> > > > > 1.76 - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-4139[TOMEE-4139]CXF
> > > > >  4.0.3
> > > > > (jakarta namespace) - link:
> > > > >
> https://issues.apache.org/jira/browse/TOMEE-4247[TOMEE-4247]Hibernate
> > > > > 6.1.7 - link:
> > > > >
> https://issues.apache.org/jira/browse/TOMEE-4227[TOMEE-4227]Jackson
> > > > > 2.15.2 - link:
> > > > >
> https://issues.apache.org/jira/browse/TOMEE-4228[TOMEE-4228]Johnzon
> > > > > 1.2.21 - link:
> > > > >
> https://issues.apache.org/jira/browse/TOMEE-4248[TOMEE-4248]Mojarra
> > > > >  3.0.5
> > > > > -
> > > > > link:https://issues.apache.org/jira/browse/TOMEE-4254[TOMEE-425
> > > > > 4]Port
> > > > > fix for CVE-2023-42795 - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-4255[TOMEE-4255]Port
> > > > >  fix for
> > > > > CVE-2023-44487 - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-4256[TOMEE-4256]Port
> > > > >  fix for
> > > > > CVE-2023-45648 - link:
> > > > >
> https://issues.apache.org/jira/browse/TOMEE-4249[TOMEE-4249]SnakeYAML
> > > > >  2.2
> > > > > -
> > > > > link:https://issues.apache.org/jira/browse/TOMEE-4250[TOMEE-425
> > > > > 0]WSS4J
> > > > > 3.0.1 - link:
> > > > >
> https://issues.apache.org/jira/browse/TOMEE-4232[TOMEE-4232]bcprov-jdk15to18-1.74.jar
> > > > > -
> > > > > link:https://issues.apache.org/jira/browse/TOMEE-4251[TOMEE-425
> > > > > 1]xmlsec
> > > > > 3.0.2== Bug[.compact] - link:
> > > > >
> https://issues.apache.org/jira/browse/TOMEE-4222[TOMEE-4222]@LoginToContinue
> > > > > JSR-375 (JavaEE Security API) causesIllegalArgumentException -
> > > > > link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-4225[TOMEE-4225]Remove
> > > > > commons-net from TomEE distribution - link:
> > > > >
> https://issues.apache.org/jira/browse/TOMEE-4226[TOMEE-4226]DataSource
> > > > > definition fails when @DataSourceDefinition doesn't defineurl
> > > > > property==
> > > > > Improvement[.compact] - link:
> > > > >
> 

Re: [VOTE] JakartaEE API 10.0-M2 - RC2

[Cesar Hernandez]

+1 thank you!

El lun, 2 oct 2023 a las 8:49, Daniel Dias Dos Santos (<
daniel.dias.analist...@gmail.com>) escribió:

> Hello,
>
> +1
>
> Thanks
>
> On Mon, Oct 2, 2023, 08:24 Richard Zowalla  wrote:
>
> > Hi all,
> >
> > this is a VOTE for a milestone release of our JakartaEE 10 shade
> > artifact.
> >
> > Compared to the previous milestone release, it fixes
> >
> > - TOMEE-4199 - https://issues.apache.org/jira/browse/TOMEE-4199
> > - TOMEE-4245 - https://issues.apache.org/jira/browse/TOMEE-4245
> >
> > The main difference to the previous release candidate is, that this
> > milestone now actually includes EE10 apis. The previous milestone (M1)
> > included Servlet 5 (instead of 6) resulting in runtime errors in an
> > actual environment, if components rely on the EE10 apis.
> >
> > Sorry for the time already invested in reviewing RC1 :/
> >
> > ###
> >
> > Maven Repo:
> >
> > https://repository.apache.org/content/repositories/orgapachetomee-1219/
> >
> > ###
> >
> > Source:
> >
> > https://dist.apache.org/repos/dist/dev/tomee/jakartaee-api-10.0-M2/
> >
> > ###
> >
> > Tag:
> >
> >
> >
> https://github.com/apache/tomee-jakartaee-api/releases/tag/jakartaee-api-10.0-M2
> >
> >
> >
> > ###
> >
> > Please VOTE
> >
> > [+1] go ship it
> > [+0] meh, don't care
> > [-1] stop, there is a ${showstopper}
> >
> > The VOTE is open for 72h or as long as needed.
> >
> > Gruß
> > Richard
> >
> >
> >
>


-- 
Atentamente:
César Hernández.

Re: [VOTE] JakartaEE API 10.0-M2

[Cesar Hernandez]

+1 thank you.

On Fri, Sep 29, 2023 at 07:37 Richard Zowalla  wrote:

> Hi all,
>
> this is a vote for a milestone release of our JakartaEE 10 shade
> artifact
>
> This bug fix release only fixes TOMEE-4199:
> https://issues.apache.org/jira/browse/TOMEE-4199
>
> ###
>
> Maven Repo:
>
> https://repository.apache.org/content/repositories/orgapachetomee-1218/
>
> ###
>
> Source:
>
> https://dist.apache.org/repos/dist/dev/tomee/jakartaee-api-10.0-M2/
>
> ###
>
> Tag:
>
>
> https://github.com/apache/tomee-jakartaee-api/releases/tag/jakartaee-api-10.0-M2
>
>
>
> ###
>
> Please VOTE
>
> [+1] go ship it
> [+0] meh, don't care
> [-1] stop, there is a ${showstopper}
>
> The VOTE is open for 72h or as long as needed.
>
> Gruß
> Richard
>
>

Re: TomEE 9.1.1 soon?

[Cesar Hernandez]

+1 thank you.

On Fri, Sep 29, 2023 at 08:10 benedict  wrote:

> +1
>  Ursprüngliche Nachricht Von: Richard Zowalla <
> r...@apache.org> Datum: 29.09.23  15:40  (GMT+01:00) An:
> dev@tomee.apache.org Betreff: TomEE 9.1.1 soon? Hi all,since we have now
> dropped our cxf shade in favour of 4.0.3 and fixedsome dependencies, etc.
> in the last weeks, what do you think about aTomEE 9.1.1 soon?We are still
> passing the TCK, so would be a good thing, imho.Any objections?
> Wdyt?GrußRichard

Re: Good news on CXF4

[Cesar Hernandez]

Thanks Richard for the good news!

El jue, 31 ago 2023 a las 14:04, Daniel Dias Dos Santos (<
daniel.dias.analist...@gmail.com>) escribió:

> Hello,
>
> Very good.
>
>
>
>
> On Thu, Aug 31, 2023, 13:55 Richard Zowalla  wrote:
>
> > Hey ladies,
> >
> > some good news:
> >
> > We are now passing the JAX-RS part of the EE9.1 tck with the latest CXF
> > 4.0.3-SNAPSHOT [1]. Don't bother about the json-p failures, which are
> > unrelated (they are also failing for our shading approach and TomEE 10,
> > so no regression here).
> >
> > Overall, I think, that we can now drop our CXF 3.5.5 Shade for TomEE
> > 9.1.x and TomEE 10 and use the "native" Jakarta version of CXF instead.
> >
> > The CXF guys plan to do a release in Mid/End of September, so we can
> > live with a SNAPSHOT for now imho.
> >
> > Any objections in bringing it into 10 _and_ 9.1.x ?
> >
> > Gruß
> > Richard
> >
> >
> > [1] https://tck.work/tomee/build?id=1693492927456
> > [2] https://github.com/apache/tomee/pull/1061
> > [3] https://github.com/apache/tomee/pull/1062
> >
>


-- 
Atentamente:
César Hernández.

Re: [HELP] Build times for Infra

[Cesar Hernandez]

>Great work!!
Thank you, good catch on your PR comment, I just updated it and added the
missing license headers.

>So, the idea of building in AWS is finally coming to fruition?
Yes, that's right. The Infra team has done an awesome job moving the
initiative forward.


El jue, 25 may 2023 a las 3:10, Richard Zowalla ()
escribió:

> Great work!!
>
>
>
> Am Mittwoch, dem 24.05.2023 um 16:58 -0700 schrieb David Blevins:
> > That’s amazing.  So the idea of building in AWS is finally coming to
> > fruition?
> >
> >
> > -David
> >
> > > On May 24, 2023, at 4:13 PM, Cesar Hernandez 
> > > wrote:
> > >
> > > Good news, I opened a PR in
> > > https://issues.apache.org/jira/browse/TOMEE-4196
> > > to include Jenkins pipelines for our main branch.
> > > Notice that the type of machine now used allows us now to have a
> > > full build
> > > of 2 hours instead of the ~4.5 we currently have.
> > > Once approved the PR, I can swap the existing maven jobs with the
> > > pipelines
> > > ones for main branch and then we can rinse an repeat for the rest
> > > of
> > > branches.
> > >
> > >
> > >
> > >
> > > El lun, 24 oct 2022 a las 6:03, Richard Zowalla ()
> > > escribió:
> > >
> > > > Awesome news! Looking forward to see faster turn around times.
> > > >
> > > > Gruß
> > > > Richard
> > > >
> > > > Am Donnerstag, dem 20.10.2022 um 18:57 -0700 schrieb David
> > > > Blevins:
> > > > > A few of us got together with some fine folks in Apache Infra
> > > > > and
> > > > > discussed getting builds going in AWS using an instance type
> > > > > that
> > > > > would give us the under 2-hour build time.  Turns out this one
> > > > > was
> > > > > also on Infra's wishlist and just needed someone to volunteer
> > > > > to step
> > > > > up and own the task.  Cesar volunteered to lead an effort. :)
> > > > >
> > > > > Big thank you to Cesar!!  If anyone wants to help, join this
> > > > > list and
> > > > > keep an eye out for related emails.
> > > > >
> > > > > - https://lists.apache.org/list.html?bui...@apache.org
> > > > >
> > > > >
> > > >
> > > >
> > >
> > > --
> > > Atentamente:
> > > César Hernández.
> >
>
>

-- 
Atentamente:
César Hernández.

Re: [HELP] Build times for Infra

[Cesar Hernandez]

Good news, I opened a PR in https://issues.apache.org/jira/browse/TOMEE-4196
to include Jenkins pipelines for our main branch.
Notice that the type of machine now used allows us now to have a full build
of 2 hours instead of the ~4.5 we currently have.
Once approved the PR, I can swap the existing maven jobs with the pipelines
ones for main branch and then we can rinse an repeat for the rest of
branches.




El lun, 24 oct 2022 a las 6:03, Richard Zowalla ()
escribió:

> Awesome news! Looking forward to see faster turn around times.
>
> Gruß
> Richard
>
> Am Donnerstag, dem 20.10.2022 um 18:57 -0700 schrieb David Blevins:
> > A few of us got together with some fine folks in Apache Infra and
> > discussed getting builds going in AWS using an instance type that
> > would give us the under 2-hour build time.  Turns out this one was
> > also on Infra's wishlist and just needed someone to volunteer to step
> > up and own the task.  Cesar volunteered to lead an effort. :)
> >
> > Big thank you to Cesar!!  If anyone wants to help, join this list and
> > keep an eye out for related emails.
> >
> >  - https://lists.apache.org/list.html?bui...@apache.org
> >
> >
>
>

-- 
Atentamente:
César Hernández.

Re: [VOTE] TomEE 8.0.15

[Cesar Hernandez]

Reviewed latest CI builds, sanity checks and release notes.
+1, thank you!

El lun, 8 may 2023 a las 6:50, Richard Zowalla () escribió:

> Hi all,
>
> this is a vote for a release of Apache TomEE 8.0.15.
>
> It is a maintenance release with some bug fixes and dependencies
> upgrades (addressing some CVEs)
>
> ###
>
> Maven Repo:
> https://repository.apache.org/content/repositories/orgapachetomee-1214/
>
> 
> 
> tomee-8.0.15-rc1
> Testing TomEE 8.0.15 RC1
> 
> https://repository.apache.org/content/repositories/orgapachetomee-1214/
> 
> 
> 
>
> ###
>
> Binaries & Source:
>
> https://dist.apache.org/repos/dist/dev/tomee/staging-1214/tomee-8.0.15/
>
> ###
>
> Tag:
>
> https://github.com/apache/tomee/releases/tag/tomee-project-8.0.15
>
>
> ###
>
> Release notes:
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12352766
>
> ###
>
> Here is an adoc generated version of the changelog as well:
>
> == Dependency upgrade
>
> [.compact]
>  - link:https://issues.apache.org/jira/browse/TOMEE-4188[TOMEE-4188]
> ActiveMQ 5.16.6
>  - link:https://issues.apache.org/jira/browse/TOMEE-4180[TOMEE-4180]
> CXF 3.5.5
>  - link:https://issues.apache.org/jira/browse/TOMEE-4187[TOMEE-4187]
> Commons FileUpload 1.5
>  - link:https://issues.apache.org/jira/browse/TOMEE-4210[TOMEE-4210]
> EclipseLink 2.7.12
>  - link:https://issues.apache.org/jira/browse/TOMEE-4211[TOMEE-4211]
> Hibernate Integration 5.6.15.Final
>  - link:https://issues.apache.org/jira/browse/TOMEE-4206[TOMEE-4206]
> Jackson 2.15.0
>  - link:https://issues.apache.org/jira/browse/TOMEE-4207[TOMEE-4207]
> Johnzon 1.2.20
>  - link:https://issues.apache.org/jira/browse/TOMEE-4205[TOMEE-4205]
> Jose4j
> 
> 0.9.3
>  - link:https://issues.apache.org/jira/browse/TOMEE-4209[TOMEE-4209]
> Mojarra 2.3.19
>  - link:https://issues.apache.org/jira/browse/TOMEE-4195[TOMEE-4195]
> Tomcat 9.0.72 (CVE-2023-28708)
>  - link:https://issues.apache.org/jira/browse/TOMEE-4191[TOMEE-4191]
> Tomcat 9.0.73
>  - link:https://issues.apache.org/jira/browse/TOMEE-4201[TOMEE-4201]
> Tomcat 9.0.74
>  - link:https://issues.apache.org/jira/browse/TOMEE-4194[TOMEE-4194]
> snakeyaml version 2.0 mitigate CVE-2022-1471
>
> == Bug
>
> [.compact]
>  - link:https://issues.apache.org/jira/browse/TOMEE-4192[TOMEE-4192]
> ApplicationComposers do not clear GC references on release
>  - link:https://issues.apache.org/jira/browse/TOMEE-4181[TOMEE-4181]
> BCProv jar loses its signature during the patch process
>  - link:https://issues.apache.org/jira/browse/TOMEE-4122[TOMEE-4122]
> Performance Regression in bean resolution in EAR files
>  - link:https://issues.apache.org/jira/browse/TOMEE-4189[TOMEE-4189]
> java.lang.ClassNotFoundException:
> org.apache.openejb.loader.SystemInstance
>  - link:https://issues.apache.org/jira/browse/TOMEE-4179[TOMEE-4179]
> Fix creeping in API JARs which should be in javaee-api
>
> == Wish
>
> [.compact]
>  - link:https://issues.apache.org/jira/browse/TOMEE-4190[TOMEE-4190]
> RunWithApplicationComposer should support inheritance
>
> == Fixed Common Vulnerabilities and Exposures (CVEs)
>
> [.compact]
>  - link:https://issues.apache.org/jira/browse/TOMEE-4194[TOMEE-4194]
> Update snakeyaml version to 2.0 to mitigate CVE-2022-1471
>  - link:https://issues.apache.org/jira/browse/TOMEE-4195[TOMEE-4195]
> Upgrade to Apache Tomcat 9.0.72 (CVE-2023-28708)
>  - link:https://issues.apache.org/jira/browse/TOMEE-4187[TOMEE-4187]
> Commons FileUpload 1.5
>
>
> ###
>
> Here is the dependency diff from 8.0.14 to 8.0.15 created with our
> release tools:
>
>   artifactId  from  to
> ---  -
>  jackson-annotations 2.14.1   2.15.0
>  jackson-core2.14.1   2.15.0
>  jackson-databind2.14.1   2.15.0
>  jackson-dataformat-yaml 2.14.1   2.15.0
>  saaj-impl1.5.1   1.5.3
>  activemq-broker 5.16.5   5.16.6
>  activemq-client 5.16.5   5.16.6
>  activemq-jdbc-store 5.16.5   5.16.6
>  activemq-kahadb-store   5.16.5   5.16.6
>  activemq-openwire-legacy5.16.5   5.16.6
>  activemq-ra 5.16.5   5.16.6
>  cxf-rt-rs-mp-client 3.4.10   3.5.5
>  johnzon-core1.2.19   1.2.20
>  johnzon-jaxrs   1.2.19   1.2.20
>  johnzon-jsonb   1.2.19   1.2.20
>  johnzon-jsonp-strict1.2.19   1.2.20
>  johnzon-mapper  1.2.19   1.2.20
>  xmlsec   2.2.3   2.3.2
>  wss4j-bindings   2.3.3   2.4.1
>  wss4j-policy 2.3.3   2.4.1
>  wss4j-ws-security-common 2.3.3   2.4.1
>  wss4j-ws-security-dom2.3.3   2.4.1
>  wss4j-ws-security-policy-stax2.3.3   2.4.1
>  

Re: Release TomEE 8.0.15 ?

[Cesar Hernandez]

No objections, thanks Richard!

El mar, 2 may 2023 a las 7:03, Alex The Rocker ()
escribió:

> Yes please release TomEE 8.0.15 !
>
> Thanks,
> Alexandre
>
> Le mar. 2 mai 2023 à 14:47, Richard Zowalla  a écrit :
> >
> > Hi all,
> >
> > any objections in doing a 8.0.15?
> >
> > We have a few pending CVE fixes in 3rd party libs: [1].
> >
> > Or does anyone see any major blockers?
> >
> > Gruß
> > Richard
> >
> >
> > [1] https://issues.apache.org/jira/projects/TOMEE/versions/12352766
>


-- 
Atentamente:
César Hernández.

Re: Backporting changes between 8.x, 9.x and 10.x

[Cesar Hernandez]

Hi David,
Thank you for the follow-up, I created
https://issues.apache.org/jira/browse/TOMEE-4193 and
https://github.com/apache/tomee-site-generator/pull/61 for the eol pages.

El jue, 16 mar 2023 a las 13:22, David Blevins ()
escribió:

> We should maybe also create pages like this as they seem to come up in
> search engines nicely:
>
>  - https://tomcat.apache.org/tomcat-10.0-eol.html <
> https://tomcat.apache.org/tomcat-10.0-eol.html>
>  - https://tomcat.apache.org/tomcat-70-eol.html <
> https://tomcat.apache.org/tomcat-70-eol.html>
>
> Some kind of URL like this would be great:
>
>  - https://tomee.apache.org/tomee-8.0-eol.html <
> https://tomee.apache.org/tomee-8.0-eol.html>
>
> We probably also want to add a bullet to the TomEE 8 download section that
> then links to this page.
>
>
> -David
>
>
> > On Feb 16, 2023, at 8:23 AM, Cesar Hernandez 
> wrote:
> >
> > About the website message for discontinued branches, I created TOMEE-4186
> > for a proposal for the Download page that won't move (yet) the
> discontinued
> > versions to the archive but instead marked them as discontinued branches.
> >
> > As Richard mentioned, having the discontinued version on the actual
> > download page may create a false impression, so we can have two steps,
> > first make clear on the download page the branches that are discontinued,
> > and then after 3 or 6 months, we can move then to the archive section but
> > keeping the discontinued text in the same way many milestones releases
> has
> > the information on the archive page.
> >
> > El mié, 15 feb 2023 a las 2:54, Richard Zowalla ()
> > escribió:
> >
> >> Thanks for all the opionions and answers, so far. Here are my thoughts
> >> on the branches:
> >>
> >> ## TomEE 10.x
> >>
> >> Happy to help - currently, I have a bit of work to do for my $$-job,
> >> though, but hope to have some more time to work on it soon :-)
> >>
> >> ## TomEE 9.x
> >>
> >> I am fine to help maintaining this one for a short period of time
> >> (until we have some a 10.x release) and fixing bugs, etc. (like the
> >> *.exe issue yesterday).
> >>
> >> If we can't upgrade to Tomcat 10.1 without breaking the EE9.1 TCK, we
> >> would need to volunteer time in Tomcat to maintain 10.0.x, which they
> >> eol'ed a few months ago. I most likely won't have time for that as I
> >> would like to focus on EE10.
> >>
> >> ## TomEE 8.x
> >>
> >> I am fine with the proposed date / strategy regarding transient
> >> dependencies.
> >>
> >> Regarding CXF 3.5.x - I think, that it should be possible for EE8 to
> >> upgrade. I have a related PR, which is sufficient to have a green
> >> build, but don't know the TCK status for it [1].
> >>
> >> I am also happy to help maintain this branch until we have an EE10
> >> release ready.
> >>
> >> ## TomEE 1.7.x / 7.0.x / 7.1.x
> >>
> >> It seems, that we have an agreement on marking 1.7.x and 7.1.x / 7.0.x
> >> as discontinued. We currently have a note on the download page for these
> >> versions:
> >>
> >> "Note: TomEE 1.7.5 was released five years ago. New releases from this
> >> branch are unlikely, but we are open for contributors to step up and
> >> lead the efforts in fixing CVEs and updating dependencies."
> >>
> >> We might need to make it a bit more clear though. I like the idea by
> >> Jon to add a list of CVEs for each of the discontinued release lines.
> >> We could even move these artifacts to a separate download page (not
> >> archive!) and explicitly mention CVEs + unlikeliness of future
> >> releases, so there isn't a false impression on the actual downloadpage,
> >> that these artifacts are still maintained, etc.
> >>
> >>
> >> [1] https://github.com/apache/tomee/pull/1010
> >>
> >>
> >> Am Dienstag, dem 14.02.2023 um 10:58 -0600 schrieb Cesar Hernandez:
> >>> +1  working on maintaining  TomEE 9 branch since currently is the
> >>> only
> >>> option users have to migrate to Jakarta namespaces with a TomEE GA
> >>> version.
> >>>
> >>> +1 on TomEE 8 strategy to check transitive dependencies reaching EOL
> >>> to
> >>> analyze its life span.
> >>>
> >>> +1 on label TomEE 7.x and 1.7 as discontinued.
> >>>
> >>>
> >>>
> >>>
> &g

Re: Backporting changes between 8.x, 9.x and 10.x

[Cesar Hernandez]

About the website message for discontinued branches, I created TOMEE-4186
for a proposal for the Download page that won't move (yet) the discontinued
versions to the archive but instead marked them as discontinued branches.

As Richard mentioned, having the discontinued version on the actual
download page may create a false impression, so we can have two steps,
first make clear on the download page the branches that are discontinued,
and then after 3 or 6 months, we can move then to the archive section but
keeping the discontinued text in the same way many milestones releases has
the information on the archive page.

El mié, 15 feb 2023 a las 2:54, Richard Zowalla ()
escribió:

> Thanks for all the opionions and answers, so far. Here are my thoughts
> on the branches:
>
> ## TomEE 10.x
>
> Happy to help - currently, I have a bit of work to do for my $$-job,
> though, but hope to have some more time to work on it soon :-)
>
> ## TomEE 9.x
>
> I am fine to help maintaining this one for a short period of time
> (until we have some a 10.x release) and fixing bugs, etc. (like the
> *.exe issue yesterday).
>
> If we can't upgrade to Tomcat 10.1 without breaking the EE9.1 TCK, we
> would need to volunteer time in Tomcat to maintain 10.0.x, which they
> eol'ed a few months ago. I most likely won't have time for that as I
> would like to focus on EE10.
>
> ## TomEE 8.x
>
> I am fine with the proposed date / strategy regarding transient
> dependencies.
>
> Regarding CXF 3.5.x - I think, that it should be possible for EE8 to
> upgrade. I have a related PR, which is sufficient to have a green
> build, but don't know the TCK status for it [1].
>
> I am also happy to help maintain this branch until we have an EE10
> release ready.
>
> ## TomEE 1.7.x / 7.0.x / 7.1.x
>
> It seems, that we have an agreement on marking 1.7.x and 7.1.x / 7.0.x
> as discontinued. We currently have a note on the download page for these
> versions:
>
> "Note: TomEE 1.7.5 was released five years ago. New releases from this
> branch are unlikely, but we are open for contributors to step up and
> lead the efforts in fixing CVEs and updating dependencies."
>
> We might need to make it a bit more clear though. I like the idea by
> Jon to add a list of CVEs for each of the discontinued release lines.
> We could even move these artifacts to a separate download page (not
> archive!) and explicitly mention CVEs + unlikeliness of future
> releases, so there isn't a false impression on the actual downloadpage,
> that these artifacts are still maintained, etc.
>
>
> [1] https://github.com/apache/tomee/pull/1010
>
>
> Am Dienstag, dem 14.02.2023 um 10:58 -0600 schrieb Cesar Hernandez:
> > +1  working on maintaining  TomEE 9 branch since currently is the
> > only
> > option users have to migrate to Jakarta namespaces with a TomEE GA
> > version.
> >
> > +1 on TomEE 8 strategy to check transitive dependencies reaching EOL
> > to
> > analyze its life span.
> >
> > +1 on label TomEE 7.x and 1.7 as discontinued.
> >
> >
> >
> >
> >
> >
> >
> >
> > El mar, 14 feb 2023 a las 5:03, Jonathan Gallimore (<
> > jonathan.gallim...@gmail.com>) escribió:
> >
> > > I very much agree with specifying where you're willing to spend
> > > your time,
> > > as opposed to just what you'd like to see.
> > >
> > > - TomEE 10: I'm happy to contribute to the development of that as I
> > > can.
> > > I'm currently working on the concurrency changes needed for EE10.
> > > - TomEE 9: I'm happy to contribute towards maintaining this until a
> > > little
> > > after TomEE 10 is released. If we discontinued this now, I think
> > > users
> > > would potentially avoid actually doing their migration from javax
> > > to
> > > jakarta. I don't see any way we can discontinue this until there is
> > > a GA
> > > TomEE 10 release.
> > > - TomEE 8: I agree we need to determine what its lifespan is, and
> > > this is
> > > to a certain extent determined by all of the components we use. I
> > > suspect
> > > CXF may be tricky in this area - as 3.4.10 is the last 3.4 release,
> > > and I'm
> > > not sure what is involved in 3.5.x or it is suitable for EE8 etc.
> > > If we
> > > don't determine a lifespan for TomEE 8, there's a real danger that
> > > people
> > > will try and stick with it forever rather than migrate to newer
> > > versions.
> > > I'd be happy to help maintain this branch for a short time
> > > - Older branches: I wouldn'

Re: PR builds in TomEE

[Cesar Hernandez]

@Richard
I raise the question on apache infra, and there is no plan to automatically
build PRs from non-committers on the on-demand CI infra. This for security
reasons as currently implemented in the current CI infra.

@Swell,
Thank you for including the github actions for PR on 9.x branch.
I included the jenkins job creation for branch 9.x via TOMEE-4178 too.





El mar, 31 ene 2023 a las 6:59, Swell () escribió:

> about PR builds in GitHub
>
> i saw there is:
> * no GitHub actions for Pull Requests on *branch 9.x* (code in main branch)
> * inversions of PR and non PR keys for the GitHub cache on *branch main*
>
> i have a PR ready if both needed.
>
> --
> Swell
>
> On Tue, 31 Jan 2023 at 00:32, Cesar Hernandez 
> wrote:
>
> > Thank you for the update Richard, I was not aware that Jenkins jobs have
> > the same restriction Github Actions has about not building PR's from
> > non-committers.
> > Indeed I have met with the INFRA team, and I'll raise these questions
> about
> > non-committers PR's.
> >
> > El lun, 30 ene 2023 a las 7:27, Richard Zowalla ()
> > escribió:
> >
> > > Hi all,
> > >
> > > the topic appeared a few times on the list. Short summary to remember:
> > >
> > > Currently, we cannot automatically build PRs from non committers due to
> > > ASF restrictions on Jenkins. INFRA (and I think Cesar?) is working on
> > > better build nodes (ephermal runners on AWS) to improve Jenkins
> > > performance and reduce the risk for security issues originating from
> > > PRs.
> > >
> > > At the moment I (most of the time) manually created jobs to get some
> > > feedback on PRs. To avoid that manual step, I created two parameterized
> > > jobs:
> > >
> > > - Java 8:
> > > https://ci-builds.apache.org/job/Tomee/job/pull-request-8.x-manual/
> > > - Java 11:
> > > https://ci-builds.apache.org/job/Tomee/job/pull-request-manual/
> > >
> > > They can be (manually triggered by any TomEE committer) either on the
> > > TomEE GitHub repo itself or on any fork. The branch is also a
> > > parameter. I think, that the security concern (from INFRA) is ok here
> > > as a build isn't triggered automatically and requires committer
> > > intervention to actually run.
> > >
> > > Happy building.
> > >
> > > Gruß
> > > Richard
> > >
> >
> >
> > --
> > Atentamente:
> > César Hernández.
> >
>


-- 
Atentamente:
César Hernández.

Re: Backporting changes between 8.x, 9.x and 10.x

[Cesar Hernandez]

+1  working on maintaining  TomEE 9 branch since currently is the only
option users have to migrate to Jakarta namespaces with a TomEE GA version.

+1 on TomEE 8 strategy to check transitive dependencies reaching EOL to
analyze its life span.

+1 on label TomEE 7.x and 1.7 as discontinued.








El mar, 14 feb 2023 a las 5:03, Jonathan Gallimore (<
jonathan.gallim...@gmail.com>) escribió:

> I very much agree with specifying where you're willing to spend your time,
> as opposed to just what you'd like to see.
>
> - TomEE 10: I'm happy to contribute to the development of that as I can.
> I'm currently working on the concurrency changes needed for EE10.
> - TomEE 9: I'm happy to contribute towards maintaining this until a little
> after TomEE 10 is released. If we discontinued this now, I think users
> would potentially avoid actually doing their migration from javax to
> jakarta. I don't see any way we can discontinue this until there is a GA
> TomEE 10 release.
> - TomEE 8: I agree we need to determine what its lifespan is, and this is
> to a certain extent determined by all of the components we use. I suspect
> CXF may be tricky in this area - as 3.4.10 is the last 3.4 release, and I'm
> not sure what is involved in 3.5.x or it is suitable for EE8 etc. If we
> don't determine a lifespan for TomEE 8, there's a real danger that people
> will try and stick with it forever rather than migrate to newer versions.
> I'd be happy to help maintain this branch for a short time
> - Older branches: I wouldn't want to contribute to these any more, and
> would be in favor of marking them as discontinued.
>
> The EOL policy you've suggested is really clear, and I think it strikes a
> reasonable balance with what's achievable from a maintenance perspective,
> while giving time for users to upgrade. While I don't necessarily object to
> releases from older branches, if there was a strong desire to do so, I do
> think the responsible thing to do is clearly list every single CVE in each
> library that hasn't been patched on the download page. I personally
> strongly prefer the policy of not releasing software where there are CVEs
> in any of the components, however.
>
> Jon
>
> On Wed, Feb 8, 2023 at 8:07 PM David Blevins 
> wrote:
>
> > Great thread to start, Richard!
> >
> > My request to everyone who responds: please be clear on where you’re
> > willing to spend your time.  If we get a lot of +1s for an option, but
> not
> > enough people actually volunteering to do the work, it really isn’t an
> > option.
> >
> > Here’s my perspective on each branch:
> >
> >  - TomEE 9.  We need to keep that CVE patched and actively released.  If
> > we don’t then people on TomEE 8 looking to migrate away won’t actually
> have
> > a safe place to migrate to.  I’d be willing to put contribution time into
> > CVE patches and doing or reviewing releases on TomEE 9 till TomEE 10 is
> > released + 6 months so people have time to migrate from 9 to 10.  We
> would
> > either need to upgrade to Tomcat 10.1 to make this work or volunteer time
> > in Tomcat to maintaining 10.
> >
> >  - TomEE 8.  I’d be willing to review patches, help with release
> releases,
> > etc for this year, so people have time to migrate.  As it will negatively
> > impact our TomEE 10 work and people will mostly likely not take advantage
> > unless forced, I’d want to have a clear end-of-life date that we set now.
> > I think Dec 31st, 2023 is a good date.  That date would be communicated
> as
> > best effort — if a dependency like say CXF stops maintaining the version
> we
> > need, the actual end of life date for TomEE 8 would be shorter.  This
> would
> > all have to be documented and visible when people download TomEE 8.  I
> > wouldn’t be willing to put time into TomEE 8 open-ended, without an
> agreed
> > end-of-life date.  Not as critical, but we might also be smart to do just
> > one release a quarter or something to minimize impact.
> >
> >  - TomEE 7 & TomEE 1.7.  These are already effectively discontinued.  I
> > think we should actually label them discontinued.  I definitely would not
> > be willing to review patches or release binaries for those branches.
> >
> >
> > # General End-of-life policy thoughts
> >
> > I had in the past leaned against officially calling a branch
> discontinued,
> > but I think I’m swayed the other way on that.  Nobody wants to do the
> > javax-to-jakarta transition and given the opportunity to put it off,
> > everyone will.  In my experience, people don’t like to upgrade even when
> > there are no breaking changes — the fear of one being hidden in there
> > somewhere is enough to stop a lot of people.  In absence of a clear “this
> > is going away” date, a lot of people will either hold off upgrading or
> not
> > be able to get the internal support for doing an upgrade.
> >
> > If I had to take a stab at a default end-of-life policy, I’d probably
> > recommend something like this:
> >
> >  - We maintain the latest stable (final) 

Re: PR builds in TomEE

[Cesar Hernandez]

Thank you for the update Richard, I was not aware that Jenkins jobs have
the same restriction Github Actions has about not building PR's from
non-committers.
Indeed I have met with the INFRA team, and I'll raise these questions about
non-committers PR's.

El lun, 30 ene 2023 a las 7:27, Richard Zowalla ()
escribió:

> Hi all,
>
> the topic appeared a few times on the list. Short summary to remember:
>
> Currently, we cannot automatically build PRs from non committers due to
> ASF restrictions on Jenkins. INFRA (and I think Cesar?) is working on
> better build nodes (ephermal runners on AWS) to improve Jenkins
> performance and reduce the risk for security issues originating from
> PRs.
>
> At the moment I (most of the time) manually created jobs to get some
> feedback on PRs. To avoid that manual step, I created two parameterized
> jobs:
>
> - Java 8:
> https://ci-builds.apache.org/job/Tomee/job/pull-request-8.x-manual/
> - Java 11:
> https://ci-builds.apache.org/job/Tomee/job/pull-request-manual/
>
> They can be (manually triggered by any TomEE committer) either on the
> TomEE GitHub repo itself or on any fork. The branch is also a
> parameter. I think, that the security concern (from INFRA) is ok here
> as a build isn't triggered automatically and requires committer
> intervention to actually run.
>
> Happy building.
>
> Gruß
> Richard
>


-- 
Atentamente:
César Hernández.

Re: Post TomEE 9.0.0 final release

[Cesar Hernandez]

Hi Jean-Louis,

About:

- create jobs for TomEE 9.x maintenance


I created https://issues.apache.org/jira/browse/TOMEE-4178 and left some
questions to understand better the amount of jobs we finally need for the
9.x branch.

El mié, 18 ene 2023 a las 14:22, Zoltán Tichov ()
escribió:

> Hi David!
>
> Ok, but eg. the JsonB TCK is more or less in one jar file and at Jakarta
> TCK is not that case.
> So I think I cannot put the whole Faces TCK in one jar to include as a
> dependency. Or I put the whole faces tck
> in the tomee/tck?
>
> Thanks:
> Zoltán
>
>
> On Wed, Jan 18, 2023 at 8:46 PM David Blevins 
> wrote:
>
> > Hi Zoltán!
> >
> > > On Jan 18, 2023, at 11:31 AM, Zoltán Tichov 
> > wrote:
> > >
> > > Hi!
> > >
> > > I examined the Jakarta Faces TCK and it appears that the setup could be
> > > done in the same way as tomee-tck is.
> > > But I don't know if it could merge the two TCK or the faces TCK should
> > be a
> > > separate project.
> > > Which direction should I go?
> >
> > All the other standalone TCKs are currently setup here:
> >
> > - https://github.com/apache/tomee/tree/main/tck
> >
> > Here’s a couple similar PRs to use as reference:
> >
> >  - https://github.com/apache/tomee/pull/1004
> >  - https://github.com/apache/tomee/pull/1003
> >  - https://github.com/apache/tomee/pull/1002
> >
> > We may split those out at some point, but that’s where things seem to be
> > going for now.
> >
> >
> > -David
> >
> > > On Thu, Jan 12, 2023 at 12:47 PM Jonathan Gallimore <
> > > jonathan.gallim...@gmail.com> wrote:
> > >
> > >> I've started wiring up the Concurrency TCK here:
> > >> https://github.com/apache/tomee/tree/TOMEE-4159_Concurrency_TCK.
> After
> > >> updating the Jakarta EE API to 10, there are some compile issues,
> > >> particularly around the concurrency area, so there is some work to do
> > >> (which I'm looking at now!).
> > >>
> > >> Cheers
> > >>
> > >> Jon
> > >>
> > >> On Thu, Jan 12, 2023 at 11:41 AM Jean-Louis Monteiro <
> > >> jlmonte...@tomitribe.com> wrote:
> > >>
> > >>> I saw some commits. Thanks for the setup and the work.
> > >>> We have a couple of pending PRs ready for the different TCK (BVal,
> CDI,
> > >>> JSONB, JSONP, Concurrent).
> > >>>
> > >>> The challenge with standalone TCK is that if we don't find a way to
> run
> > >>> them on the cloud, we'll need to consolidate the results between the
> 2
> > >>> platforms. It will be definitely slower on the Apache CI system and
> > will
> > >>> make the build unbelievably slow.
> > >>>
> > >>> We have some investment there. We can of course run in the cloud with
> > >> `mvn
> > >>> verify -pl tck/bval-tomee` etc. But how are we going to collect the
> > >>> results? Furthermore for CDI and others, it would be great to split
> > into
> > >>> smaller chunks to run in parallel.
> > >>>
> > >>>
> > >>> Long story short, there is some good investment to have on this area.
> > It
> > >>> will definitely pay off in the long run.
> > >>>
> > >>> --
> > >>> Jean-Louis Monteiro
> > >>> http://twitter.com/jlouismonteiro
> > >>> http://www.tomitribe.com
> > >>>
> > >>>
> > >>> On Thu, Jan 12, 2023 at 2:54 AM David Blevins <
> david.blev...@gmail.com
> > >
> > >>> wrote:
> > >>>
> > > On Jan 4, 2023, at 4:00 PM, David Blevins  >
> >  wrote:
> > >
> > > I created JIRAs for all the individual TCKs involved in EE 10.
> Some
> > >> of
> >  these are already setup:
> > >
> > > TOMEE-4156   Platform/WebProfile TCK
> > 
> >  I have this at least minimally setup here:
> > 
> >  - https://github.com/apache/tomee-tck
> > 
> >  There’s a `setup.sh` that will download and install the Jakarta EE
> 10
> >  Platform & Web Profile TCK on your machine.
> > 
> >  General FYI on some tweaks I made to the branches.
> > 
> >  - main: now points to TomEE 10 instead of TomEE 8
> >  - tomee-8.x: new branch made from the former `main` branch,
> dedicated
> > >> to
> >  TomEE 8
> >  - tomee-8.x: new branch made from the `jakartaee9-tck` branch,
> > >> dedicated
> >  to TomEE 9
> > 
> >  Next steps for me will be trying to get a run or two going up in the
> > >>> cloud
> >  so we have some base numbers.  Quite a lot of the tests were moved
> out
> > >> to
> >  standalone TCKs, so there’ll some work to get a good view of how
> > things
> >  compare.
> > 
> > 
> >  -David
> > 
> > 
> > >>>
> > >>
> >
> >
>


-- 
Atentamente:
César Hernández.

Re: [VOTE] TomEE 8.0.14

[Cesar Hernandez]

+1 (binding).
Thank you!

El mar, 17 ene 2023 a las 16:36, Jean-Louis Monteiro (<
jlmonte...@tomitribe.com>) escribió:

> +1 (binding)
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Tue, Jan 17, 2023 at 4:31 PM Thomas Andraschko <
> andraschko.tho...@gmail.com> wrote:
>
> > +1 (non-binding)
> > our applications are working fine
> >
> > Am Di., 17. Jan. 2023 um 14:49 Uhr schrieb Daniel Dias Dos Santos <
> > daniel.dias.analist...@gmail.com>:
> >
> > > Hello,
> > >
> > > +1
> > >
> > > Thanks
> > >
> > > On Tue, Jan 17, 2023, 10:40 Richard Zowalla  wrote:
> > >
> > > > Hi all,
> > > >
> > > > this is a vote for a release of Apache TomEE 8.0.14.
> > > >
> > > > It is a maintenance release with some bug fixes and dependencies
> > > > upgrades.
> > > >
> > > > ###
> > > >
> > > > Maven Repo:
> > > >
> > https://repository.apache.org/content/repositories/orgapachetomee-1213/
> > > >
> > > > 
> > > > 
> > > > tomee-8.0.14-release-test
> > > > Testing TomEE 8.0.14 release candidate
> > > > 
> > > >
> > https://repository.apache.org/content/repositories/orgapachetomee-1213/
> > > > 
> > > > 
> > > > 
> > > >
> > > > ###
> > > >
> > > > Binaries & Source:
> > > >
> > > >
> > https://dist.apache.org/repos/dist/dev/tomee/staging-1213/tomee-8.0.14/
> > > >
> > > > ###
> > > >
> > > > Tag:
> > > >
> > > > https://github.com/apache/tomee/releases/tag/tomee-project-8.0.14
> > > >
> > > >
> > > > ###
> > > >
> > > > Release notes:
> > > >
> > > > https://issues.apache.org/jira/projects/TOMEE/versions/12352390
> > > >
> > > > ###
> > > >
> > > > Here is an adoc generated version of the changelog as well:
> > > >
> > > > == Dependency upgrade
> > > >
> > > > [.compact]
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4100[TOMEE-4100]
> > > > XBean 4.22
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4126[TOMEE-4126]
> > > > CXF 3.4.10
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4118[TOMEE-4118]
> > > > CXF 3.4.9
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4125[TOMEE-4125]
> > > > CXF versions mitigate CVE-2022-46364 and CVE-2022-46363
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4086[TOMEE-4086]
> > > > HSQLDB 2.7.1
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4170[TOMEE-4170]
> > > > Hibernate 5.6.14
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4107[TOMEE-4107]
> > > > Jackson 2.14.0
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4129[TOMEE-4129]
> > > > Jackson 2.14.1
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4169[TOMEE-4169]
> > > > SnakeYAML - CVE-2022-1471
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4116[TOMEE-4116]
> > > > Tomcat 9.0.69
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4121[TOMEE-4121]
> > > > Tomcat 9.0.70
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4173[TOMEE-4173]
> > > > Tomcat 9.0.71
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4109[TOMEE-4109]
> > > > Velocity 2.3
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4110[TOMEE-4110]
> > > > Woodstox 6.4.0 (CVE-2022-40152)
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4111[TOMEE-4111]
> > > > bcel component
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4130[TOMEE-4130]
> > > > commons-compress
> > > > <
> > >
> >
> https://issues.apache.org/jira/browse/TOMEE-4130%5BTOMEE-4130%5Dcommons-compress
> > > >
> > > > 1.22
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4094[TOMEE-4094]
> > > > jackson 2.14.0-rc2
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4103[TOMEE-4103]
> > > > woodstox-core
> > > > <
> > >
> >
> https://issues.apache.org/jira/browse/TOMEE-4103%5BTOMEE-4103%5Dwoodstox-core
> > > >
> > > > mitigate CVE-2022-40153
> > > >
> > > > == Bug
> > > >
> > > > [.compact]
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4120[TOMEE-4120]
> > > > Remote EJB2 BMP Memory Leak
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4122[TOMEE-4122]
> > > > Performance Regression in bean resolution in EAR files
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4101[TOMEE-4101]
> > > > Typo with EL22Adaptor implementation in openwebbeans.properties
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4102[TOMEE-4102]
> > > > TomEE logs SEVERE: Expected ContextBinding to have the method
> > > > getThreadName()
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4106[TOMEE-4106]
> > > > TomEE version no longer appearing at default manager page
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4014[TOMEE-4014]
> > > > Unable to see TomEE version in Tomcat home page with Java 17
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4108[TOMEE-4108]
> > > > Backport TOMEE-4065: LoginToContinue interceptor fails on custom auth
> > > > mechanism
> 

Re: [VOTE] Apache TomEE Patch Plugin 0.10

[Cesar Hernandez]

+1

On Wed, Jan 4, 2023 at 5:48 PM David Blevins 
wrote:

> +1
>
> -David
>
>
> > On Jan 2, 2023, at 3:31 AM, Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
> >
> > Hi,
> >
> > I'd like to vote Apache TomEE Patch Plugin 0.10 up for vote. The changes
> > are fairly minimal and consist of patching the source jar so that IDE
> isn't
> > lost. This release is required so we can then quickly push 9.0.0 final.
> >
> > Changes:
> >
> > - TOMEE-4136 Support sources patching
> >
> > Sources:
> >
> >
> https://dist.apache.org/repos/dist/dev/tomee/tomee-patch-plugin_staging-1209/
> >
> > Staging Nexus Repository:
> >
> > https://repository.apache.org/content/repositories/orgapachetomee-1209
> >
> > Tag:
> >
> >
> https://github.com/apache/tomee-patch-plugin/tree/tomee-patch-parent-0.10
> >
> > Please vote to approve this release:
> > [ ] +1 Approve the release
> > [ ] -1 Don't approve the release (please provide specific comments)
> >
> > This vote will be open for at least 72 hours.
> >
> > Jean-Louis
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
>
> --
Atentamente:
César Hernández.

Re: [VOTE] Apache TomEE 9.0.0

[Cesar Hernandez]

+1 binding.
Thank you all!

On Wed, Jan 4, 2023 at 5:25 AM Thomas Andraschko <
andraschko.tho...@gmail.com> wrote:

> +1 (non-binding)
>
> Am Mi., 4. Jan. 2023 um 12:17 Uhr schrieb Richard Zowalla  >:
>
> > +1 (binding)
> >
> > Am Mittwoch, dem 04.01.2023 um 12:15 +0100 schrieb Jean-Louis Monteiro:
> > > My own +1
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
> > >
> > >
> > > On Wed, Jan 4, 2023 at 12:14 PM Martin Wiesner 
> > > wrote:
> > >
> > > > +1 (non-binding)
> > > >
> > > > Best
> > > > Martin
> > > >
> > > >
> > > > On 2023/01/03 09:53:20 Jean-Louis Monteiro wrote:
> > > > > Hi all,
> > > > >
> > > > > I'm very proud to call a vote for Apache TomEE 9.0.0 final. It's
> > > > > been
> > > > > almost a year since we certified the server using a bytecode
> > > > > enhancement
> > > > > approach. Even though it worked, it introduced a lot of
> > > > > restrictions
> > > > > especially with tooling (IDE, Arquillian, Embedded container,
> > > > > etc).
> > > > >
> > > > > We started migrating the entire server to the new jakarta
> > > > > namespace and
> > > > the
> > > > > 9.0.0 final is the result of such work. We fully passed the
> > > > > entire TCK
> > > > for
> > > > > Jakarta EE 9.1 and cherry on the cake, we decided to address a
> > > > > long time
> > > > > request to support a newer version of MicroProfile. So I'm
> > > > > pleased to
> > > > also
> > > > > announce that this version is fully MicroProfile 5.0 compliant.
> > > > >
> > > > > - Sources
> > > > > https://dist.apache.org/repos/dist/dev/tomee/tomee_staging-1210/
> > > > >
> > > > > - Maven staging repository
> > > > >
> > https://repository.apache.org/content/repositories/orgapachetomee-1210
> > > > >
> > > > > - Signing keys
> > > > > https://dist.apache.org/repos/dist/release/tomee/KEYS
> > > > >
> > > > > - Changelog since last milestone
> > > > >
> > > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12350136
> > > > > Sub-task
> > > > >
> > > > >- [TOMEE-3883 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-3883>;] -
> > > > >Update example 'mvc-resteasy' to use Server/API Bom - master
> > > > > branch
> > > > >- [TOMEE-3950 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-3950>;] -
> > > > >Support for JWT token cookies
> > > > >- [TOMEE-3951 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-3951>;] -
> > > > JWT
> > > > >token groups claim is now optional
> > > > >- [TOMEE-3952 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-3952>;] -
> > > > >Deprecate RSA keys of 1024 bit length
> > > > >
> > > > > Bug
> > > > >
> > > > >- [TOMEE-4065 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-4065>;] -
> > > > >LoginToContinue interceptor fails on custom auth mechanism
> > > > >- [TOMEE-4117 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-4117>;] -
> > > > >MicroProfile OpenAPI not generating model
> > > > >- [TOMEE-4119 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-4119>;] -
> > > > >TomEEJsonbProvider triggered for */* mime types
> > > > >- [TOMEE-4135 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-4135>;] -
> > > > >Unable to see TomEE version in Tomcat home page with Java 17
> > > > >
> > > > > New Feature
> > > > >
> > > > >- [TOMEE-3946 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-3946>;] -
> > > > >MicroProfile JWT 2.0
> > > > >- [TOMEE-4050 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-4050>;] -
> > > > >Retry and Refresh for MP JWT keys supplied via HTTP
> > > > >- [TOMEE-4068 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-4068>;] -
> > > > >MicroProfile 5.0
> > > > >- [TOMEE-4069 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-4069>;] -
> > > > >MicroProfile Config 3.0
> > > > >- [TOMEE-4070 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-4070>;] -
> > > > >MicroProfile Fault Tolerance 4.0
> > > > >- [TOMEE-4071 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-4071>;] -
> > > > >MicroProfile Health 4.0
> > > > >- [TOMEE-4072 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-4072>;] -
> > > > >MicroProfile Metrics 4.0
> > > > >- [TOMEE-4073 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-4073>;] -
> > > > >MicroProfile Rest Client 3.0
> > > > >- [TOMEE-4074 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-4074>;] -
> > > > >MicroProfile OpenAPI 3.0
> > > > >- [TOMEE-4075 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-4075>;] -
> > > > >MicroProfile OpenTracing 3.0
> > > > >- [TOMEE-4076 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-4076>;] -
> > > > >Public Keys in OpenSSH format
> > > > >- [TOMEE-4077 <
> > > > > https://issues.apache.org/jira/browse/TOMEE-4077>;] -
> > > > >Public Keys in SSH2 format
> > > > >- 

Re: [VOTE] Apache TomEE 9.0.0.RC1 - staging repo 1208

[Cesar Hernandez]

+1 (binding)
Thank you !
On Tue, Nov 1, 2022 at 17:26 Jean-Louis Monteiro 
wrote:

> my own +1 (binding)
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Tue, Nov 1, 2022 at 6:07 PM David Blevins 
> wrote:
>
> > Looks good.
> >
> > +1
> >
> > Thanks for putting this release together!
> >
> >
> > -David
> >
> >
> > > On Oct 31, 2022, at 3:06 AM, Jean-Louis Monteiro <
> > jlmonte...@tomitribe.com> wrote:
> > >
> > > Hi all,
> > >
> > > As discussed, here is the vote for Apache TomEE 9.0.0.RC1. This is a
> > > release candidate implementing Jakarta EE 9.1 and MicroProfile 5. It is
> > > fully passing MicroProfile 5 TCK and only has a few failures for
> Jakarta
> > > TCK, hence the release candidate.
> > >
> > > This is a jakarta namespace compatible version. And it will result in a
> > > final version as soon as we can get the few TCK failures fixed.
> > >
> > > Binaries and sources
> > > https://dist.apache.org/repos/dist/dev/tomee/staging-1208/
> > >
> > > Staging repository
> > > https://repository.apache.org/content/repositories/orgapachetomee-1208
> > >
> > > CI last green build
> > > https://ci-builds.apache.org/job/Tomee/job/master-build-full/797/
> > >
> > > Releases notes
> > > = Apache TomEE 9.0.0.RC1 Release Notes
> > > :index-group: Release Notes
> > > :jbake-type: page
> > > :jbake-status: published
> > >
> > > == Dependency upgrade
> > >
> > > [.compact]
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4100[TOMEE-4100]
> > XBean
> > > 4.22
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4083[TOMEE-4083]
> > > Commons CLI 1.5.0
> > > - link:https://issues.apache.org/jira/browse/TOMEE-3800[TOMEE-3800]
> DBCP
> > > 2.9.0
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4037[TOMEE-4037]
> > > Eclipse Mojarra 3.0.2
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4036[TOMEE-4036]
> > > EclipseLink 3.0.3
> > > - link:https://issues.apache.org/jira/browse/TOMEE-3980[TOMEE-3980]
> > HSQLDB
> > > 2.7.0
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4019[TOMEE-4019]
> > HSQLDB
> > > 2.7.0
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4086[TOMEE-4086]
> > HSQLDB
> > > 2.7.1
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4039[TOMEE-4039]
> > > Hibernate 6.1
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4093[TOMEE-4093]
> > > Hibernate 6.1.4.Final
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4038[TOMEE-4038]
> > > Jackson 2.13.4
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4026[TOMEE-4026]
> > > Johnzon 1.2.19
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4030[TOMEE-4030]
> > Log4J2
> > > 2.18.0
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4097[TOMEE-4097]
> > > MicroProfile Fault Tolerance API 4.0.2
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4098[TOMEE-4098]
> > > MicroProfile Health API 4.0.1
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4099[TOMEE-4099]
> > > MicroProfile Rest Client API 3.0.1
> > > - link:https://issues.apache.org/jira/browse/TOMEE-3999[TOMEE-3999]
> > > MyFaces 3.0.2
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4054[TOMEE-4054]
> > > Snakeyaml 1.33
> > > - link:https://issues.apache.org/jira/browse/TOMEE-3831[TOMEE-3831]
> > TomEE
> > > should support library asm9.1 support fully Java 17
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4040[TOMEE-4040]
> > Tomcat
> > > 10.0.23
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4096[TOMEE-4096]
> > Tomcat
> > > 10.0.27
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4018[TOMEE-4018]
> > > bcprov-jdk15on 1.70
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4006[TOMEE-4006]
> > slf4j
> > > 1.7.36
> > >
> > > == Bug
> > >
> > > [.compact]
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4101[TOMEE-4101]
> Typo
> > > with EL22Adaptor implementation in openwebbeans.properties
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4102[TOMEE-4102]
> > TomEE
> > > logs SEVERE: Expected ContextBinding to have the method getThreadName()
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4032[TOMEE-4032]
> > Class
> > > cast Exception when undeploying application with @PostConstruct
> LifeCycle
> > > - link:https://issues.apache.org/jira/browse/TOMEE-3795[TOMEE-3795]
> > Proxy
> > > class definition does not work in Java 17+
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4014[TOMEE-4014]
> > Unable
> > > to see TomEE version in Tomcat home page with Java 17
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4041[TOMEE-4041] 4
> > CVE
> > > Vulnerabilities in snakeyaml-1.30.jar
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4001[TOMEE-4001]
> > > CVE-2022-34305 displaying user provided data without filtering,
> exposing
> > a
> > > XSS vulnerability
> > >
> > > == Task
> > >
> > > [.compact]
> > > - link:https://issues.apache.org/jira/browse/TOMEE-4022[TOMEE-4022]
> 

Re: [VOTE] Apache TomEE 8.0.13 - First Attempt

[Cesar Hernandez]

+1  (binding)
Thank you all!

On Sun, Oct 23, 2022 at 12:34 Jean-Louis Monteiro 
wrote:

> Sorry for the delay Richard. The weekend was a bit busy.
>
> +1 (binding)
> Tested quickly and looked at the packages
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Sun, Oct 23, 2022 at 3:33 PM Daniel Dias Dos Santos <
> daniel.dias.analist...@gmail.com> wrote:
>
> > Hi,
> >
> > +1
> >
> > Thanks
> >
> > On Sun, Oct 23, 2022, 08:29 Richard Zowalla  wrote:
> >
> > > Any more votes?
> > >
> > > Am Dienstag, dem 11.10.2022 um 19:59 +0200 schrieb Richard Zowalla:
> > > > Hi all,
> > > >
> > > > this is a first attempt at a vote for a release of Apache TomEE
> > > > 8.0.13.
> > > >
> > > > It is a maintenance release with some bug fixes and dependencies
> > > > upgrades.
> > > >
> > > > ###
> > > >
> > > > Maven Repo:
> > > >
> https://repository.apache.org/content/repositories/orgapachetomee-1207
> > > >
> > > >   
> > > > 
> > > >   tomee-8.0.13-release-test
> > > >   Testing TomEE 8.0.13 release candidate
> > > > 
> > > >
> https://repository.apache.org/content/repositories/orgapachetomee-1207
> > > > 
> > > > 
> > > >   
> > > >
> > > > ###
> > > >
> > > > Binaries & Source:
> > > >
> > > >
> > https://dist.apache.org/repos/dist/dev/tomee/staging-1207/tomee-8.0.13/
> > > >
> > > > ###
> > > >
> > > > Tag:
> > > >
> > > > https://github.com/apache/tomee/releases/tag/tomee-project-8.0.13
> > > >
> > > > ###
> > > >
> > > > Latest CI/CD build:
> > > >
> > > > https://ci-builds.apache.org/job/Tomee/job/tomee-8.x-build-full/226/
> > > >
> > > > ###
> > > >
> > > > Release notes:
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12351820
> > > >
> > > > ###
> > > >
> > > > Here is an adoc generated version of the changelog as well:
> > > >
> > > > == Dependency upgrade
> > > >
> > > > [.compact]
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-3985[TOMEE-3985]
> > > > BatchEE 1.0.2
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4057[TOMEE-4057]
> > > > CXF 3.4.8
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-3800[TOMEE-3800]
> > > > DBCP 2.9.0
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4059[TOMEE-4059]
> > > > EclipseLink 2.7.11
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4063[TOMEE-4063]
> > > > Geronimo Transaction Manager 3.1.5
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4019[TOMEE-4019]
> > > > HSQLDB 2.7.0
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-3986[TOMEE-3986]
> > > > Hibernate Integration 5.6.9.Final
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4042[TOMEE-4042]
> > > > Jackson 2.13.4
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4067[TOMEE-4067]
> > > > Jackson 2.14.0-rc1
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4020[TOMEE-4020]
> > > > Jakarta Faces 2.3.18
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4026[TOMEE-4026]
> > > > Johnzon 1.2.19
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4030[TOMEE-4030]
> > > > Log4J2 2.18.0
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-3998[TOMEE-3998]
> > > > MyFaces 2.3.10
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4044[TOMEE-4044]
> > > > Snakeyaml 1.32
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4054[TOMEE-4054]
> > > > Snakeyaml 1.33
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4002[TOMEE-4002]
> > > > Tomcat 9.0.64
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4051[TOMEE-4051]
> > > > Tomcat 9.0.65
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4060[TOMEE-4060]
> > > > Tomcat 9.0.67
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4087[TOMEE-4087]
> > > > Tomcat 9.0.68
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4018[TOMEE-4018]
> > > > bcprov-jdk15on 1.70
> > > >
> > > > == New Feature
> > > >
> > > > [.compact]
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-3928[TOMEE-3928]
> > > > Example for properties provider
> > > >
> > > > == Bug
> > > >
> > > > [.compact]
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4021[TOMEE-4021]
> > > > Unexpected ehcache 3.8.1 in tomee/lib
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-3850[TOMEE-3850]
> > > > HTTP(S) connections are not reused
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4014[TOMEE-4014]
> > > > Unable to see TomEE version in Tomcat home page with Java 17
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-3979[TOMEE-3979]
> > > > service.bat issue when using JRE_HOME on Windows
> > > >  - link:https://issues.apache.org/jira/browse/TOMEE-4041[TOMEE-4041]
> > > > 4
> > > > CVE Vulnerabilities in snakeyaml-1.30.jar
> > > >  - 

Re: Website not publishing

[Cesar Hernandez]

I pulled the latest main branch locally and compile it (mvn compile
-Djbake.http=true), but the server doesn't seem to be working.
This PR add basic Github Action so we can validate building on each PR
https://github.com/apache/tomee-site-generator/pull/52  we can add Jenkins
pipeline too, but I'm doing git bisect to see how we can add a check(s)
after maven build is successful in trying to validate from CI if all the
JBake requirements are met.

El jue, 20 oct 2022 a las 15:15, David Blevins ()
escribió:

> > On Oct 20, 2022, at 8:53 AM, Swell  wrote:
> >
> > i noticed we clone several times the same repo for several branches,
> >
> > there is room for performance improvement, but currently out of my
> > league/time.
> >
> [...]
> > we receive the object streams slowly ... twice, or more, for the same
> .git
> > database.
> >
> > we should instead, fetch all the DB once, then iterate on the 2 or 3
> > branches , do a reset hard, copy the current branch "docs" into a
> specific
> > folder for the jbake to read.
>
> It would definitely be a real improvement!
>
> >
> > this would cut the time to build by 2 ? maybe another day !
>
> I'm pretty confident it'll be there waiting in months or years should you
> want to take a swing someday. :)  Open source code is so patient.
>
>
> -David
>
>

-- 
Atentamente:
César Hernández.

Re: [HELP] Build times for Infra

[Cesar Hernandez]

Build https://builds.apache.org/job/TomEE/job/master-build-full/776/
finished after 4 hr 25 min, still not much improvement from the average
build time with the MAVEN_OPTS-Xmx1536m
https://builds.apache.org/job/TomEE/job/master-build-full/buildTimeTrend

I reverted MAVEN OPTS to -Xmx1536m and removed the maven property
help:system in the job
https://ci-builds.apache.org/job/TomEE/job/master-build-full/

El vie, 14 oct 2022 a las 12:29, Cesar Hernandez ()
escribió:

> Anyway long story short: yes, our build could be faster with better
>> hardware.  Just not very clear what that hardware should be.
>
>
> We don't know what is running under the hood in
> https://ci-builds.apache.org/ for on-demand workers, but I do see other
> projects that have specific controller types:
> https://jenkins-ccos.apache.org/
> From the numbers so far, it seems that anything bigger than AWS t2.xlarge
> (4 vCpus, 16 GB ram) can speed by half the current timing executor in the
> apache infra is taking
> https://builds.apache.org/job/TomEE/job/master-build-full/buildTimeTrend
>
> Based on Jonathan's feedback, I reviewed, and the current
> https://builds.apache.org/job/TomEE/job/master-build-full is using in
> MAVEN_OPTS = -Xmx1536m
> I wonder if the result shared in this thread have specific MAVEN_OPTS
> values, mine are  = -Xms2g -Xmx8g
>
> I updated https://builds.apache.org/job/TomEE/job/builder-info/ to show
> the worker memory, and it seems we have 18 GB free out of 94 GB. [1], but
> this is distributed amount of other projects running in that worker, so
> there is no guarantee we will always have X or Y GB of RAM available.
> I don't have access to check the runner's limits peer node in the entire
> builds.apache.org. and
> https://cwiki.apache.org/confluence/display/INFRA/Jenkins+node+labels
> documentation seems to be outdated.
>
>
> Today's build already finished
> https://builds.apache.org/job/TomEE/job/master-build-full/774/ and took ~
> 4 hour.
> I updated https://builds.apache.org/job/TomEE/job/master-build-full/ with
> the following changes:
>
> a) Changed MAVEN_OPTS-Xmx1536m to MAVEN_OPTS=-Xmx4096m
> b) Changed  -U --show-version --fail-at-end clean install -Pall-adapters
> -Dfile.encoding=UTF-8 to -U help:system --show-version --fail-at-end clean
> install -Pall-adapters -Dfile.encoding=UTF-8
>  The only change is I added help:system maven argument to maven to
> double-check the OTPS are read.
> c) Build https://builds.apache.org/job/TomEE/job/master-build-full/776/
> is currently running with a) and b) applied, I don't expect to see major
> improvements even if we are now using 4GB and the load on the shared server
> is unpredictable.
>
> After building
> https://builds.apache.org/job/TomEE/job/master-build-full/776/ I plan to
> revert to previous job configurations if need it.
>
>
> [1]
>
> free -g
>   totalusedfree  shared  buff/cache   
> available
> Mem: 94  10  18   0  64  
> 82
>
>
>
>
>
>
> El vie, 14 oct 2022 a las 8:18, Jonathan Gallimore (<
> jonathan.gallim...@gmail.com>) escribió:
>
>> Taking the commands very literally, the timings for 2 machines here are
>> below. I'm curious though - are there any JAVA_OPTS or MAVEN_OPTS we
>> should
>> use here (e.g. max heap)? The slower machine here seems to be running at
>> an
>> absolute crawl 2/3rds of the way through the build here with the default
>> settings. The result below is after a reboot and MAVEN_OPTS="-Xmx4g".
>>
>> Laptop (WSL2/Ubuntu on Windows 11, i7-12700H, 32GB Ram):
>>
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time:  01:36 h
>> [INFO] Finished at: 2022-10-14T11:10:08+01:00
>> [INFO]
>> 
>>
>> Dell Optiplex 7040 "Server" machine (Ubuntu 20.04.5 LTS, i7-6700T, 16GB
>> Ram):
>>
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time:  01:57 h
>> [INFO] Finished at: 2022-10-14T15:16:58+01:00
>> [INFO]
>> 
>>
>> On Fri, Oct 14, 2022 at 12:13 AM David Blevins 
>> wrote:
>>
>> > Alright, here are some build times for the runs I've done.  Results are
>> > quite varied.
>> >
>> > c1.xlarge : [INFO] Total time:  03:59 

Re: [HELP] Build times for Infra

[Cesar Hernandez]

>
> Anyway long story short: yes, our build could be faster with better
> hardware.  Just not very clear what that hardware should be.


We don't know what is running under the hood in
https://ci-builds.apache.org/ for on-demand workers, but I do see other
projects that have specific controller types:
https://jenkins-ccos.apache.org/
>From the numbers so far, it seems that anything bigger than AWS t2.xlarge
(4 vCpus, 16 GB ram) can speed by half the current timing executor in the
apache infra is taking
https://builds.apache.org/job/TomEE/job/master-build-full/buildTimeTrend

Based on Jonathan's feedback, I reviewed, and the current
https://builds.apache.org/job/TomEE/job/master-build-full is using in
MAVEN_OPTS = -Xmx1536m
I wonder if the result shared in this thread have specific MAVEN_OPTS
values, mine are  = -Xms2g -Xmx8g

I updated https://builds.apache.org/job/TomEE/job/builder-info/ to show the
worker memory, and it seems we have 18 GB free out of 94 GB. [1], but this
is distributed amount of other projects running in that worker, so there is
no guarantee we will always have X or Y GB of RAM available.
I don't have access to check the runner's limits peer node in the entire
builds.apache.org. and
https://cwiki.apache.org/confluence/display/INFRA/Jenkins+node+labels
documentation seems to be outdated.


Today's build already finished
https://builds.apache.org/job/TomEE/job/master-build-full/774/ and took ~ 4
hour.
I updated https://builds.apache.org/job/TomEE/job/master-build-full/ with
the following changes:

a) Changed MAVEN_OPTS-Xmx1536m to MAVEN_OPTS=-Xmx4096m
b) Changed  -U --show-version --fail-at-end clean install -Pall-adapters
-Dfile.encoding=UTF-8 to -U help:system --show-version --fail-at-end clean
install -Pall-adapters -Dfile.encoding=UTF-8
 The only change is I added help:system maven argument to maven to
double-check the OTPS are read.
c) Build https://builds.apache.org/job/TomEE/job/master-build-full/776/ is
currently running with a) and b) applied, I don't expect to see major
improvements even if we are now using 4GB and the load on the shared server
is unpredictable.

After building
https://builds.apache.org/job/TomEE/job/master-build-full/776/ I plan to
revert to previous job configurations if need it.


[1]

free -g
  totalusedfree  shared  buff/cache   available
Mem: 94  10  18   0  64  82






El vie, 14 oct 2022 a las 8:18, Jonathan Gallimore (<
jonathan.gallim...@gmail.com>) escribió:

> Taking the commands very literally, the timings for 2 machines here are
> below. I'm curious though - are there any JAVA_OPTS or MAVEN_OPTS we should
> use here (e.g. max heap)? The slower machine here seems to be running at an
> absolute crawl 2/3rds of the way through the build here with the default
> settings. The result below is after a reboot and MAVEN_OPTS="-Xmx4g".
>
> Laptop (WSL2/Ubuntu on Windows 11, i7-12700H, 32GB Ram):
>
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time:  01:36 h
> [INFO] Finished at: 2022-10-14T11:10:08+01:00
> [INFO]
> 
>
> Dell Optiplex 7040 "Server" machine (Ubuntu 20.04.5 LTS, i7-6700T, 16GB
> Ram):
>
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time:  01:57 h
> [INFO] Finished at: 2022-10-14T15:16:58+01:00
> [INFO]
> 
>
> On Fri, Oct 14, 2022 at 12:13 AM David Blevins 
> wrote:
>
> > Alright, here are some build times for the runs I've done.  Results are
> > quite varied.
> >
> > c1.xlarge : [INFO] Total time:  03:59 h
> > t2.medium : [INFO] Total time:  05:05 h
> > t2.xlarge : [INFO] Total time:  02:30 h
> > t3.medium : [INFO] Total time:  03:21 h
> > my.laptop : [INFO] Total time:  01:56 h
> >
> > Specs for the AWS instances are public.  Here are the stats for my
> laptop:
> >
> > MacBook Pro (16-inch, 2019)
> > 2.4 GHz 8-Core Intel Core i9
> > Memory 64 GB 2667 MHz DDR4
> >
> > I did try some other AWS instance types, but anything with 2GB or less
> > failed due to out of memory issues.  I'd be interested to try some other
> > types, particularly the AMD-based types.
> >
> > Anyway long story short: yes, our build could be faster with better
> > hardware.  Just not very clear what that hardware should be.
> >
> >
> > -David
> >
> >
> > > On Oct 11, 2022, at 3:05 PM, David Blevins 
> > wrote:
> > >
> > > All,
> > >
> > > I'm collecting some stats on how long it takes to run our full build
> > exactly as Jenkins does.  The goal is to work with them to see if we can
> > get some better hardware -- I assume that will require donations, etc.
> > >
> > > If you'd like to help in collecting data, 

Re: TomEE MicroProfile - current status

[Cesar Hernandez]

Awesome news Jean-Louis, thank you for the update!

El vie, 2 sept 2022 a las 4:59, Jean-Louis Monteiro (<
jlmonte...@tomitribe.com>) escribió:

> Quick update ...
>
> I managed to finish the SmallRye OpenAPI integration. We now pass 100% of
> the MicroProfile OpenAPI TCK.
> I'm cleaning up and I'll be pushing soon.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Thu, Sep 1, 2022 at 3:25 PM Jean-Louis Monteiro <
> jlmonte...@tomitribe.com>
> wrote:
>
> > Hi,
> >
> > Thanks for the update.
> > For the command to work you need first to put the module back in the
> > reactor
> >
> >
> https://github.com/apache/tomee/blob/main/tck/microprofile-tck/pom.xml#L39
> >
> > It's currently commented out.
> >
> > Can you try it and see if it works?
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Wed, Aug 31, 2022 at 7:59 AM Zoltán Tichov 
> > wrote:
> >
> >> Hi!
> >>
> >> When I tried to run 'mvn clean install -pl
> >> tck/microprofile-tck/opentracing', I received the following error
> message:
> >> Could not find the selected project in the reactor:
> >> tck/microprofile-tck/opentracing
> >> However I ran the tests in NetBeans and all tests was failed. Is this
> >> normal yet? I have not changed any code yet.
> >> I used openjdk 17 in NetBeans, is this appropriate or should I change to
> >> openjdk 11?
> >> --
> >> Zoltán
> >>
> >>
> >> On Wed, Aug 24, 2022 at 2:42 PM Jean-Louis Monteiro <
> >> jlmonte...@tomitribe.com> wrote:
> >>
> >> > Awesome.
> >> >
> >> > So lemme start with some pointers.
> >> >
> >> > The MicroProfile integration code sits in this module
> >> >
> >> >
> >>
> https://github.com/apache/tomee/tree/main/tomee/tomee-microprofile/mp-common/src/main/java/org/apache/tomee/microprofile
> >> > You have one subpackage per MicroProfile specification.
> >> >
> >> > The TomEEMicroProfileService registers the TomEEMicroProfileListener
> >> which
> >> > is responsible for wiring all extensions for each specification.
> >> >
> >> > The TCK setup is located here
> >> > https://github.com/apache/tomee/tree/main/tck/microprofile-tck
> >> > Same as previously, one module per specification. The OpenTracing is
> >> there.
> >> >
> >> > Basically, if you add it back to the reactor, Maven will run the
> >> > OpenTracing TCK.
> >> >
> >> > You can do `mvn clean install -DskipTests` and then `mvn clean install
> >> -pl
> >> > tck/microprofile-tck/opentracing`
> >> > There is a tck-dev.xml you can use to run individual or all tests in
> the
> >> > IDE (TestNG based).
> >> >
> >> > Let's start this way and lemme know what you think and if you need
> more
> >> > help
> >> >
> >> > --
> >> > Jean-Louis Monteiro
> >> > http://twitter.com/jlouismonteiro
> >> > http://www.tomitribe.com
> >> >
> >> >
> >> > On Wed, Aug 24, 2022 at 1:45 PM Zoltán Tichov <
> zoltan.tic...@gmail.com>
> >> > wrote:
> >> >
> >> > > Hi!
> >> > >
> >> > > Then I'd rather continue the OpenTracing integration, so I'd be
> happy
> >> if
> >> > > you could help me to start it.
> >> > >
> >> > > Zoltán Tichov
> >> > >
> >> > > On Wed, Aug 24, 2022 at 12:49 PM Jean-Louis Monteiro <
> >> > > jlmonte...@tomitribe.com> wrote:
> >> > >
> >> > > > I have started OpenTracing so you have some basics to continue if
> >> you
> >> > > want
> >> > > > to.
> >> > > > The TCK setup is done and some integration is also done.
> >> > > >
> >> > > > Does that sound good?
> >> > > >
> >> > > > Fault tolerance and OpenAPI are not started so it might be a bit
> >> > > > challenging to start from scratch. But either way I am happy to
> >> help.
> >> > > >
> >> > > >
> >> > > > --
> >> > > > Jean-Louis Monteiro
> >> > > > http://twitter.com/jlouismonteiro
> >> > > > http://www.tomitribe.com
> >> > > >
> >> > > >
> >> > > > On Tue, Aug 23, 2022 at 4:55 PM Zoltán Tichov <
> >> zoltan.tic...@gmail.com
> >> > >
> >> > > > wrote:
> >> > > >
> >> > > > > Hi!
> >> > > > >
> >> > > > > I want to work on any of them.
> >> > > > >
> >> > > > > --
> >> > > > > Zoltán Tichov
> >> > > > >
> >> > > > > On Tue, Aug 23, 2022 at 2:39 PM Jean-Louis Monteiro <
> >> > > > > jlmonte...@tomitribe.com> wrote:
> >> > > > >
> >> > > > > > Hi,
> >> > > > > >
> >> > > > > > Was looking for the last thread to pull up, but it's pretty
> far
> >> > back
> >> > > > and
> >> > > > > > misses many different things. So I decided to create a new
> >> thread
> >> > as
> >> > > a
> >> > > > > > follow up.
> >> > > > > >
> >> > > > > > Since then, we worked a lot on Jakarta EE 9 compatibility and
> we
> >> > are
> >> > > > > close
> >> > > > > > enough. So we can now focus on MicroProfile to catch up with
> the
> >> > > latest
> >> > > > > > available version.
> >> > > > > >
> >> > > > > > So far,
> >> > > > > >
> >> > > > > >- rest-client using CXF is fully integrated and compatible.
> >> No
> >> > > > failure
> >> > > > > >- metrics using SmallRye. No failure.
> >> > > > > >- health 

Re: [VOTE] Apache TomEE 9.0.0-M8

[Cesar Hernandez]

+1 thank you!

El mié, 29 jun 2022 a las 5:59, Daniel Dias Dos Santos (<
daniel.dias.analist...@gmail.com>) escribió:

> Hi
>
> +1
>
> Thanks
>
> On Tue, Jun 28, 2022, 19:01 Jean-Louis Monteiro 
> wrote:
>
> > Hi,
> >
> > As discussed, here is the vote for Apache TomEE 9.0.0-M8. This milestone
> > differs from previous 9.x in the sense that we migrated all TomEE code to
> > the new jakarta namespace. Previously, we used bytecode relocation but
> most
> > of the integration was broken (tests, arquillian, etc).
> >
> > We are still working on some regressions and fixes in order to pass all
> TCK
> > for Jakarta EE 9.1. But starting to gather feedback can only help sooner
> > rather than later.
> >
> > This is a maintenance release with minor fixes and dependencies upgrades.
> >
> > Maven staging repo
> > https://repository.apache.org/content/repositories/orgapachetomee-1205/
> >
> > Binaries and sources
> > https://dist.apache.org/repos/dist/dev/tomee/tomee-9.0.0-M8
> >
> > Github Tag
> > https://github.com/apache/tomee/tree/tomee-project-9.0.0-M8
> >
> > Commit hash
> > 12e5dd91fe34affa775a68d5341576b417530008
> >
> > Release Notes
> > https://issues.apache.org/jira/projects/TOMEE/versions/12350178
> >
> > Sub-task
> >
> >- [TOMEE-3861 ] -
> >Upgrade to apache-parent-26
> >- [TOMEE-3865 ] -
> >Switch arquillian to the new Servlet 5 protocol
> >- [TOMEE-3866 ] -
> >Upgrade Hibernate to 5.6.7 / Hibernate Validator to 7.0.2 (Jakarta
> > Artifact)
> >- [TOMEE-3868 ] -
> >Remove SAAJ Axis 1 provider
> >- [TOMEE-3869 ] -
> >Remove JAX-RPC
> >- [TOMEE-3870 ] -
> >Remove Management J2EE
> >- [TOMEE-3877 ] -
> No
> >interface view EJB proxies broken on JDK16+
> >- [TOMEE-3879 ] -
> Add
> >missing --add-opens options to itests/failover
> >- [TOMEE-3881 ] -
> Add
> >JDK --add-opens to our scripts in openejb-standalone
> >- [TOMEE-3920 ] -
> Fix
> >TomEE :: Web Examples :: Moviefun Rest
> >- [TOMEE-3922 ] -
> >Patch Tomcat JasperInitializer and create jira
> >- [TOMEE-3925 ] -
> Fix
> >Websocket TLS Basic Auth
> >- [TOMEE-3926 ] -
> Fix
> >Webservice SSL Client Certificate Example
> >- [TOMEE-3930 ] -
> fix
> >arquillian-tomee-moviefun-example
> >- [TOMEE-3931 ] -
> fix
> >example/cucumber-jvm
> >- [TOMEE-3932 ] -
> >Migration tips and tricks
> >- [TOMEE-3939 ] -
> Fix
> >Jakarta Mail API with Apache Velocity Templating
> >- [TOMEE-3940 ] -
> Fix
> >TomEE :: Examples :: JakartaMail API
> >- [TOMEE-3943 ] -
> Fix
> >TomEE :: Examples :: Multiple JPA providers
> >- [TOMEE-3944 ] -
> Fix
> >TomEE :: Examples :: Simple EAR :: Functional Tests
> >- [TOMEE-3953 ] -
> Fix
> >TomEE :: Examples :: JPA with EclipseLink
> >- [TOMEE-3954 ] -
> Fix
> >TomEE :: Examples :: JPA with Hibernate and arquillian
> >- [TOMEE-3956 ] -
> Fix
> >TomEE :: Connector Examples :: Connector in WAR
> >- [TOMEE-3957 ] -
> Fix
> >TomEE :: Examples :: DeltaSpike @ConfigProperty
> >- [TOMEE-3958 ] -
> Fix
> >TomEE :: Examples :: DeltaSpike Exception Handling
> >- [TOMEE-3959 ] -
> Fix
> >TomEE :: Examples :: DeltaSpike I18n
> >- [TOMEE-3960 ] -
> Fix
> >TomEE :: Examples :: DeltaSpike ProjectStage
> >
> > Bug
> >
> >- [TOMEE-2420 ] -
> >Incorrect "Wall of fame" page layout
> >- [TOMEE-3739 ] -
> Fix
> >JAX-RS landscape / regressions introduced during TCK Work
> >- [TOMEE-3740 

Re: Release issue with master

[Cesar Hernandez]

Hi Jean-Louis,

As Richard mentioned, the first version-related issue during release was
documented here: https://issues.apache.org/jira/browse/TOMEE-3916
For the latest one you are sharing, may be related to:
https://issues.apache.org/jira/browse/MJAVADOC-618

El lun, 27 jun 2022 a las 6:19, Jean-Louis Monteiro (<
jlmonte...@tomitribe.com>) escribió:

> Hi all,
>
> Yes this one is fixed and I pushed a couple of other workarounds for this
> release so we are not stuck.
> Now trying to fix this one. So if anyone has some hints to help.
>
> [INFO] [INFO]
> > 
> > [INFO] [INFO] BUILD FAILURE
> > [INFO] [INFO]
> > 
> > [INFO] [INFO] Total time:  02:51 min
> > [INFO] [INFO] Finished at: 2022-06-27T10:57:55+02:00
> > [INFO] [INFO]
> > 
> > [INFO] [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-javadoc-plugin:3.3.2:jar (attach-javadocs)
> > on project openejb-jee: Execution attach-javadocs of goal
> > org.apache.maven.plugins:maven-javadoc-plugin:3.3.2:jar failed:
> > '/Users/jlmonteiro/devs/jeanouii/apache/tomee/boms/jaxb-runtime/pom.xml'
> > not allowed on the path, only outputDirectories and jars are accepted ->
> > [Help 1]
> >
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Mon, Jun 27, 2022 at 11:36 AM Richard Zowalla  wrote:
>
> > Looks like we solved this issue. It was related to ${} version
> > property replacement in nested module structures in the examples, which
> > couldn't be resolved via the mvn release plugin.
> >
> > We now have some javadoc related struggles...
> >
> > Gruß
> > rz
> >
> >
> > Am Sonntag, dem 26.06.2022 um 21:43 +0200 schrieb Jean-Louis Monteiro:
> > > Does someone has an idea about this
> > > Currently blocking 9.0.0-M8 release
> > >
> > > [INFO]
> > > > -
> > > > ---
> > > > [INFO] BUILD FAILURE
> > > > [INFO]
> > > > -
> > > > ---
> > > > [INFO] Total time:  15.393 s
> > > > [INFO] Finished at: 2022-06-26T21:42:16+02:00
> > > > [INFO]
> > > > -
> > > > ---
> > > > [ERROR] Failed to execute goal
> > > > org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare
> > > > (default-cli) on project tomee-project: The version could not be
> > > > updated:
> > > > ${tomee.version} -> [Help 1]
> > > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> > > > execute
> > > > goal org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare
> > > > (default-cli) on project tomee-project: The version could not be
> > > > updated:
> > > > ${tomee.version}
> > > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > > > (MojoExecutor.java:215)
> > > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > > > (MojoExecutor.java:156)
> > > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > > > (MojoExecutor.java:148)
> > > > at
> > > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildPro
> > > > ject
> > > > (LifecycleModuleBuilder.java:117)
> > > > at
> > > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildPro
> > > > ject
> > > > (LifecycleModuleBuilder.java:81)
> > > > at
> > > > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleTh
> > > > readedBuilder.build
> > > > (SingleThreadedBuilder.java:56)
> > > > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> > > > (LifecycleStarter.java:128)
> > > > at org.apache.maven.DefaultMaven.doExecute
> > > > (DefaultMaven.java:305)
> > > > at org.apache.maven.DefaultMaven.doExecute
> > > > (DefaultMaven.java:192)
> > > > at org.apache.maven.DefaultMaven.execute
> > > > (DefaultMaven.java:105)
> > > > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> > > > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> > > > at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> > > > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0
> > > > (Native
> > > > Method)
> > > > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> > > > (NativeMethodAccessorImpl.java:62)
> > > > at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> > > > (DelegatingMethodAccessorImpl.java:43)
> > > > at java.lang.reflect.Method.invoke (Method.java:566)
> > > > at
> > > > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> > > > (Launcher.java:282)
> > > > at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> > > > (Launcher.java:225)
> > > > at
> > > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> > > > 

Re: [VOTE] Apache TomEE jakartaee-api 9.1-M2

[Cesar Hernandez]

+1

El lun, 13 jun 2022 a las 3:53, Daniel Dias Dos Santos (<
daniel.dias.analist...@gmail.com>) escribió:

> Hello,
>
> +1
>
> On Mon, Jun 13, 2022, 06:49 Jean-Louis Monteiro 
> wrote:
>
> > Hi folks!
> >
> > I'd like to call a VOTE on Apache TomEE jakarta-api-9.1-M2.
> >
> > This is another step to complete Jakarta 9.1 certification. Changes are
> > essentially
> >
> > - adding Jakarta Security which was missing
> > - Management API was also missing
> > - use Geronimo Activation which is now fully compliant
> > - remove jcache and XML apis because they aren't part of jakarta
> > - remove faces API because it's tight to impl and we do support 2
> > implementations so we need to be able to switch while building TomEE.
> >
> >
> > The staging repo is:
> > https://repository.apache.org/content/repositories/orgapachetomee-1204
> >
> > The source zip can be found at
> > https://dist.apache.org/repos/dist/dev/tomee/jakartaee-api-9.1-M2/
> >
> >
> > Please VOTE
> >
> > [+1] go ship it
> > [+0] meh, don't care
> > [-1] stop, there is a ${showstopper}
> >
> > The VOTE is open for 72h
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
>


-- 
Atentamente:
César Hernández.

Re: [VOTE] Apache TomEE 8.0.12

[Cesar Hernandez]

+1

El lun, 13 jun 2022 a las 4:57, Jonathan Gallimore (<
jonathan.gallim...@gmail.com>) escribió:

> +1
>
> Jon
>
> On Tue, Jun 7, 2022 at 1:43 PM Jean-Louis Monteiro <
> jlmonte...@tomitribe.com>
> wrote:
>
> > Hi,
> >
> > As discussed, here is the vote for Apache TomEE 8.0.12.
> >
> > This is a maintenance release with minor fixes and dependencies upgrades.
> >
> > Maven staging repo
> > https://repository.apache.org/content/repositories/orgapachetomee-1203
> >
> > Binaries and sources
> > https://dist.apache.org/repos/dist/dev/tomee/tomee-8.0.12/
> >
> > Github Tag
> > https://github.com/apache/tomee/tree/tomee-project-8.0.12
> >
> > Release Notes
> > https://issues.apache.org/jira/projects/TOMEE/versions/12351588
> >
> > Sub-task
> >
> >- [TOMEE-3647 ] -
> >Update example 'mvc-resteasy' to use Server/API Bom
> >- [TOMEE-3861 ] -
> >Upgrade to apache-parent-26
> >
> > Bug
> >
> >- [TOMEE-3849 ] -
> >EclipseLink JPA provider not discoverable in TomEE Plume libraries
> >- [TOMEE-3903 ] -
> >Investigate *.tar.gz distributions aren't installed correctly to Maven
> >Repository
> >- [TOMEE-3908 ] -
> CI
> >Job für TomEE Site Publish is failing
> >- [TOMEE-3919 ] -
> Fix
> >GitHub Actions Bom Generation targeting wrong branch
> >- [TOMEE-3935 ] -
> BOM
> >Regeneration fails due to GitHub Actions permission issue
> >- [TOMEE-3969 ] -
> >javax.cache API not part of Jakarta EE 8
> >
> > Improvement
> >
> >- [TOMEE-3924 ] -
> >Disable @dependabot via .asf.yaml
> >- [TOMEE-3934 ] -
> >Upgrade to Johnzon 1.2.18
> >
> > Task
> >
> >- [TOMEE-3905 ] -
> Fix
> >Post release pom versioning for tomee-8.x branch
> >
> > Dependency upgrade
> >
> >- [TOMEE-3911 ] -
> >Upgrade XBean to 4.21
> >- [TOMEE-3912 ] -
> >Upgrade TomEE Patch Plugin to 0.9
> >- [TOMEE-3913 ] -
> >Examples: Upgrade JUnit 4.12 to 4.13.2
> >- [TOMEE-3918 ] -
> >Upgrade Johnzon to 1.2.17
> >- [TOMEE-3941 ] -
> >Apache ActiveMQ 5.16.5
> >- [TOMEE-3961 ] -
> >Upgrade to Apache Tomcat 9.0.63 (CVE-2022-29885)
> >- [TOMEE-3977 ] -
> >Apache OpenWebBeans 2.0.27
> >
> > Documentation
> >
> >- [TOMEE-3846 ] -
> >Inconsistence between tomee flavors comparison in website and actual
> > jars
> >- [TOMEE-3904 ] -
> >Enhance / Update existing release documentation
> >
> >
> > Please VOTE
> >
> > [+1] go ship it
> > [+0] meh, don't care
> > [-1] stop, there is a ${showstopper}
> >
> > The VOTE is open for 72h
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
>


-- 
Atentamente:
César Hernández.

Re: TomEE 9.x - from javax to jakarta namespace

[Cesar Hernandez]

+1, Thank you!


El mié, 11 may 2022 a las 9:06, Daniel Dias Dos Santos (<
daniel.dias.analist...@gmail.com>) escribió:

> +1
>
> On Wed, May 11, 2022, 12:00 Zowalla, Richard <
> richard.zowa...@hs-heilbronn.de> wrote:
>
> > I am fine with it: +1
> > 
> > Von: Jean-Louis Monteiro 
> > Gesendet: Mittwoch, 11. Mai 2022 15:57:54
> > An: dev@tomee.apache.org
> > Betreff: Re: TomEE 9.x - from javax to jakarta namespace
> >
> > Alright, with the latest changes pushed yesterday and today, we are now
> at
> > the exact same numbers for TomEE 8.x / Jakarta EE 8 under JDK8 and TomEE
> > 9.x / Jakarta 9.1 under JDK17.
> >
> > If everyone is ok with it, we can create a new milestone and give users
> the
> > opportunity to provide us with some feedback and to report bugs.
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Tue, May 10, 2022 at 7:06 PM David Blevins 
> > wrote:
> >
> > > Was checking out the TCK numbers this morning can make to suggest a
> > > 9.0.0-M8 while things look good and found this amazing email.
> > >
> > > The 9.0.x branch is looking absolutely amazing!!!
> > >
> > > What do we think about pushing out a 9.0.0-M8 while things are in their
> > > peak-stable state?  I'm sure we'll have to rip up a few more things to
> > > finish off the remaining Jakarta EE and MP TCK issues.  Would be great
> to
> > > have something that isn't M7 to fallback on as a reference point to
> track
> > > regressions.
> > >
> > > Thoughts?
> > >
> > >
> > > -David
> > >
> > >
> > >
> > > > On May 10, 2022, at 3:56 AM, Jean-Louis Monteiro <
> > > jlmonte...@tomitribe.com> wrote:
> > > >
> > > > Hi all,
> > > >
> > > > Time for some reporting
> > > >
> > > > On our journey to migrate TomEE over from javax to jakarta namespace,
> > we
> > > > had many issues.
> > > > After updating all our code, we had to do a bunch of dependency
> > upgrades
> > > > after upgrading many of them (OpenWebbeans, BVal, Geronimo, etc).
> > > >
> > > > We then faced many issues with non compatible libraries for example
> > > > (ActiveMQ, commons-dbcp, CXF, sxc, taglib, etc). So we ended up
> > repacking
> > > > them in our own groupId after using the Maven Shade plugin to
> relocate
> > > the
> > > > packages.
> > > >
> > > > We worked on BVal TCK and CDI TCK and we are close to passing them.
> > > >
> > > > But we had before to solve all our outdated MicroProfile 1.3 stack to
> > the
> > > > most recent and jakarta compatible version. Geronimo implementations
> > > being
> > > > far being, we decided to use some SmallRye implementations until we
> can
> > > > dedicate some time to update our Apache implementations (config,
> > metrics,
> > > > health, openapi, opentracing, fault tolerance).
> > > >
> > > > Our build is now more stable, but still not green. Some issues are
> > > > basically easy to fix and most people could do it (examples for
> > > instance).
> > > >
> > > > https://ci-builds.apache.org/job/Tomee/job/master-build-full/
> > > >
> > > > The integration for openapi, opentracing and fault tolerance is not
> > done
> > > > and we are far from passing the TCK. On config, metrics and health we
> > are
> > > > close. Same for our JWT implementation.
> > > >
> > > > I also wanted to have a view on the platform TCK, so I decided to
> stop
> > > > TomEE work in order to spend time on the Platform TCK to do all
> > > dependency
> > > > upgrades and get the TCK to run properly. I'm pleased to announce
> that
> > > > after 2 weeks of hard work, we are 99% compatible
> > > >
> > > > https://tck.work/tomee/build?id=1652104572445
> > > >
> > > > Thanks everyone for the help.
> > > > Keep going and if you need some guidance or help, let us know.
> > > >
> > > > For coordination purposes, here is the issue
> > > > https://issues.apache.org/jira/browse/TOMEE-3862
> > > > Many subtasks are there and you can create new tasks when needed and
> > ask
> > > > any committer to assign it to you.
> > > >
> > > >
> > > >
> > > > --
> > > > Jean-Louis Monteiro
> > > > http://twitter.com/jlouismonteiro
> > > > http://www.tomitribe.com
> > > >
> > > >
> > > > On Thu, May 5, 2022 at 11:13 AM Zowalla, Richard <
> > > > richard.zowa...@hs-heilbronn.de> wrote:
> > > >
> > > >> Yes - we already yanked it in 9.x
> > > >>
> > > >> Gruß
> > > >> Richard
> > > >>
> > > >> Am Donnerstag, dem 05.05.2022 um 10:10 +0100 schrieb Jonathan
> > > >> Gallimore:
> > > >>> Sounds good. I'll drop the transformer from the 8.x branch (looks
> > > >>> like we
> > > >>> don't use it in 9.x), and I'll create a single example to
> demonstrate
> > > >>> it in
> > > >>> a sandbox.
> > > >>>
> > > >>> Jon
> > > >>>
> > > >>> On Wed, May 4, 2022 at 12:32 PM Zowalla, Richard <
> > > >>> richard.zowa...@hs-heilbronn.de> wrote:
> > > >>>
> > >  You are right - we can remove it imho from 8.x as we do not test
> > >  with
> > >  it and the transformed samples might not even work, 

Re: [VOTE] Apache TomEE Patch Plugin 0.9

[Cesar Hernandez]

+1

On Thu, May 5, 2022 at 06:44 Daniel Dias Dos Santos <
daniel.dias.analist...@gmail.com> wrote:

> +1
>
> On Thu, May 5, 2022, 09:43 Richard Zowalla  wrote:
>
> > +1
> >
> > Am Dienstag, dem 03.05.2022 um 11:01 +0200 schrieb Jean-Louis Monteiro:
> > > Hi,
> > >
> > > I'd like to vote Apache TomEE Patch Plugin 0.9 up for vote. The
> > > changes are
> > > fairly minimal and are meant to help with Maven new versions.
> > >
> > > Again, big thank you Richard for putting this together.
> > >
> > > Changes:
> > >
> > > - Fix for TOMEE-3903 (Don't attach *.tar.gz files multiple times)
> > >
> > > Sources:
> > >
> > > https://dist.apache.org/repos/dist/dev/tomee/staging-1201/
> > >
> > > Staging Nexus Repository:
> > >
> > >
> https://repository.apache.org/content/repositories/orgapachetomee-1201/
> > >
> > > Tag:
> > >
> > >
> >
> https://github.com/apache/tomee-patch-plugin/releases/tag/tomee-patch-parent-0.9
> > >
> > > Please vote to approve this release:
> > > [ ] +1 Approve the release
> > > [ ] -1 Don't approve the release (please provide specific comments)
> > >
> > > This vote will be open for at least 72 hours.
> > >
> > > Jean-Louis
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
> >
> >
>
-- 
Atentamente:
César Hernández.

Re: Next TomEE+ 7.1.x release

[Cesar Hernandez]

Hello,


7.1.x full build is back to green:
> https://ci-builds.apache.org/job/Tomee/job/tomee-7.1.x/11/


@Richard, that's awesome, thank you!


Let me start on the workflow items and then look at the dependencies to see


Hi, @Geeth, on the top of my head, the following dependencies may need to
be updated.:

   - Tomcat
   - cxf
   - mojarra
   - jackson
   - santuario

The job https://ci-builds.apache.org/job/Tomee/job/pull-request/ listen to
PR's against TomEE  7.1.x branch, among others, so feedback is
automatically provided if you open a PR.






El sáb, 23 abr 2022 a las 13:13, Zowalla, Richard (<
richard.zowa...@hs-heilbronn.de>) escribió:

> Hi,
>
> did some fixes and now the 7.1.x full build is back to green:
> https://ci-builds.apache.org/job/Tomee/job/tomee-7.1.x/11/
>
> That means we are in good shape for the dependency updates as we now have
> a valid baseline and any change can be validated via CI.
>
> Gruß
> Richard
> 
> Von: Geeth Narayanan 
> Gesendet: Freitag, 22. April 2022 14:47:27
> An: dev@tomee.apache.org
> Betreff: Re: Next TomEE+ 7.1.x release
>
> Thanks, Richard and Jean-Louis. Appreciate your flexibility.
>
> Let me start on the workflow items and then look at the dependencies to see
> what's included and maybe go out the latest minor version in that mainline
> version.
>
> Will keep you posted.
>
> On Fri, Apr 22, 2022 at 4:18 AM Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
>
> > Hi,
> >
> > Thanks Richard for restoring a CI for the 7.1.x branch.
> >
> > If we can have multiple PRs to update the dependencies and the build is
> > green, I agree with Richard, it should not be a big problem to do the
> > release.
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Fri, Apr 22, 2022 at 8:02 AM Zowalla, Richard <
> > richard.zowa...@hs-heilbronn.de> wrote:
> >
> > > Hi Geeth,
> > >
> > > thanks for your first contribution to TomEE. It is very much
> > > appreciated.
> > >
> > > The last release was in 2020 and most effort has been shifted to 8.x
> > > and 9.x. Personally, I do not use 7.1.x in any project anymore.
> > > Therefore, I am unable to test related binaries.
> > >
> > > Nevertheless, I appreciate your attitude in offering help in reviewing
> > > / contributing. Therefore, I created / restored the CI environment for
> > > 7.1.x [1] and triggered a full build, so we get some information how
> > > the current build looks like.
> > >
> > > With a working CI env in place, we would need to conduct (or at least
> > > try) some dependency updates (like Tomcat, BatchEE (maybe?), CXF
> > > (maybe?), Johnzon (maybe?), OWB (maybe?), ActiveMQ (maybe?), MyFaces
> > > (maybe?), Mojarra (maybe?), Jackson (maybe - used in Microprofile),
> > > etc.) and find the latest corresponding versions supporting EE7.
> > >
> > > Perhaps that would be a good starting point to contribute, if you have
> > > some spare time / resources available.
> > >
> > > Our basic contribution workflow would be:
> > >
> > > (1) Create a Jira (e.g. for a version update)
> > > (2) Ask on the dev@ list to be assigned
> > > (3) Work on the issue. Ask for help / guidance if needed
> > > (4) Create a PR.
> > > (5) Ask for review on dev@
> > >
> > > In addition it needs some fixes on the structure of the project itself
> > > (SCM urls as git-wip-us went EOL a few weeks ago). If we decide to
> > > pursue this further, I can do these (structural) changes.
> > >
> > > If the CI is green afterwards, a potential 7.1.5 would be in a good
> > > shape IMHO.
> > >
> > > The (mechanical) work to conduct a release isn't that much of an effort
> > > but requires a TomEE PMC member for some of the steps (eg. the vote,
> > > etc.).
> > >
> > > The list of currently resolved issues for a 7.1.5 is here: [2]
> > >
> > > Gruß
> > > Richard
> > >
> > >
> > > [1] https://ci-builds.apache.org/job/Tomee/job/tomee-7.1.x/
> > > [2] https://issues.apache.org/jira/projects/TOMEE/versions/12349482
> > >
> > > Am Donnerstag, dem 21.04.2022 um 19:29 -0500 schrieb Geeth Narayanan:
> > > > Hi,
> > > >
> > > > I recently made my first code contribution as a patch to 7.1.x
> > > > release.
> > > > This was for a startup issue that has been fixed in 8.x. It was also
> > > > not
> > > > present in 7.1.1, but was introduced in 7.1.2.
> > > >
> > > > I understand that the team's focus is to release 8.x and 9.x, but I
> > > > was
> > > > wondering if you could put out 7.1.5 with this change and anything
> > > > else in
> > > > there. Looks like it's been a while since 7.1.4 was released.
> > > >
> > > > As I mentioned, it was my first foray into contribution, so please
> > > > let me
> > > > know if I can help in any way like reviewing binaries or contributing
> > > > on
> > > > anything else.
> > > >
> > > > Appreciate the help!
> > > >
> > > > More information on the issue:
> > > >
> > > > https://issues.apache.org/jira/browse/TOMEE-2919
> > > > 

Re: TomEE 9.x - from javax to jakarta namespace

[Cesar Hernandez]

+1 Jonathan.


On Wed, May 4, 2022 at 05:32 Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> wrote:

> You are right - we can remove it imho from 8.x as we do not test with
> it and the transformed samples might not even work, e.g. dependencies
> are not migrated, etc.
>
> +1 for providing a (bigger) example.
>
> Gruß
> Richard
>
> Am Mittwoch, dem 04.05.2022 um 11:17 +0100 schrieb Jonathan Gallimore:
> > I've picked up a task related to the examples:
> > https://issues.apache.org/jira/browse/TOMEE-3873. I specifically went
> > for
> > this, as I added the Eclipse Transformer to the build for a number of
> > examples in the past, back when we were doing the transformation
> > process on
> > TomEE itself. The drawbacks here is that any tests in the examples
> > run on
> > the javax code, and we just "assume" that the transformed artifact
> > works. I
> > would suggest removing that for the master build, as it just takes
> > build
> > time, and the examples should be transformed from javax to jakarta at
> > source (if they aren't already). On the TomEE 8 build, we could
> > select a
> > few examples (no need to do them all) and find a way to run the tests
> > on
> > both javax and jakarta versions of TomEE.
> >
> > Additionally, it would likely be useful to add documentation to this.
> > If we
> > also wanted a bigger example application that specifically covers
> > transformation, I could look at that too.
> >
> > What do you think?
> >
> > Jon
> >
> >
> >
> > On Tue, Mar 22, 2022 at 12:58 PM Jean-Louis Monteiro <
> > jlmonte...@tomitribe.com> wrote:
> >
> > > Hi,
> > >
> > > I've been working for quite a long time on TomEE 9.x, and it's been
> > > more
> > > challenging and painful than I was expecting. I thought it would be
> > > good to
> > > give you some sort of status.
> > >
> > > I created a PR for the work. As a reminder, since Java EE moved to
> > > Eclipse
> > > to become Jakarta EE, we had a switch from javax.* namespace to
> > > jakarta.*
> > > namespace. This is an impacting change, since all applications and
> > > applications servers are built on top of it.
> > >
> > > In TomEE, we decided to do that change in TomEE. We had previously
> > > a
> > > bytecode change approach like an application could do. It worked
> > > and we
> > > were able to get certified. But it had a lot of limitations, so we
> > > had to
> > > do the migration in the code and fix all compatibility issues.
> > >
> > > Here is the PR https://github.com/apache/tomee/pull/814
> > > It has 90+ commits and nearly 5000 files touched (added, removed,
> > > updated).
> > > I understand it's a lot and it makes it almost impossible to
> > > review. But I
> > > did not see much approaches in this scenario to create smaller PRs.
> > >
> > > I created a Jenkins build though available at
> > > https://ci-builds.apache.org/job/Tomee/job/master-build-quick-9.x/
> > >
> > > It makes it possible to track the progress. There have been steps
> > > forward
> > > and steps backward.
> > >
> > > All the code does not sit under TomEE, we use a bunch of third
> > > party
> > > projects and libraries. I have been able to contribute, publish
> > > jakarta
> > > compatible versions and get releases for some of them (Jakarta EE
> > > APIs Uber
> > > jar, Geronimo Connectors and Transaction Manager, Geronimo Config,
> > > Health,
> > > Metrics, OpenTracing, OpenAPI. OpenJPA, BVal, and OpenWebBeans will
> > > be
> > > released soon.
> > >
> > > The big parts is CXF, and ActiveMQ. I had to get them done in TomEE
> > > and
> > > update all group/artifact ids. It's under deps, alongside with SXC,
> > > DBCP,
> > > and others.
> > >
> > > In terms of removal, I tried to remove old stuff like SAAJ Axis 1
> > > integration, JAX RPC, Management J2EE and a couple of other old
> > > things.
> > >
> > > A lot of other libraries got updated to their latest version when
> > > available
> > > in the new jakarta namespace.
> > >
> > > I'm starting to get all the build stable and many modules are
> > > passing now,
> > > including all CXF webservices, OpenEJB Core, and others. I can get
> > > a build
> > > and run TomEE.
> > >
> > > Goal is to get a green build asap so we can start working on TCK.
> > > The "quick" build is now green. Working on the full build.
> > >
> > > I'll soon be creating a branch for TomEE 8.x maintenance and merge
> > > the PR.
> > > I'm hoping we can then have small PRs or at least more people
> > > working in
> > > parallel.
> > >
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
> > >
>
-- 
Atentamente:
César Hernández.

Re: TomEE 9.x - from javax to jakarta namespace

[Cesar Hernandez]

Thank you, I push the fixes.

El mar, 3 may 2022 a las 10:50, Zowalla, Richard (<
richard.zowa...@hs-heilbronn.de>) escribió:

> Thanks, Cesar. I left some comments.
>
> Am Montag, dem 02.05.2022 um 21:01 -0600 schrieb Cesar Hernandez:
> > I created https://issues.apache.org/jira/browse/TOMEE-3932 and the PR
> > with
> > the first iteration of the document is ready for review.
> > https://github.com/apache/tomee/pull/878
> >
> > El sáb, 30 abr 2022 a las 0:26, Zowalla, Richard (<
> > richard.zowa...@hs-heilbronn.de>) escribió:
> >
> > > Sounds good: +1
> > >
> > > Am Freitag, dem 29.04.2022 um 11:06 +0200 schrieb Jean-Louis
> > > Monteiro:
> > > > That sounds great Cesar. Thanks
> > > > --
> > > > Jean-Louis Monteiro
> > > > http://twitter.com/jlouismonteiro
> > > > http://www.tomitribe.com
> > > >
> > > >
> > > > On Fri, Apr 29, 2022 at 5:48 AM Cesar Hernandez <
> > > > cesargu...@gmail.com
> > > > wrote:
> > > >
> > > > > Thank you for the list, Richard,
> > > > >
> > > > > If there is no objection, I propose to create a
> > > > > https://github.com/apache/tomee/javaxToJakartaNamespace.adoc  t
> > > > > o
> > > > > keep
> > > > > track
> > > > > of the shaded versions we currently have, common dependencies
> > > > > that
> > > > > will
> > > > > need to be updated, and strategies to troubleshooting common
> > > > > issues
> > > > > and
> > > > > link to the main epic
> > > > > https://issues.apache.org/jira/browse/TOMEE-3862.
> > > > >
> > > > > WDYT?
> > > > >
> > > > >
> > > > >
> > > > > El mié, 27 abr 2022 a las 0:23, Zowalla, Richard (<
> > > > > richard.zowa...@hs-heilbronn.de>) escribió:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I am not aware of any public reference list. There are some
> > > > > > things,
> > > > > > which floated around the mailing list or in the heads, which
> > > > > > are:
> > > > > >
> > > > > > - Javamail is currently broken. We need to have a jakarta
> > > > > > compatible
> > > > > > version of Geronimo Javamail. This currently breaks 2
> > > > > > examples
> > > > > > and
> > > > > > prevents platform tck from running.
> > > > > >
> > > > > > - Deltaspike / Kratzo examples require dependency upgrades,
> > > > > > i.e.
> > > > > > MVC
> > > > > > 2.0 + Jakarta version of Deltaspike.
> > > > > >
> > > > > > - Micro Profile examples are broken due to the ongoing
> > > > > > integration work
> > > > > > of SmallRye impls. If the integration is done, we can fix
> > > > > > them.
> > > > > >
> > > > > > - If Hibernate is used, we either need to upgrade to 6.0.0
> > > > > > _or_
> > > > > > use the
> > > > > > Jakarta artifact from the 5.6.x series. In some examples, we
> > > > > > still use
> > > > > > Hibernate 4, so the upgrade also requires to deal with
> > > > > > "tomee.jpa.factory.lazy".
> > > > > >
> > > > > > - Check for "http" repositories to avoid the default http
> > > > > > blocker
> > > > > > in
> > > > > > newer Maven versions.
> > > > > >
> > > > > > Gruß
> > > > > > Richard
> > > > > >
> > > > > >
> > > > > > Am Dienstag, dem 26.04.2022 um 21:28 -0600 schrieb Cesar
> > > > > > Hernandez:
> > > > > > > Hi all,
> > > > > > >
> > > > > > > Late last week I started to pick and create sub-task
> > > > > > > related to
> > > > > > > https://issues.apache.org/jira/browse/TOMEE-3862.
> > > > > > > The current CI master status [1] has helped me to identify
> > > > > > > tests that
> > > > > > > need
> > > > > >

Re: TomEE 9.x - from javax to jakarta namespace

[Cesar Hernandez]

I created https://issues.apache.org/jira/browse/TOMEE-3932 and the PR with
the first iteration of the document is ready for review.
https://github.com/apache/tomee/pull/878

El sáb, 30 abr 2022 a las 0:26, Zowalla, Richard (<
richard.zowa...@hs-heilbronn.de>) escribió:

> Sounds good: +1
>
> Am Freitag, dem 29.04.2022 um 11:06 +0200 schrieb Jean-Louis Monteiro:
> > That sounds great Cesar. Thanks
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Fri, Apr 29, 2022 at 5:48 AM Cesar Hernandez  > >
> > wrote:
> >
> > > Thank you for the list, Richard,
> > >
> > > If there is no objection, I propose to create a
> > > https://github.com/apache/tomee/javaxToJakartaNamespace.adoc  to
> > > keep
> > > track
> > > of the shaded versions we currently have, common dependencies that
> > > will
> > > need to be updated, and strategies to troubleshooting common issues
> > > and
> > > link to the main epic
> > > https://issues.apache.org/jira/browse/TOMEE-3862.
> > >
> > > WDYT?
> > >
> > >
> > >
> > > El mié, 27 abr 2022 a las 0:23, Zowalla, Richard (<
> > > richard.zowa...@hs-heilbronn.de>) escribió:
> > >
> > > > Hi,
> > > >
> > > > I am not aware of any public reference list. There are some
> > > > things,
> > > > which floated around the mailing list or in the heads, which are:
> > > >
> > > > - Javamail is currently broken. We need to have a jakarta
> > > > compatible
> > > > version of Geronimo Javamail. This currently breaks 2 examples
> > > > and
> > > > prevents platform tck from running.
> > > >
> > > > - Deltaspike / Kratzo examples require dependency upgrades, i.e.
> > > > MVC
> > > > 2.0 + Jakarta version of Deltaspike.
> > > >
> > > > - Micro Profile examples are broken due to the ongoing
> > > > integration work
> > > > of SmallRye impls. If the integration is done, we can fix them.
> > > >
> > > > - If Hibernate is used, we either need to upgrade to 6.0.0 _or_
> > > > use the
> > > > Jakarta artifact from the 5.6.x series. In some examples, we
> > > > still use
> > > > Hibernate 4, so the upgrade also requires to deal with
> > > > "tomee.jpa.factory.lazy".
> > > >
> > > > - Check for "http" repositories to avoid the default http blocker
> > > > in
> > > > newer Maven versions.
> > > >
> > > > Gruß
> > > > Richard
> > > >
> > > >
> > > > Am Dienstag, dem 26.04.2022 um 21:28 -0600 schrieb Cesar
> > > > Hernandez:
> > > > > Hi all,
> > > > >
> > > > > Late last week I started to pick and create sub-task related to
> > > > > https://issues.apache.org/jira/browse/TOMEE-3862.
> > > > > The current CI master status [1] has helped me to identify
> > > > > tests that
> > > > > need
> > > > > fixes, examples that need dependencies updates to match the
> > > > > javax. ->
> > > > > jakarta , etc.
> > > > >
> > > > > Do we have a place where we can check the list of knowing-Issue
> > > > > and
> > > > > knowing-fixes a contributor can take as a reference when trying
> > > > > to
> > > > > fix a
> > > > > subtask from TOMEE-3862 ?
> > > > > For example, today I faced a javax/servlet issue [2] that
> > > > > required
> > > > > some
> > > > > dependencies replacements like jstl [3 ] with
> > > > > jakarta.servlet.jsp.jstl-api
> > > > > [4] and taglibs:standard [5] with taglibs-shade [6].
> > > > >
> > > > >
> > > > > [1]
> > > > > https://ci-builds.apache.org/job/Tomee/job/master-build-full/
> > > > >
> > > > > [2]
> > > > >
> > > > > Caused by: java.lang.NoClassDefFoundError:
> > > > > javax/servlet/jsp/tagext/TagSupport
> > > > >
> > > > >
> > > > > [3]
> > > > > javax.servlet
> > > > > jstl
> > > > > 1.1.2
> > > > >
> > > > > [4]

Re: Increasing Discard Old Builds strategy in CI

[Cesar Hernandez]

Hello,

I found the post-action "Delete Workspace when build is done", I updated
https://ci-builds.apache.org/job/TomEE/job/master-pull-request/ to check if
this can reduce the job size.
If this doesn't work I'll rollback the change and keep you updated.

[image: image.png]

El mar, 26 abr 2022 a las 13:43, Cesar Hernandez ()
escribió:

> I forgot that /home/jenkins/.m2 is in the Agent and what is actually
> analyzed for the test results are the surefire files as Richard mentioned:
>
> /home/jenkins/jenkins-agent/workspace/Tomee/master-pull-request/
>
>
> I'm +1 on trying a mvn clean as a post step to see if that reduces the
> size of the job result without loosing logs.
>
>
>
>
> El mar, 26 abr 2022 a las 12:52, Cesar Hernandez ()
> escribió:
>
>> In the job, after the test results are executed we can add a post-build
>> doing a:
>> rm -rf /home/jenkins/.m2/
>>
>>
>>
>>
>> El mar, 26 abr 2022 a las 12:51, Zowalla, Richard (<
>> richard.zowa...@hs-heilbronn.de>) escribió:
>>
>>> Afaik Jenkins is parsing the surefire report files. The log files might
>>> also be important for the creator of the PR, so we would need to keep
>>> them too.
>>>
>>> Might be worth a try, I guess.
>>>
>>> Gruß
>>> Richard
>>>
>>> Am Dienstag, dem 26.04.2022 um 11:15 -0700 schrieb David Blevins:
>>> > > On Apr 26, 2022, at 10:47 AM, Zowalla, Richard <
>>> > > richard.zowa...@hs-heilbronn.de> wrote:
>>> > >
>>> > > However, we need to carefully monitor the disk usage / volume used
>>> > > as
>>> > > INFRA has a problem if our used storage volume per jobs exceeds a
>>> > > certain quota.
>>> > >
>>> > > We occupied 1,5T last week (cumulated over a few weeks) and they
>>> > > were a
>>> > > bit mad as the Jenkins CI env went out of storage.
>>> >
>>> > I was going to jump in on that thread and got side tracked.
>>> >
>>> > I wonder if we can do a `mvn clean` or something similar as a post
>>> > build step.  Looks like after a build we have 2.8G used of disk space
>>> > and once we clean that goes down to 398M.
>>> >
>>> > The test case results are the obvious trick.  I'm not sure if Jenkins
>>> > keeps those somewhere else or if we need them to keep living in the
>>> > target directories.  If they need to stay in the target directories
>>> > we can maybe create a script that deletes everything in target/ but
>>> > surefire results.
>>> >
>>> > If we did that, we'd use 1.5 gigabytes for 30 builds vs 10.5
>>> > gigabytes.
>>> >
>>> > Then we could just keep 30 builds regardless of days and it should be
>>> > good.
>>> >
>>> > Thoughts?
>>> >
>>> >
>>> > -David
>>> >
>>>
>>
>>
>> --
>> Atentamente:
>> César Hernández.
>>
>
>
> --
> Atentamente:
> César Hernández.
>


-- 
Atentamente:
César Hernández.

Re: TomEE 9.x - from javax to jakarta namespace

[Cesar Hernandez]

Thank you for the list, Richard,

If there is no objection, I propose to create a
https://github.com/apache/tomee/javaxToJakartaNamespace.adoc  to keep track
of the shaded versions we currently have, common dependencies that will
need to be updated, and strategies to troubleshooting common issues and
link to the main epic https://issues.apache.org/jira/browse/TOMEE-3862.

WDYT?



El mié, 27 abr 2022 a las 0:23, Zowalla, Richard (<
richard.zowa...@hs-heilbronn.de>) escribió:

> Hi,
>
> I am not aware of any public reference list. There are some things,
> which floated around the mailing list or in the heads, which are:
>
> - Javamail is currently broken. We need to have a jakarta compatible
> version of Geronimo Javamail. This currently breaks 2 examples and
> prevents platform tck from running.
>
> - Deltaspike / Kratzo examples require dependency upgrades, i.e. MVC
> 2.0 + Jakarta version of Deltaspike.
>
> - Micro Profile examples are broken due to the ongoing integration work
> of SmallRye impls. If the integration is done, we can fix them.
>
> - If Hibernate is used, we either need to upgrade to 6.0.0 _or_ use the
> Jakarta artifact from the 5.6.x series. In some examples, we still use
> Hibernate 4, so the upgrade also requires to deal with
> "tomee.jpa.factory.lazy".
>
> - Check for "http" repositories to avoid the default http blocker in
> newer Maven versions.
>
> Gruß
> Richard
>
>
> Am Dienstag, dem 26.04.2022 um 21:28 -0600 schrieb Cesar Hernandez:
> > Hi all,
> >
> > Late last week I started to pick and create sub-task related to
> > https://issues.apache.org/jira/browse/TOMEE-3862.
> > The current CI master status [1] has helped me to identify tests that
> > need
> > fixes, examples that need dependencies updates to match the javax. ->
> > jakarta , etc.
> >
> > Do we have a place where we can check the list of knowing-Issue and
> > knowing-fixes a contributor can take as a reference when trying to
> > fix a
> > subtask from TOMEE-3862 ?
> > For example, today I faced a javax/servlet issue [2] that required
> > some
> > dependencies replacements like jstl [3 ] with
> > jakarta.servlet.jsp.jstl-api
> > [4] and taglibs:standard [5] with taglibs-shade [6].
> >
> >
> > [1]
> > https://ci-builds.apache.org/job/Tomee/job/master-build-full/
> >
> > [2]
> >
> > Caused by: java.lang.NoClassDefFoundError:
> > javax/servlet/jsp/tagext/TagSupport
> >
> >
> > [3]
> > javax.servlet
> > jstl
> > 1.1.2
> >
> > [4]
> > jakarta.servlet.jsp.jstl
> > jakarta.servlet.jsp.jstl-api
> > 2.0.0
> >
> > [5]
> > taglibs
> > standard
> > 1.1.2
> >
> > [6]
> > org.apache.tomee
> > taglibs-shade
> > 9.0.0-M8-SNAPSHOT
> >
> >
> > El mié, 30 mar 2022 a las 1:20, Jean-Louis Monteiro (<
> > jlmonte...@tomitribe.com>) escribió:
> >
> > > Thanks Richard.
> > >
> > > I got personal issues with my computer and it's taking a bit of
> > > time to set
> > > everything up again.
> > >
> > >
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
> > >
> > >
> > > On Wed, Mar 30, 2022 at 8:45 AM Zowalla, Richard <
> > > richard.zowa...@hs-heilbronn.de> wrote:
> > >
> > > > Update regarding TOMEE-3879: We were missing --add-opens options
> > > > in the
> > > > failover tests to run with Java 11+ - we added it to the bat / sh
> > > > scripts of openejb-standalone. However, bat / sh is not used in
> > > > the
> > > > failover tests.
> > > >
> > > > I added the options in the tests, so TOMEE-3879 is fixed now.
> > > >
> > > > Gruß
> > > > Richard
> > > >
> > > > Am Dienstag, dem 29.03.2022 um 06:53 + schrieb Zowalla,
> > > > Richard:
> > > > > Hi,
> > > > >
> > > > > to follow up on TOMEE-3879 [1]: I add some more context to the
> > > > > Jira.
> > > > > The permissions do not matter as we are not invoking the
> > > > > scripts in
> > > > > bin/* in the failover itests (itests/failover).
> > > > >
> > > > > We are directly booting the servers via the java command (via
> > > > > Bootstrap
> > > > > from openejb-core) and a lot of properties to confi

Re: OpenJDK is no more?

[Cesar Hernandez]

>
> Eclipse Temurin.


+1

El jue, 28 abr 2022 a las 4:07, Jonathan Gallimore (<
jonathan.gallim...@gmail.com>) escribió:

> +1
>
> On Thu, 28 Apr 2022, 10:19 Jean-Louis Monteiro, 
> wrote:
>
> > Eclipse is fine.
> > Thanks
> >
> > Le jeu. 28 avr. 2022 à 01:22, Jenkins, Rodney J (Rod) <
> > jenki...@nationwide.com> a écrit :
> >
> > > All,
> > >
> > > I was notified of the pull request below.  Long story short:   We need
> to
> > > choose a different JDK to run on our docker images.
> > >
> > > At the moment I'm not sure what all the choices are.   When I looked at
> > > this before, I suggested Eclipse Temurin.
> > >
> > > Does anyone have a preference or others to consider?
> > >
> > > Thanks,
> > > Rod.
> > >
> > >
> > > https://github.com/docker-library/openjdk/pull/495
> > >
> >
>


-- 
Atentamente:
César Hernández.

Re: TomEE 9.x - from javax to jakarta namespace

[Cesar Hernandez]

Hi all,

Late last week I started to pick and create sub-task related to
https://issues.apache.org/jira/browse/TOMEE-3862.
The current CI master status [1] has helped me to identify tests that need
fixes, examples that need dependencies updates to match the javax. ->
jakarta , etc.

Do we have a place where we can check the list of knowing-Issue and
knowing-fixes a contributor can take as a reference when trying to fix a
subtask from TOMEE-3862 ?
For example, today I faced a javax/servlet issue [2] that required some
dependencies replacements like jstl [3 ] with jakarta.servlet.jsp.jstl-api
[4] and taglibs:standard [5] with taglibs-shade [6].


[1]
https://ci-builds.apache.org/job/Tomee/job/master-build-full/

[2]

Caused by: java.lang.NoClassDefFoundError: javax/servlet/jsp/tagext/TagSupport


[3]
javax.servlet
jstl
1.1.2

[4]
jakarta.servlet.jsp.jstl
jakarta.servlet.jsp.jstl-api
2.0.0

[5]
taglibs
standard
1.1.2

[6]
org.apache.tomee
taglibs-shade
9.0.0-M8-SNAPSHOT


El mié, 30 mar 2022 a las 1:20, Jean-Louis Monteiro (<
jlmonte...@tomitribe.com>) escribió:

> Thanks Richard.
>
> I got personal issues with my computer and it's taking a bit of time to set
> everything up again.
>
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Wed, Mar 30, 2022 at 8:45 AM Zowalla, Richard <
> richard.zowa...@hs-heilbronn.de> wrote:
>
> > Update regarding TOMEE-3879: We were missing --add-opens options in the
> > failover tests to run with Java 11+ - we added it to the bat / sh
> > scripts of openejb-standalone. However, bat / sh is not used in the
> > failover tests.
> >
> > I added the options in the tests, so TOMEE-3879 is fixed now.
> >
> > Gruß
> > Richard
> >
> > Am Dienstag, dem 29.03.2022 um 06:53 + schrieb Zowalla, Richard:
> > > Hi,
> > >
> > > to follow up on TOMEE-3879 [1]: I add some more context to the Jira.
> > > The permissions do not matter as we are not invoking the scripts in
> > > bin/* in the failover itests (itests/failover).
> > >
> > > We are directly booting the servers via the java command (via
> > > Bootstrap
> > > from openejb-core) and a lot of properties to configure it, which
> > > fails
> > > (at least for me atm) with a ClassNotFoundException (see issue). Due
> > > to
> > > this exception, the servers never become ready and the tests will
> > > just
> > > timeout.
> > >
> > > Don't have time to dig into it now but hope it helps anyone, who will
> > > work on it in the near future :)
> > >
> > > Gruß
> > > Richard
> > >
> > > [1] https://issues.apache.org/jira/browse/TOMEE-3879
> > >
> > > Am Montag, dem 28.03.2022 um 08:16 + schrieb Zowalla, Richard:
> > > > Heyho,
> > > >
> > > > the ZIP created for TOMEE-3879 looks good to me. It has +x set.
> > > > Perhaps
> > > > it looses the info during extraction in our code.
> > > >
> > > > Can you give a pointer, which tests are suspected to be impacted by
> > > > it?
> > > >
> > > > Gruß
> > > > Richard
> > > >
> > > > Am Samstag, dem 26.03.2022 um 10:40 +0100 schrieb Jean-Louis
> > > > Monteiro:
> > > > > Awesome, divide and conquer.
> > > > >
> > > > > Trying to add a bit more...
> > > > > This one might be small for someone with some spare cycles.
> > > > >
> > > > > https://issues.apache.org/jira/browse/TOMEE-3879
> > > > >
> > > > >
> > > > > --
> > > > > Jean-Louis Monteiro
> > > > > http://twitter.com/jlouismonteiro
> > > > > http://www.tomitribe.com
> > > > >
> > > > >
> > > > > On Sat, Mar 26, 2022 at 5:35 AM David Blevins <
> > > > > david.blev...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > > On Mar 24, 2022, at 2:28 AM, Jean-Louis Monteiro <
> > > > > > jlmonte...@tomitribe.com> wrote:
> > > > > > > We can now divide and conquer. An issue has been created
> > > > > > > https://issues.apache.org/jira/browse/TOMEE-3862
> > > > > > > We are going to add as many small tasks as possible so people
> > > > > > > can
> > > > > > > pick
> > > > > > and
> > > > > > > contribute in parallel.
> > > > > >
> > > > > > Thanks for that JIRA.  I saw an easy one I could do and went a
> > > > > > head
> > > > > > and
> > > > > > knocked it out :)
> > > > > >
> > > > > >  -
> > > > > >
> >
> https://github.com/apache/tomee/commit/6e37ec02ca60fe955a3a909d761e09aa5a506978
> > > > > >
> > > > > > That yanks 1 minute out of the build on my machine.
> > > > > >
> > > > > >
> > > > > > -David
> > > > > >
> > > > > >
> > > > > > > On Tue, Mar 22, 2022 at 1:59 PM Jean-Louis Monteiro <
> > > > > > > jlmonte...@tomitribe.com> wrote:
> > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > I've been working for quite a long time on TomEE 9.x, and
> > > > > > > > it's
> > > > > > > > been more
> > > > > > > > challenging and painful than I was expecting. I thought it
> > > > > > > > would be
> > > > > > good to
> > > > > > > > give you some sort of status.
> > > > > > > >
> > > > > > > > I created a PR for the work. As a reminder, since Java EE
> > > > > > > > moved
> > > > > > > > to
> > > > 

Re: Increasing Discard Old Builds strategy in CI

[Cesar Hernandez]

I forgot that /home/jenkins/.m2 is in the Agent and what is actually
analyzed for the test results are the surefire files as Richard mentioned:

/home/jenkins/jenkins-agent/workspace/Tomee/master-pull-request/


I'm +1 on trying a mvn clean as a post step to see if that reduces the size
of the job result without loosing logs.




El mar, 26 abr 2022 a las 12:52, Cesar Hernandez ()
escribió:

> In the job, after the test results are executed we can add a post-build
> doing a:
> rm -rf /home/jenkins/.m2/
>
>
>
>
> El mar, 26 abr 2022 a las 12:51, Zowalla, Richard (<
> richard.zowa...@hs-heilbronn.de>) escribió:
>
>> Afaik Jenkins is parsing the surefire report files. The log files might
>> also be important for the creator of the PR, so we would need to keep
>> them too.
>>
>> Might be worth a try, I guess.
>>
>> Gruß
>> Richard
>>
>> Am Dienstag, dem 26.04.2022 um 11:15 -0700 schrieb David Blevins:
>> > > On Apr 26, 2022, at 10:47 AM, Zowalla, Richard <
>> > > richard.zowa...@hs-heilbronn.de> wrote:
>> > >
>> > > However, we need to carefully monitor the disk usage / volume used
>> > > as
>> > > INFRA has a problem if our used storage volume per jobs exceeds a
>> > > certain quota.
>> > >
>> > > We occupied 1,5T last week (cumulated over a few weeks) and they
>> > > were a
>> > > bit mad as the Jenkins CI env went out of storage.
>> >
>> > I was going to jump in on that thread and got side tracked.
>> >
>> > I wonder if we can do a `mvn clean` or something similar as a post
>> > build step.  Looks like after a build we have 2.8G used of disk space
>> > and once we clean that goes down to 398M.
>> >
>> > The test case results are the obvious trick.  I'm not sure if Jenkins
>> > keeps those somewhere else or if we need them to keep living in the
>> > target directories.  If they need to stay in the target directories
>> > we can maybe create a script that deletes everything in target/ but
>> > surefire results.
>> >
>> > If we did that, we'd use 1.5 gigabytes for 30 builds vs 10.5
>> > gigabytes.
>> >
>> > Then we could just keep 30 builds regardless of days and it should be
>> > good.
>> >
>> > Thoughts?
>> >
>> >
>> > -David
>> >
>>
>
>
> --
> Atentamente:
> César Hernández.
>


-- 
Atentamente:
César Hernández.

Re: Increasing Discard Old Builds strategy in CI

[Cesar Hernandez]

In the job, after the test results are executed we can add a post-build
doing a:
rm -rf /home/jenkins/.m2/




El mar, 26 abr 2022 a las 12:51, Zowalla, Richard (<
richard.zowa...@hs-heilbronn.de>) escribió:

> Afaik Jenkins is parsing the surefire report files. The log files might
> also be important for the creator of the PR, so we would need to keep
> them too.
>
> Might be worth a try, I guess.
>
> Gruß
> Richard
>
> Am Dienstag, dem 26.04.2022 um 11:15 -0700 schrieb David Blevins:
> > > On Apr 26, 2022, at 10:47 AM, Zowalla, Richard <
> > > richard.zowa...@hs-heilbronn.de> wrote:
> > >
> > > However, we need to carefully monitor the disk usage / volume used
> > > as
> > > INFRA has a problem if our used storage volume per jobs exceeds a
> > > certain quota.
> > >
> > > We occupied 1,5T last week (cumulated over a few weeks) and they
> > > were a
> > > bit mad as the Jenkins CI env went out of storage.
> >
> > I was going to jump in on that thread and got side tracked.
> >
> > I wonder if we can do a `mvn clean` or something similar as a post
> > build step.  Looks like after a build we have 2.8G used of disk space
> > and once we clean that goes down to 398M.
> >
> > The test case results are the obvious trick.  I'm not sure if Jenkins
> > keeps those somewhere else or if we need them to keep living in the
> > target directories.  If they need to stay in the target directories
> > we can maybe create a script that deletes everything in target/ but
> > surefire results.
> >
> > If we did that, we'd use 1.5 gigabytes for 30 builds vs 10.5
> > gigabytes.
> >
> > Then we could just keep 30 builds regardless of days and it should be
> > good.
> >
> > Thoughts?
> >
> >
> > -David
> >
>


-- 
Atentamente:
César Hernández.

Re: Increasing Discard Old Builds strategy in CI

[Cesar Hernandez]

Thank you for the context Richard,
My proposal is for master PR's only since I think this is where most of the
activity is going on at the moment.

We occupied 1,5T last week


In that case, I think a more conservative proposal would be:

Days to keep builds:  8
Max # of builds to keep: 15



El mar, 26 abr 2022 a las 11:47, Zowalla, Richard (<
richard.zowa...@hs-heilbronn.de>) escribió:

> Hi Cesar,
>
> I have no problem with increasing the values for the discard strategy.
> It makes sense to keep it a bit longer for PRs.
>
> However, we need to carefully monitor the disk usage / volume used as
> INFRA has a problem if our used storage volume per jobs exceeds a
> certain quota.
>
> We occupied 1,5T last week (cumulated over a few weeks) and they were a
> bit mad as the Jenkins CI env went out of storage.
>
> Gruß
> Richard
>
>
> Am Dienstag, dem 26.04.2022 um 11:39 -0600 schrieb Cesar Hernandez:
> > Hello,
> >
> > Our current Discard old builds Strategy in CI for PR's for the master
> > branch is [1]:
> > Days to keep builds: 2
> > Max # of builds to keep: 3
> >
> > Is there any objection if I update this to at least:
> > Days to keep builds:  15
> > Max # of builds to keep: 30
> >
> > Currently, if one opens a PR on a Friday and tries to catch up on
> > mid-Monday next week, the PR results are gone.
> > The above proposal will also give us a bit more room for more context
> > on
> > how PR's and past builds have evolved, especially when trying to
> > chase and
> > resolve random test failures.
> >
> >
> > [1]
> > https://ci-builds.apache.org/job/Tomee/job/master-pull-request
>


-- 
Atentamente:
César Hernández.

Increasing Discard Old Builds strategy in CI

[Cesar Hernandez]

Hello,

Our current Discard old builds Strategy in CI for PR's for the master
branch is [1]:
Days to keep builds: 2
Max # of builds to keep: 3

Is there any objection if I update this to at least:
Days to keep builds:  15
Max # of builds to keep: 30

Currently, if one opens a PR on a Friday and tries to catch up on
mid-Monday next week, the PR results are gone.
The above proposal will also give us a bit more room for more context on
how PR's and past builds have evolved, especially when trying to chase and
resolve random test failures.


[1]
https://ci-builds.apache.org/job/Tomee/job/master-pull-request
-- 
Atentamente:
César Hernández.

TOMEE-3905 - Fix Post release pom versioning for tomee-8.x branch

[Cesar Hernandez]

Hi, all!,

I opened https://issues.apache.org/jira/browse/TOMEE-3905 along with
https://github.com/apache/tomee/pull/853 to fix some post-release version
issues.

Notice that even after this TOMEE-3905 , there are two examples that need a
bit of love since they have been commented out of the examples modules for
quite a while. I opened this JIRA in case someone wants to pick them up:


   - examples/applet/  https://issues.apache.org/jira/browse/TOMEE-3906
   - examples/mbean-auto-registration
   https://issues.apache.org/jira/browse/TOMEE-3907



-- 
Atentamente:
César Hernández.

Re: [VOTE] Apache TomEE 8.0.11 - take 2

[Cesar Hernandez]

+1.
Thank you all and congratulations Richard for driving this release!

El jue, 14 abr 2022 a las 9:06, Jean-Louis Monteiro (<
jlmonte...@tomitribe.com>) escribió:

> Hi All,
>
> This is the first attempt at a vote for a release of Apache TomEE 8.0.11
>
> I'd like to start with a big thank you and a big applause to Richard. He
> has been doing a tremendous work on the project and started to roll out his
> first release today. Per Apache rules, the release manager needs to be a
> TomEE PMC, that's why I'm starting this VOTE, but the work has been done by
> Richard, so thank you. Well done.
>
> Maven Repo:
> https://repository.apache.org/content/repositories/orgapachetomee-1200/
>
> Binaries & Sources:
> https://dist.apache.org/repos/dist/dev/tomee/staging-1200/tomee-8.0.11/
>
> Tags:
> https://github.com/apache/tomee/releases/tag/tomee-project-8.0.11
>
> Release notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12351352
>
> Here are the releases notes
> Bug
>
>- [TOMEE-3840 ] -
>TomEE WebProfile 8.0.9 does not start with security enabled
>- [TOMEE-3848 ] -
>Apache TomEE 8.0.6 onwards is packaged with quartz-2.2.4.jar
>- [TOMEE-3860 ] -
>Upgrade jackson-databind for CVE-2020-36518
>- [TOMEE-3871 ] -
>TomEE Plume is missing BatchEE / JCS Cache
>- [TOMEE-3876 ] - BOM
>generation corrupted under windows (slash problems)
>- [TOMEE-3889 ] -
>Invalid ObjectName for MDB listening to wildcard destination
>- [TOMEE-3892 ] -
>TomEE Maven Plugin does not allow to override default "-ea" in
> RemoteServer
>
> Improvement
>
>- [TOMEE-3842 ] -
>GitHub Actions fails for PullRequest Builds due to BOM auto generation
>- [TOMEE-3851 ] -
>Replace Google Analytics with ASF Matomo
>- [TOMEE-3859 ] -
>Update tomee.xml file so it refers to the right location
>
> Task
>
>- [TOMEE-3852 ] -
>Review the website in regard to external embedding of resources (JS,
> Fonts,
>CSS)
>- [TOMEE-3853 ] -
> Link
>ASF Privacy Policy from TomEE Website
>
> Dependency upgrade
>
>- [TOMEE-3841 ] -
>Upgrade SLF4J to 1.7.36
>- [TOMEE-3845 ] -
>Upgrade Tomcat to 9.0.59
>- [TOMEE-3855 ] -
>Upgrade Tomcat to 9.0.60
>- [TOMEE-3856 ] -
>Upgrade to jackson 2.13.2
>- [TOMEE-3858 ] -
>Upgrade OpenJPA to 3.2.2
>- [TOMEE-3872 ] -
>Update Hibernate Integration to 5.6.7
>- [TOMEE-3886 ] -
>Upgrade tomcat to 9.0.62
>- [TOMEE-3893 ] -
>Upgrade to jackson 2.13.2.2
>
> Documentation
>
>- [TOMEE-3814 ] -
>Commented SSL Connector fix for tomee server.xml
>- [TOMEE-3846 ] -
>Inconsistence between tomee flavors comparison in website and actual
> jars
>- [TOMEE-3847 ] -
>Exception when building website from windows os
>- [TOMEE-3854 ] -
>Provide a first draft of a link collection page targeting
>contributor/committer resources
>- [TOMEE-3888 ] -
>Cleanup documentation
>- [TOMEE-3894 ] -
>website generation broken under windows
>
>
> (Developers - please review and adjust your tickets if necessary!)
>
> Please VOTE:
>
> [+1] Yes, release it
> [+0] Not fussed
> [-1] Don't release, there's a showstopper (please specify what the
> showstopper is)
>
> Vote will be open for 72 hours.
>
> Thanks
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>


-- 
Atentamente:
César Hernández.

Re: TOMEE-3846 flavors comparison page / TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache

[Cesar Hernandez]

>
> all the TomEE 7.0 stuff would say "Java EE" not "Jakarta EE" and use
> "Enterprise JavaBeans" not "Jakarta EnterpriseBeans", etc.

Agree, I overlooked the fact that spec names changed along with namespace.



El mar, 12 abr 2022 a las 12:09, Zowalla, Richard (<
richard.zowa...@hs-heilbronn.de>) escribió:

> Makes sense, imho. Thanks for the thoughts, David.
> That would simplify it for the reader.
>
> If we have it per version and link the per version documents from the
> overall comparision, we are proabably in a good shape.
>
>
>
> Am Dienstag, dem 12.04.2022 um 10:58 -0700 schrieb David Blevins:
> > Hey All,
> >
> > I see there's a big thread on PR#37.
> >
> >  - https://github.com/apache/tomee-site-generator/pull/37
> >
> > My gut reaction is that we might be trying to achieve the impossible
> > by trying to fit every TomEE version and every Java EE/Jakarta EE
> > version into one massive matrix or page.
> >
> > What do people think about potentially pausing that, taking a step
> > back and seeing if there's a simpler approach.  Often when I'm
> > working on code and I notice it's getting just too big and hard to
> > fit in my head or on the page in a way that makes sense, I change my
> > approach.  Instead of trying to solve the whole problem at once, I
> > just take a slice of it that I know I'll need and work on it till
> > it's clean.  Then I move on and take another small slice and
> > repeat.  As I keep going I often find there is no more big mess, not
> > because I found a better way to do it, but because I never needed it.
> >
> > My advice would be to give this a try.  Pause the big PR#37 and shift
> > gears.  Instead try nailing just a basic comparison page for TomEE 9
> > that is like the one that's there, but adds the spec versions, links
> > to the spec documents  and the java information.
> >
> > I.e. we copy this page
> >
> >  -
> >
> https://github.com/apache/tomee-site-generator/blob/master/src/main/jbake/content/comparison.adoc
> >
> > To here:
> >
> >  -
> > https://github.com/apache/tomee/commits/master/docs/comparison.adoc
> >
> > Then we start with adding the spec versions and the spec links and
> > get that merged.  Afterwards we try adding the java information, and
> > get that merged.  Once we have a page we all like, we move on and do
> > the same for TomEE 8.0
> >
> >  -
> > https://github.com/apache/tomee/blob/tomee-8.x/docs/comparison.adoc
> >
> > If we have the energy, let's do 7.1 and 7.0 since we're still
> > releasing those once in a while.
> >
> > Each page will be of course only mentioning the specifications they
> > implement.  We can even use the exact spec names as they existed, so
> > for example, all the TomEE 7.0 stuff would say "Java EE" not "Jakarta
> > EE" and use "Enterprise JavaBeans" not "Jakarta EnterpriseBeans",
> > etc.
> >
> > Once we get individual pages for each TomEE version, we will likely
> > have a different perspective on what we need for the main comparison
> > page.  Possibly we'll need very little as the individual pages will
> > be doing most the hard work.
> >
> >
> > Thoughts?
> >
> >
> > -David
> >
> > > On Apr 5, 2022, at 5:42 AM, Swell  wrote:
> > >
> > > Thanks Richard,
> > >
> > > two pages can be pre-reviewed :
> > > • compare-jakarta-versions.html
> > > • comparison.html
> > > i believe we can choose only one of the two for release. which one
> > > do you find more readable ?
> > > (they differ in the detailed list of jakarta specs.)
> > >
> > > i'll try to update my page later to better reflect JRE ranges and
> > > your warnings on JRE/ASM.
> > > i have reflected JL work regarding MicroProfile dependencies in my
> > > draft PR.
> > >
> > >
> > > also we could update TomEE 8.x to MicroProfile 4.1,
> > > (SmallRye?) but is it worth ?
> > >
> > > Swell
> > >
> > > On Tue, 5 Apr 2022 at 11:49, Zowalla, Richard <
> > > richard.zowa...@hs-heilbronn.de> wrote:
> > > Hi Swell,
> > >
> > > > my TomEE 8.x is working on both JDK 11 and 17 with a small app.
> > > > What
> > > features can be broken with wrong JDK/ASM version ?
> > >
> > > (1) If you are running with an unsupported version of ASM the
> > > server
> > > might not startup or the deployment of applications will simply not
> > > work. Most of often this will result in an exception (rather early)
> > > telling you, that ASM does not support this specific version of
> > > Java.
> > >
> > > (2) Our scripts are rather defensively written, but you might
> > > encounter
> > > issues with unsupported JVM flags (between major JDK versions) or
> > > certain other mechanisms do not work (i.e. usages of Unsafe,
> > > Illegal
> > > Reflective Access, etc.)
> > >
> > > Most often this happens with "too new" JDKs (i.e. JDK 18-GA) as we
> > > need
> > > some time to adjust / test or wait for transient libs to be updated
> > > (matter of resources).
> > >
> > > > TomEE works on both JDK and JRE, but can use more memory/cache in
> > > JDK. is this right ? Is JDK to be preferred ?
> > >

Re: [VOTE] Apache TomEE - Jakarta EE API 9.1-M1

[Cesar Hernandez]

+1

El lun, 14 mar 2022 a las 20:05, David Blevins ()
escribió:

> Looks like we still need one more PMC vote to close this.
>
>
> -David
>
> On Mar 1, 2022, at 4:09 AM, Jean-Louis Monteiro 
> wrote:
>
> Hi All,
>
> This is a first attempt at a vote for a release of Apache TomEE /
> jakartaee-api 9.1-M1
> This is essentially the first milestone of the Jakarta EE 9 APIs using the
> new jakarta namespace. It's probably going to move a bit and lead to
> another set of releases to refine it.
>
> Maven Repo:
> https://repository.apache.org/content/repositories/orgapachetomee-1195
>
> Binaries & Source:
>
> https://dist.apache.org/repos/dist/dev/tomee/staging-1195_tomee-jakartaee-api-9.1-M1/
>
> Tags:
> https://github.com/apache/tomee-jakartaee-api/tree/jakartaee-api-9.1-M1
>
> Please VOTE:
>
> [+1] Yes, release it
> [+0] Not fussed
> [-1] Don't release, there's a showstopper (please specify what the
> showstopper is)
>
> Vote will be open for 72 hours.
>
> Thanks
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
>

-- 
Atentamente:
César Hernández.

Re: Re: TomEE Docker image support for arm64?

[Cesar Hernandez]

+1 on the proposal to support arm64 for 8,9 with support for java 8, 11,
and 17.


El mar, 25 ene 2022 a las 8:47, Jonathan Gallimore (<
jonathan.gallim...@gmail.com>) escribió:

> That sounds like a good proposal to me, and I'm happy to help test.
>
> Jon
>
> On Mon, Jan 24, 2022 at 5:28 PM Jenkins, Rodney J (Rod) <
> jenki...@nationwide.com> wrote:
>
> > Hello,
> >
> > I would vote in favor of supporting arm64.  The question for me is how
> > deep do we go?  I propose 8 and 9 with java support for 8, 11, and 17.
> >
> > I will get a branch created so that you can pull it down and test.
> >
> > Thank you,
> > Rod.
> >
> >
> > On 1/24/22, 9:17 AM, "Memo Díaz Solis"  wrote:
> >
> > Nationwide Information Security Warning: This is an EXTERNAL email.
> > Use CAUTION before clicking on links, opening attachments, or responding.
> > (Sender: dev-return-28784-JENKIR14=nationwide@tomee.apache.org)
> >
> >
> >
> --
> >
> >
> > If the community agrees on adding support for arm64 then I can test
> it
> > if
> > you don't mind.
> >
> > El jue, 20 ene 2022 a las 14:24, Jenkins, Rodney J (Rod) (<
> > jenki...@nationwide.com>) escribió:
> >
> > > Hello,
> > >
> > > If the community would like an arm64 build, I would be happy to
> > create
> > > it.  I do not have the ability to test it.
> > >
> > > If we decided on this course, what images do we want to create?   I
> > would
> > > assume 8.x and 9.x.  Would we want to create versions for Java 8,
> > 11, and
> > > 17?  (I would have to look to see what is available.)
> > >
> > >
> > > Thanks,
> > > Rod.
> > >
> > >
> > > On 1/17/22, 4:39 PM, "Cesar Hernandez" 
> wrote:
> > >
> > > Nationwide Information Security Warning: This is an EXTERNAL
> > email.
> > > Use CAUTION before clicking on links, opening attachments, or
> > responding.
> > > (Sender: dev-return-28775-JENKIR14=nationwide@tomee.apache.org
> )
> > >
> > >
> > >
> >
> --
> > >
> > >
> > > Hello,
> > >
> > > I saw Gillermo finding about running TomEE docker image on macs
> > with M1
> > > architecture (arm64)
> > > https://github.com/tomitribe/docker-tomee/issues/58
> > >
> > > I created https://issues.apache.org/jira/browse/TOMEE-3827 to
> > follow
> > > up
> > > this topic since it seems there is a workaround [1] but
> > ultimately I
> > > would
> > > like to know what do you think on adding support for arm64, it
> > seems
> > > Tomcat
> > > already is doing this and our base image (openjdk:8-jre)
> already
> > has
> > > support for it [2]
> > >
> > >
> > >
> > >
> > > [1] https://docs.docker.com/desktop/mac/apple-silicon/
> > > [2] https://hub.docker.com/r/arm64v8/openjdk/
> > > --
> > > Atentamente:
> > > César Hernández.
> > >
> > >
> >
> >
>


-- 
Atentamente:
César Hernández.

TomEE Docker image support for arm64?

[Cesar Hernandez]

Hello,

I saw Gillermo finding about running TomEE docker image on macs with M1
architecture (arm64)
https://github.com/tomitribe/docker-tomee/issues/58

I created https://issues.apache.org/jira/browse/TOMEE-3827 to follow up
this topic since it seems there is a workaround [1] but ultimately I would
like to know what do you think on adding support for arm64, it seems Tomcat
already is doing this and our base image (openjdk:8-jre) already has
support for it [2]




[1] https://docs.docker.com/desktop/mac/apple-silicon/
[2] https://hub.docker.com/r/arm64v8/openjdk/
-- 
Atentamente:
César Hernández.

Re: [VOTE] TomEE Patch plugin 0.8

[Cesar Hernandez]

+1
Thank you Jean-Louis!

El lun, 17 ene 2022 a las 14:08, Jean-Louis Monteiro (<
jlmonte...@tomitribe.com>) escribió:

> Hi!
>
> I’d like to call a VOTE on Apache TomEE Patch Plugin v0.8
>
> Here is the staging repo
> https://repository.apache.org/content/repositories/orgapachetomee-1189
> 
>
> And the source zip which is voted on
>
> https://dist.apache.org/repos/dist/dev/tomee/staging-1189/tomee-patch-parent-0.8-source-release.zip
>
> Git tag
> https://github.com/apache/tomee-patch-plugin/tree/tomee-patch-parent-0.8
>
> My key can be found at
> https://downloads.apache.org/tomee/KEYS
>
> please VOTE
> [+1] all fine, ship it
> [+0] don't care
> [-1] stop, because ${reason}
>
>
> The VOTE is open for at least 72h.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>


-- 
Atentamente:
César Hernández.

Re: [VOTE] Apache TomEE 8.0.9

[Cesar Hernandez]

+1, thank you all for the hard work for this release.

El mié, 29 dic 2021 a las 6:15, Jean-Louis Monteiro (<
jlmonte...@tomitribe.com>) escribió:

> Wow Thanks so much Alexandre.
>
> This is really helpful feedback and a valuable vote.
>
> FYI, I have uploaded the zip files into the dist area again. For some
> reason, last time it failed. Should be better now.
> As Richard mentioned, the staging repo had the right files.
>
> $ svn commit -m "Replace bad zip files"
> > Envoi  apache-tomee-8.0.9-microprofile.zip
> > Envoi  apache-tomee-8.0.9-plume.zip
> > Envoi  apache-tomee-8.0.9-plus.zip
> > Envoi  apache-tomee-8.0.9-webprofile.zip
> > Transmission des données done
> > Transaction de propagation...
> > Révision 51815 propagée.
> >
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Wed, Dec 29, 2021 at 10:54 AM Alex The Rocker 
> wrote:
>
> > Hello,
> >
> > +1 from my side (non-binding) : I have successfully tested TomEE+
> > 8.0.9 (using .tar.gz archive since .zip is broken) with large web app
> > using JAX-RS & JAX-WS, JMS (w and w/o embedded ActiveMQ) and Entity
> > Beans with multiple servers spread on different VMs, on Linux Centos
> > 7.9 with IBM Semeru 11.0.3 (OpenJ9-based Java 11)
> >
> > Also tested with success TomEE+ 8.0.9 with Java 17 (IBM Semeru JRE
> > 17.0.1) on Linux CentOS 7.9 in Docker containers, with a relatively
> > simple web app based on MariaDB database.
> >
> > And tested TomEE 8.0.9 embedded with my basic Arquillian tests on Windows
> > 10.
> >
> > Best regards,
> > Alexandre
> >
> > Le mar. 28 déc. 2021 à 17:56, Alex The Rocker  a
> > écrit :
> > >
> > > Hello,
> > >
> > > Update:
> > > 1. Since ZIP pointed by the announce are corrupted, I used the .tar.gz
> > > archives for my tests.
> > > But I guess that for the vote being meaningful it would make sense
> > > to fix pointed files.
> > >
> > > 2. I see in the body of the 8.0.9 vote mail: "This is a first attempt
> > > at a vote for a release of Apache TomEE 8.0.8."
> > >=> probably a typo, but it's not helping vote clarity... people can
> > > get fooled by reading that body, thinking "heck, it's already
> > > released"
> > >
> > > 3. I've been successfully testing (at basic level) embedded TomEE
> > > 8.0.9 with arquillian, Java 17 (IBM Semeru 17.0.1) on Windows 10 Pro
> > >
> > > 4. I've been successfully deploying a basic web app with TomEE+ 8.0.9
> > > with Java 11 (IBM Semeru 11.0.3) on Linux CentOS 7.9
> > >
> > > 5. I'm building a more complex test with multiple web apps, using
> > > JAX-RS & JAX-WS, JMS (w and w/o embedded ActiveMQ) and Entity Beans
> > > with multiple servers spread on different VMs. I'll have the results
> > > in couple of hours (yes it's a big test)
> > >
> > > 6. I'll also test TomEE+ 8.0.9 in the context of a container-based
> > > app, with IBM Semeru JRE 17.0.1 as the Java runtime => results to come
> > > soon
> > >
> > > Regards,
> > > Alex
> > >
> > > Le mar. 28 déc. 2021 à 15:55, Jean-Louis Monteiro
> > >  a écrit :
> > > >
> > > > Might be the SVN copy and SVN copy with my command. Happy to copy the
> > files
> > > > over again and commit to the dist
> > > >
> > > > Le mar. 28 déc. 2021 à 15:22, Zowalla, Richard <
> > > > richard.zowa...@hs-heilbronn.de> a écrit :
> > > >
> > > > > Looks like it does only impacts the artifacts on dist.a.o
> > > > > Can confirm, that the ZIPs on dist.a.o are broken
> > > > >
> > > > > However, the ZIPs via Maven
> > > > >
> > > > >
> >
> https://repository.apache.org/content/repositories/orgapachetomee-1188/org/apache/tomee/apache-tomee/8.0.9/
> > > > >  look good to me.
> > > > >
> > > > > Gruß
> > > > > Richard
> > > > >
> > > > > Am Dienstag, dem 28.12.2021 um 12:39 +0100 schrieb Alex The Rocker:
> > > > > > Hello Jean-Louis,
> > > > > >
> > > > > > There's a problem with all ZIP archives.
> > > > > > For example
> > > > > >
> > > > >
> >
> https://dist.apache.org/repos/dist/dev/tomee/staging-1188_tomee-8.0.9/apache-tomee-8.0.9-plus.zip
> > > > > > is not a valid ZIP file.
> > > > > > Would you please check ?
> > > > > > (this doesn't seem to impact .tar.gz versions)
> > > > > >
> > > > > > Alex
> > > > > >
> > > > > > Le mar. 28 déc. 2021 à 12:15, Alex The Rocker <
> > alex.m3...@gmail.com>
> > > > > > a écrit :
> > > > > > > Hello Jean-Louis,
> > > > > > >
> > > > > > > I'll check today this 8.0.9 with our apps, sorry for being late
> > - I
> > > > > > > was on vacations!
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Alex
> > > > > > >
> > > > > > > Le mar. 28 déc. 2021 à 12:00, Jean-Louis Monteiro
> > > > > > >  a écrit :
> > > > > > > > Any more votes?
> > > > > > > > --
> > > > > > > > Jean-Louis Monteiro
> > > > > > > > http://twitter.com/jlouismonteiro
> > > > > > > > http://www.tomitribe.com
> > > > > > > >
> > > > > > > >
> > > > > > > > On Thu, Dec 23, 2021 at 3:27 PM Daniel Dias Dos Santos <
> > > > > > > > daniel.dias.analist...@gmail.com> wrote:
> 

Re: [VOTE] Apache tomee-patch-plugin 0.7

[Cesar Hernandez]

+1

El mié, 13 oct 2021 a las 1:24, Jean-Louis Monteiro (<
jlmonte...@tomitribe.com>) escribió:

> +1
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Wed, Oct 13, 2021 at 8:53 AM Zowalla, Richard <
> richard.zowa...@hs-heilbronn.de> wrote:
>
> > +1
> >
> > Am Dienstag, dem 12.10.2021 um 18:39 -0300 schrieb Daniel Dias Dos
> > Santos:
> > > +1
> > >
> > >
> > >
> > > Em ter., 12 de out. de 2021 às 18:31, Jean-Louis Monteiro <
> > > jlmonte...@tomitribe.com> escreveu:
> > >
> > > > Hi!
> > > >
> > > > I’d like to call a VOTE on Apache Johnzon 1.2.15
> > > >
> > > > Here is the staging repo
> > > >
> https://repository.apache.org/content/repositories/orgapachetomee-1187
> > > >
> > > > And the source zip which is voted on
> > > >
> > > >
> >
> https://dist.apache.org/repos/dist/dev/tomee/staging-1187_tomee-patch-plugin-0.7/tomee-patch-parent-0.7-source-release.zip
> > > >
> > > > Git tag
> > > >
> > https://github.com/apache/tomee-patch-plugin/tree/tomee-patch-parent-0.7
> > > >
> > > > My key can be found at
> > > > https://downloads.apache.org/tomee/KEYS
> > > >
> > > > please VOTE
> > > > [+1] all fine, ship it
> > > > [+0] don't care
> > > > [-1] stop, because ${reason}
> > > >
> > > > The VOTE is open for 72h.
> > > > --
> > > > Jean-Louis Monteiro
> > > > http://twitter.com/jlouismonteiro
> > > > http://www.tomitribe.com
> > > >
> > --
> > Richard Zowalla, M.Sc.
> > Research Associate, PhD Student | Medical Informatics
> >
> > Hochschule Heilbronn – University of Applied Sciences
> > Max-Planck-Str. 39
> > D-74081 Heilbronn
> > phone: +49 7131 504 6791 (zur Zeit nicht via Telefon erreichbar)
> > mail: richard.zowa...@hs-heilbronn.de
> > web: https://www.mi.hs-heilbronn.de/
> >
>


-- 
Atentamente:
César Hernández.

Re: TomEE Jakarta project - have we reach the limit?

[Cesar Hernandez]

>
> IMO the following is the best way:
> - branch 8.0.x
> - make master 9.0 and rename javax -> jakarta
> - branch 9.0 after everything is working fine
> - working on 10.0 in master
> - maintain 8.0 and 10.0 and dont maintain the 9.0 branch


+1

 In terms of how we handle 9.x, I think we'd want to stay on top of any
> CVEs in that release for at least 6 months after 10 goes final so people
> have at least a little time to transition

+1

By merging both opinions above,  the following would be a potential set of
steps:

- branch 8.0.x
- make master 9.0 and rename javax -> jakarta
- maintain 8.0 and 9.0 (master)
- When 10 is out, keep 10 in master and branch 9.0.
- Maintain 8, 9, and master (10)


El mar, 5 oct 2021 a las 15:31, David Blevins ()
escribió:

> > On Oct 5, 2021, at 1:59 AM, Thomas Andraschko <
> andraschko.tho...@gmail.com> wrote:
> >
> > yep
> > i think we have to maintain 8.0.x anyway as its the last javax release
> and
> > we cant expect that everyone does a fast migration
> >
> > IMO the following is the best way:
> > - branch 8.0.x
> > - make master 9.0 and rename javax -> jakarta
> > - branch 9.0 after everything is working fine
> > - working on 10.0 in master
> > - maintain 8.0 and 10.0 and dont maintain the 9.0 branch
>
> Agree with making 8 be the branch and 9 be main/master.  In terms of how
> we handle 9.x, I think we'd want to stay on top of any CVEs in that release
> for at least 6 months after 10 goes final so people have at least a little
> time to transition over.
>
>
> -David
>
>
> >
> >
> > Am Di., 5. Okt. 2021 um 10:53 Uhr schrieb Jean-Louis Monteiro <
> > jlmonte...@tomitribe.com>:
> >
> >> Agreed ...
> >>
> >> 1.7.x - EOL
> >> 7.0.x and 7.1.x - mostly similar so if we maintain one, we should
> maintain
> >> the other.
> >>
> >> But I agree that 1 actively developed version (TomEE master/TomEE 9.x)
> and
> >> 1 maintained version (TomEE 8.x) is good.
> >> That'd be my choice.
> >> --
> >> Jean-Louis Monteiro
> >> http://twitter.com/jlouismonteiro
> >> http://www.tomitribe.com
> >>
> >>
> >> On Tue, Oct 5, 2021 at 10:37 AM Zowalla, Richard <
> >> richard.zowa...@hs-heilbronn.de> wrote:
> >>
> >>> +1
> >>>
> >>> I am wondering, if we still maintain 7.0.x, 7.1.x in the future (1.7.x
> >>> is eol, I guess) ? Maintenance cost will rise with every additional
> >>> version branch. The last releases of 7.0.x and 7.1.x are 1 year old...
> >>> but this is maybe another discussion.
> >>>
> >>>
> >>> Am Dienstag, dem 05.10.2021 um 10:05 +0200 schrieb Jean-Louis Monteiro:
>  Thanks everyone.
> 
>  Same feeling here.
>  I think we tried and pushed it as much as we could.
> 
>  What we can do is make sure we fix remaining failures on TCK and
>  support
>  JDK 17 with TomEE.
>  Do a release, branch for maintenance and move master to jakarta.
> 
>  Does it sound like an acceptable plan?
> 
>  --
>  Jean-Louis Monteiro
>  http://twitter.com/jlouismonteiro
>  http://www.tomitribe.com
> 
> 
>  On Tue, Oct 5, 2021 at 7:56 AM David Jencks  >
>  wrote:
> 
> > Maybe even “Our second release _confirmed_…”…
> >
> > David Jencks
> >
> >> On Oct 4, 2021, at 12:33 PM, David Blevins <
> >> david.blev...@gmail.com>
> > wrote:
> >>> - Our first release proved releasing both 8 & 9 together can be
> > impractical.  The TomEE 8 binaries were a dud, only TomEE 9 was
> > released.
> > There was communication overhead and made for a potentially
> > confusing
> > release.  The TomEE 9 binaries are still very limited.
> >>> - Our first release proved releasing both 8 & 9 together can be
> > impractical.  The TomEE 8 binaries were released, we didn't release
> > TomEE
> > 9.  It's the second time we've done that.  We've only managed one
> > TomEE 9
> > release in the last 10 months.
> >> This was supposed to start "our second
> >> release".  CopyPasteException :)
> >>
> >> -David
> >>
> >>> --
> >>> Richard Zowalla, M.Sc.
> >>> Research Associate, PhD Student | Medical Informatics
> >>>
> >>> Hochschule Heilbronn – University of Applied Sciences
> >>> Max-Planck-Str. 39
> >>> D-74081 Heilbronn
> >>> phone: +49 7131 504 6791 (zur Zeit nicht via Telefon erreichbar)
> >>> mail: richard.zowa...@hs-heilbronn.de
> >>> web: https://www.mi.hs-heilbronn.de/
> >>>
> >>
>
>

-- 
Atentamente:
César Hernández.

Re: [VOTE] Apache TomEE 8.0.8

[Cesar Hernandez]

+1 (plus one) thank you!

El mié, 1 sept 2021 a las 20:03, Luis Ventocilla ()
escribió:

> +1
>
> On Wed, Sep 1, 2021 at 8:57 PM Daniel Dias Dos Santos <
> daniel.dias.analist...@gmail.com> wrote:
>
> > +1
> >
> > Em qua., 1 de set. de 2021 às 11:48, Zowalla, Richard <
> > richard.zowa...@hs-heilbronn.de> escreveu:
> >
> > > Hi,
> > >
> > > +1 from my side.
> > >
> > > I tested the 8.0.8 plus artifact with our fullstack EAR app (jpa,
> > > jaxrs, jsf).
> > >
> > > Thanks, JL for preparing this release artifact :)
> > >
> > > Gruss
> > > Richard
> > >
> > >
> > > Am Mittwoch, dem 01.09.2021 um 15:49 +0200 schrieb Jean-Louis Monteiro:
> > > > Hi All,
> > > >
> > > > This is a first attempt at a vote for a release of Apache TomEE
> > > > 8.0.8.
> > > >
> > > > Maven Repo:
> > > >
> https://repository.apache.org/content/repositories/orgapachetomee-1186
> > > >
> > > > Binaries & Source:
> > > > https://dist.apache.org/repos/dist/dev/tomee/staging-1186/
> > > >
> > > > Tags:
> > > > https://github.com/apache/tomee/tree/tomee-project-8.0.8
> > > >
> > > > Release notes:
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12350177=Html=12312320
> > > >
> > > > Here is an adoc generated version (Thanks Richard)
> > > >
> > > > > = Apache TomEE 8.0.8 Release Notes
> > > > > :index-group: Release Notes
> > > > > :jbake-type: page
> > > > > :jbake-status: published
> > > > > == Dependency upgrade
> > > > > [.compact]
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-2990[TOMEE-2990]
> > > > > BatchEE 0.6
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-3750[TOMEE-3750]
> > > > > BatchEE 1.0.0
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-2987[TOMEE-2987] CXF
> > > > > 3.4.3
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-3756[TOMEE-3756]
> > > > > HSQLDB 2.3.4
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-3772[TOMEE-3772]
> > > > > JUnit 4.13.2
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-3734[TOMEE-3734]
> > > > > Johnzon 1.2.11
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-3755[TOMEE-3755]
> > > > > Johnzon 1.2.13
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-3770[TOMEE-3770]
> > > > > Johnzon 1.2.14
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-3732[TOMEE-3732]
> > > > > MyFaces 2.3.9
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-3753[TOMEE-3753]
> > > > > OpenJPA 3.2.0
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-2997[TOMEE-2997]
> > > > > OpenSAML V3.4.6
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-2809[TOMEE-2809]
> > > > > OpenWebBeans 2.0.22
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-2998[TOMEE-2998]
> > > > > Tomcat 9.0.45
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-3760[TOMEE-3760]
> > > > > Tomcat 9.0.48
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-3773[TOMEE-3773]
> > > > > Tomcat 9.0.50
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-3787[TOMEE-3787]
> > > > > Tomcat 9.0.52
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-2939[TOMEE-2939]
> > > > > bcprov-jdk15on 1.67
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-3765[TOMEE-3765]
> > > > > bountycastle 1.69
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-3764[TOMEE-3764]
> > > > > commons-dbcp 2.3.0
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-3759[TOMEE-3759]
> > > > > commons-io 2.10.0
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-2972[TOMEE-2972]
> > > > > latest OWB version run on Java16
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-2988[TOMEE-2988]
> > > > > xbean 4.18+ (Java 16 support)
> > > > > == New Feature
> > > > > [.compact]
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-3730[TOMEE-3730] Add
> > > > > JSONP and JSONB Providers JAX-RS Client
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-2365[TOMEE-2365]
> > > > > Implement Java EE Security API from EE 8
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-2966[TOMEE-2966]
> > > > > Provide a pure JUnit5 OpenEJB Extension
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-2977[TOMEE-2977]
> > > > > Provide a ApplicationComposer JUnit 5 Extension
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-2993[TOMEE-2993] API
> > > > > pom for each TomEE distribution
> > > > > == Bug
> > > > > [.compact]
> > > > >  - link:
> > > > > https://issues.apache.org/jira/browse/TOMEE-3774[TOMEE-3774]
> > > > > Problems with master branch in Windows 10
> > > > >  - link:
> > > > > 

Re: Issue with a docker image

[Cesar Hernandez]

Hi Rodney,

Thank you for the notice. The repo now have github issues enable.

El jue, 1 jul 2021 a las 8:42, Jenkins, Rodney J (Rod) (<
jenki...@nationwide.com>) escribió:

> Hello all,
>
> Someone was unable to open an issue on
> https://github.com/tomitribe/docker-tomee.  Two things….
>
>
>   1.  Can we allow the creation of issues for that repo?
>   2.  Can someone look in to it?  I think it is something very simple.
>
> I would look into it, but I am out of the office until next week.  If it
> is not resolved by then, I will look at it then.
>
> Thanks,
> Rod.
>
>

-- 
Atentamente:
César Hernández.

Re: Updated Contributors list

[Cesar Hernandez]

Nice work David and Richard!
As of today, the page shows 100+ contributors :)


El vie, 21 may 2021 a las 22:22, David Blevins ()
escribió:

> Richard and I collaborated over on Slack to fix the broken contributors
> page.  What do you think?
>
>  - http://tomee.apache.org/community/contributors.html *
>
> Props go to Richard for getting this moving and fixing up the html/css.
>
> The list is contributions across all our repos, sorted by a combination of
> commits, lines added and lines removed.  If you contribute to any of our
> repos, you go up the list.
>
> * site-publish was still running when this email was sent, but should be
> done in 20 minutes
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
>

-- 
Atentamente:
César Hernández.

Re: Automatic website publishing

[Cesar Hernandez]

>
> FYI, Cesar, your test didn't work because you need to select
> `git-websites` as the node.  That has the credentials setup and permissions
> to publish to an `asf-site` or `asf-staging-*` branch.


Thank you for the update. I'm deleting now the test-pipeline to clear out
our current number of jenkis jobs.


El jue, 20 may 2021 a las 2:01, Zowalla, Richard (<
richard.zowa...@hs-heilbronn.de>) escribió:

> Great news :) - definitly an important improvement for website / doc
> contributions!
>
>
> Am Mittwoch, den 19.05.2021, 20:36 -0700 schrieb David Blevins:
> > Thanks, David and Cesar!
> >
> > The Jenkins part is working.  My tests runs that pushed to `asf-site`
> > all worked and since the last email I've completed it and we now have
> > automated publishing to the `asf-site` branch.  The job is setup to
> > run daily, but any of us can click the 'Build Now' button at any time
> > if you're impatient.
> >
> >   -
> >
> https://github.com/apache/tomee-site-pub/commit/3409970cd9cd0dbf806da49ff9edc0c37d152e46
> >
> > FYI, Cesar, your test didn't work because you need to select `git-
> > websites` as the node.  That has the credentials setup and
> > permissions to publish to an `asf-site` or `asf-staging-*` branch.
> >
> > What doesn't work is that our website was setup to use `master` not
> > `asf-site`, so after the switch from `master` to `asf-site` updates
> > do not reach https://tomee.apache.org.
> >
> > I filed a ticket (INFRA-21903).  I worked a bit with @fluxo on
> > #asfinfra and neither of us were able to figure it out.  I suspect
> > @Humbedooh will get it resolved.
> >
> > The good news is that when he does, we're completely setup for
> > automated publishes to the website!
> >
> --
> Richard Zowalla, M.Sc.
> Research Associate, PhD Student | Medical Informatics
>
> Hochschule Heilbronn – University of Applied Sciences
> Max-Planck-Str. 39
> D-74081 Heilbronn
> phone: +49 7131 504 6791 (zur Zeit nicht via Telefon erreichbar)
> mail: richard.zowa...@hs-heilbronn.de
> web: https://www.mi.hs-heilbronn.de/
>


-- 
Atentamente:
César Hernández.

Re: Potential new home page

[Cesar Hernandez]

Great website refresh!
Congratulation and thank you.


El jue, 20 may 2021 a las 15:14, David Blevins ()
escribió:

> > On May 20, 2021, at 1:00 AM, Zowalla, Richard <
> richard.zowa...@hs-heilbronn.de> wrote:
> >
> > Hi,
> >
> > looks good :)
>
> Glad you like it!  Ryan and Andrii do great work :)
>
> > - Documentation is empty / seems to be broken on the staging
> > environment. Is this intentional?
>
> Yes, I just generated enough of the site to show the front-page and
> generally how things look as generating the full site takes a long time.
>
>
> -David
>
>

-- 
Atentamente:
César Hernández.

Re: Automatic website publishing

[Cesar Hernandez]

Hi David,

I tried to do these steps using jenkins pipeline with a test job here:
https://ci-builds.apache.org/job/Tomee/job/test-pipeline/
The problem [1] I'm getting seems to be related to the fact that the CI
user doesn't have write access to the repo:

"remote: Permission to apache/tomee-site-pub.git denied to . "


[1]

+ git commit -m test publish from ci-builds.apache.org using jenkins
[asf-staging-test 678b293a4] test publish from ci-builds.apache.org
using jenkins
 1 file changed, 1 insertion(+), 1 deletion(-)[Pipeline]
withCredentials
Masking
supported pattern matches of $GIT_USERNAME or $GIT_PASSWORD[Pipeline]
{ 
[Pipeline]
sh 

+ git push origin HEAD:asf-staging-test
remote: Permission to apache/tomee-site-pub.git denied to .
fatal: unable to access 'https://github.com/apache/tomee-site-pub/':
The requested URL returned error: 403[Pipeline] }[Pipeline] //
withCredentials[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline]
// node[Pipeline] End of PipelineERROR: script returned exit code 128
Finished: FAILURE




El mié, 19 may 2021 a las 19:03, David Blevins ()
escribió:

> I've been trying to setup automatic website publishing.
>
> So far I have a test Jenkins job that does a simple commit/push:
>
>  - https://ci-builds.apache.org/job/Tomee/job/site-publish
>
> At the moment it's just a simple Freestyle job with a test script to see a
> successful commit/push work:
>
> git clone https://gitbox.apache.org/repos/asf/tomee-site-pub.git -b
> asf-staging-test
> cd tomee-site-pub
> date > test.txt
> git add test.txt
> git commit -m "test publish from ci-builds.apache.org" test.txt
> git push origin asf-staging-test
>
> The trick and where I'm stuck is that we're using `master` as our main
> branch for https://tomee.apache.org and Jenkins is setup to only let us
> push a branch called `asf-site` or `asf-staging-*`
>
> I've attempted to switch `tomee-site-pub` from `master` to `asf-site`, but
> it doesn't seem to work.  I've filed a ticket with Infra and will keep you
> updated:
>
>  - https://issues.apache.org/jira/browse/INFRA-21903
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
>

-- 
Atentamente:
César Hernández.

Re: [VOTE] Release Apache TomEE 8.0.7 and 9.0.0-M7

[Cesar Hernandez]

+1 (binding)
We can add a Note in the download section for TomEE 8.0.7 and in parallel
working on the fixes to then release  8.0.8. We have been doing this for 9
milestones.
Up to this point we have been seen and living the benefits of the patch and
transformer plugging, this time I think we can add the note for 8.0.7 so
when 8.0.8 is release we are back on track.

El lun, 3 may 2021 a las 11:31, Zowalla, Richard (<
richard.zowa...@hs-heilbronn.de>) escribió:

> Hi Alex,
>
> I guess, that the links got mixed up.
>
> The 8.0.7 binaries are in the 1182 repo:
>
>
> https://repository.apache.org/content/repositories/orgapachetomee-1182/org/apache/tomee/apache-tomee/
>
> Gruss
> Richard
>
> Am Montag, den 03.05.2021, 19:24 +0200 schrieb Alex The Rocker:
> > Hello,
> >
> > I haven't found 8.0.7 binaries (only binaries at 9.0.0M7 link), is
> > that intentional ?
> >
> > Alex
> >
> > Le lun. 3 mai 2021 à 17:01, David Blevins  a
> > écrit :
> > > Ok, folks,
> > >
> > > Here we go.  Again, bear in mind we need these binaries for the
> > > Jakarta EE 9.1 release ballot today.  Any issues and we can roll a
> > > Apache TomEE 8.0.8 and Apache TomEE 9.0.0-M8 asap.  I think we
> > > should plan on doing that anyway, so feel free to say call it
> > > straight out when reporting "I found x issue we should fix in
> > > 8.0.8"
> > >
> > >
> > > TomEE Patch Plugin v0.5
> > >
> https://repository.apache.org/content/repositories/orgapachetomee-1182/
> > >
> > > Apache TomEE 8.0.7
> > >
> https://repository.apache.org/content/repositories/orgapachetomee-1183/
> > >
> > > Apache TomEE 9.0.0-M7
> > >
> https://repository.apache.org/content/repositories/orgapachetomee-1184/
> > >
> > > This vote will be open for 72 hours.  Please vote +1, 0, -1.  When
> > > voting -1, please state the reason.
> > >
> > >
> > >
> > > --
> > > David Blevins
> > > http://twitter.com/dblevins
> > > http://www.tomitribe.com
> > >
> --
> Richard Zowalla, M.Sc.
> Research Associate, PhD Student | Medical Informatics
>
> Hochschule Heilbronn – University of Applied Sciences
> Max-Planck-Str. 39
> D-74081 Heilbronn
> phone: +49 7131 504 6791 (zur Zeit nicht via Telefon erreichbar)
> mail: richard.zowa...@hs-heilbronn.de
> web: https://www.mi.hs-heilbronn.de/
>


-- 
Atentamente:
César Hernández.

TOMEE-3733 - Results page for website

[Cesar Hernandez]

Hi,

I started to work on the website to add a new page to display the Jakarta
EE TCK summary results base
on the  information required by Eclipse Foundation Technology Compatibility
Kit License [1]
I just created  https://issues.apache.org/jira/browse/TOMEE-3733 and PR is
also available with the first
iteration: https://github.com/apache/tomee-site-generator/pull/22

As a side note, at the beginning I struggle a bit trying to run locally the
project
https://github.com/apache/tomee-site-generator/ because when I tried to run
 mvn compile -Djbake.http=true
the server failed to start with java.lang.IllegalArgumentException
at org.apache.xbean.asm5.ClassReader exception [2]

To fix this I had to downgrade the tika-parsers from 1.25 to 1.17 because
according
to 1.17 release note [3] the project dropped support for Java 7 around that
version.
I made sure that download-ng.java worked fine before and after the change
so no regressions were
introduced by downgrading the tika-parsers since the jar is only used when
running
org.apache.tomee.website.DownloadsNG.java standalone runner.


[1]
https://www.eclipse.org/legal/tck.php

[2]
java.lang.IllegalArgumentException: java.lang.IllegalArgumentException
at org.apache.tomee.embedded.Container.deploy(Container.java:272)
at
org.apache.tomee.embedded.Container.deployPathsAsWebapp(Container.java:228)
at
org.apache.tomee.embedded.Container.deployClasspathAsWebApp(Container.java:193)
at
org.apache.tomee.embedded.Container.deployClasspathAsWebApp(Container.java:173)
at
org.apache.tomee.embedded.Container.deployClasspathAsWebApp(Container.java:164)
at org.apache.tomee.website.JBake.main(JBake.java:174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:282)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException
at org.apache.xbean.asm5.ClassReader.(Unknown Source)
at org.apache.xbean.asm5.ClassReader.(Unknown Source)
at org.apache.xbean.asm5.ClassReader.(Unknown Source)
at
org.apache.xbean.finder.AnnotationFinder.readClassDef(AnnotationFinder.java:1169)
at
org.apache.xbean.finder.AnnotationFinder.(AnnotationFinder.java:147)
at
org.apache.xbean.finder.AnnotationFinder.(AnnotationFinder.java:160)
at
org.apache.openejb.config.FinderFactory$OpenEJBAnnotationFinder.(FinderFactory.java:546)
at org.apache.tomee.embedded.Container.deploy(Container.java:268)

[3]
https://archive.apache.org/dist/tika/CHANGES-1.17.txt
-- 
Atentamente:
César Hernández.

Re: Permanently Fixing examples after library upgrades

[Cesar Hernandez]

+1 for the generated BOM's.
I see there is another thread with already work in progress [1] So I'll
follow up there since one of the tests I want to make is to perform a
maven release:prepare and check if the versions from the Examples (with our
without Boom) are all updated.

[1]
https://lists.apache.org/thread.html/r4ba417fe29a55e45bee4feb33ba646331aaf4289ba0654062c1a0a36%40%3Cdev.tomee.apache.org%3E

El sáb, 3 abr 2021 a las 12:55, Daniel Dias Dos Santos (<
daniel.dias.analist...@gmail.com>) escribió:

> Hello David,
>
> +1 for the idea, it will help a lot.
>
> thanks
>
>
>
>
> Em sáb., 3 de abr. de 2021 às 06:37, Zowalla, Richard <
> richard.zowa...@hs-heilbronn.de> escreveu:
>
> > Hi David,
> >
> > thanks for the this thread!
> >
> > I like the idea of using the generated BOMs in our examples rather than
> > adding libraries by hand (and updating them all the time).
> >
> > Sometimes it will be necassary to still add some additional libs in the
> > examples, but overall it will make it easier to maintain the examples
> > (as long as we get the habit of regenerating the BOMs after library
> > updates).
> >
> > Related to the "*-api" idea: Probably yes. Would be somehow natural to
> > have an "api" and an "impl"-thing (even if it not called impl).
> >
> > I just tested it locally with one of the failing tests and it worked
> > perfectly.  So I am +1 here.
> >
> > Gruss
> > Richard
> >
> > Am Freitag, den 02.04.2021, 15:09 -0700 schrieb David Blevins:
> > > Richard mentioned some examples were broken after a recent library
> > > upgrade and I promised to start a thread on the topic as we have
> > > system issues there.
> > >
> > > One of the things that's aways bugged me and was on the "some day"
> > > list is that in our examples we are encouraging people to have to
> > > know how to put together the right dependencies to get a working
> > > container for plain unit testing.
> > >
> > > Some examples show `openejb-core` and `javaee-api`, some show
> > > `openejb-cxf-rs`, some show just `openejb-cxf`, some show `tomee-
> > > jaxrs`, some also pull in specific dependencies like `cxf-rt-rs-
> > > client`, some add a specific MicroProfile API.
> > >
> > > None of this documented anywhere, you just have to "know".  And any
> > > time we upgrade our dependencies, users must upgrade theirs.   Any
> > > time we change our excludes or mark things provided, users need to
> > > add dependencies they weren't informed they now need.  We're setting
> > > people up for failure and frustration.  Side note, this is one of the
> > > reasons I really like having the examples in the main codebase as it
> > > helps to keep us honest -- we experience the same things in our build
> > > users experience in theirs.
> > >
> > > Some months back I wrote some code that will inspect a TomEE server
> > > zip and generate a pom from it.  The poms have zero transitive
> > > dependencies, every dependency is explicitly listed and it is
> > > therefore library to library identical to the zip, but usable as a
> > > plain maven dependency.  There is one for each of our servers:
> > >
> > >   
> > > org.apache.tomee.bom
> > > tomee-webprofile
> > > 8.0.7-SNAPSHOT
> > >   
> > >   
> > > org.apache.tomee.bom
> > > tomee-microprofile
> > > 8.0.7-SNAPSHOT
> > >   
> > >   
> > > org.apache.tomee.bom
> > > tomee-plus
> > > 8.0.7-SNAPSHOT
> > >   
> > >   
> > > org.apache.tomee.bom
> > > tomee-plume
> > > 8.0.7-SNAPSHOT
> > >   
> > >
> > > I recommend we take this opportunity to go through all the examples
> > > and replace the use of individual TomEE dependencies in favor of one
> > > of the dependencies above.  Once we've done that, the odds of our
> > > users or our examples being affected by library changes drops
> > > significantly.
> > >
> > > In writing this, the one gap I see is that we probably want an
> > > equivalent API pom for each server dist.  Our examples tend to have
> > > javaee-api marked as scope `provided` and the server jars marked with
> > > scope `test` so code in `src/main/java` isn't depending on our
> > > internals.  We could have an additional "api" pom that contains the
> > > javaee-api jar, all microprofile-*.jar api jars and any API jars we
> > > provide ourselves (at the moment that's just openejb-api.jar).
> > >
> > > That might give us examples that look like this in practice:
> > >
> > >   
> > > org.apache.tomee.bom
> > > tomee-microprofile-api
> > > 8.0.7-SNAPSHOT
> > > provided
> > >   
> > >   
> > > org.apache.tomee.bom
> > > tomee-microprofile
> > > 8.0.7-SNAPSHOT
> > > test
> > >   
> > >
> > > It's tempting to think, "maybe the second dependency should have an
> > > 'impl' suffix?"  I asked myself, thought through it and came out on
> > > the "no" side.  There will be people who just want the 

Re: [VOTE] Apache TomEE on Jakarta EE Compatible Products page

[Cesar Hernandez]

+1 for Option A, since this enables smooth understanding and navigation for
users and developers over ASF projects and their compatibility over
JakartaEE.
Having this bridge between the ASF project and Jakarta EE would be a good
synergy in the ecosystem.

El dom, 28 mar 2021 a las 2:27, Alex The Rocker ()
escribió:

> +1 for Option A : it think it would be a nice way to promote TomEE to
> a large audience, while not involving too much overhead since, as I
> understand, TomEE developers are already using TCK tests for
> validation purposes.
>
> Le dim. 28 mars 2021 à 01:05, David Blevins  a
> écrit :
> >
> > Please see Rob Tompkins' email "[jarkarta-ee] Is there apatite to ever
> use Jakarta EE logos on the TomEE site"
> >
> > This vote is strictly limited to 1) getting Jakarta EE Platform and
> Jakarta EE Web Profile implementations at the ASF listed on the jakarta.ee
> compatible products page[1] and 2) use of the "Jakarta EE Compatible"[2]
> logo on apache.org websites.
> >
> > The rules for either of these require you to be a member of the Jakarta
> EE Working Group.
> >
> > As I've been on the Working Group from the start and knew this would be
> affecting us as Apache is is not a member of the Working Group, I've
> ensured we have two options.  The vote is to gather feedback on which of
> the two options you prefer.
> >
> >  - Option A: Apache joins the Jakarta EE Working Group and gains the
> ability to get Apache TomEE and any other ASF Jakarta EE Platform and
> Jakarta EE Web Profile implementations listed on the compatible products
> page[1].  As a Member, Apache TomEE and any other ASF Jakarta EE Platform
> and Jakarta EE Web Profile implementations can use the "Jakarta EE
> Compatible"[2] logo on tomee.apache.org and other *.apache.org sites.  In
> this path the TCK results summary of tests passed must be hosted on
> tomee.apache.org for each certified server version, tck version, jdk and
> os combination.  The entry for Apache TomEE on the jakarta.ee website
> will contain one link to tomee.apache.org for the TCK results summary and
> one link to download Apache TomEE at tomee.apache.org.
> >
> >  - Option B: Apache does not join, however, Strategic Members of the
> Jakarta EE Working Group could get Apache TomEE listed on the compatible
> products page[1] as an open source implementation they support.  As Apache
> is not itself a member, we would not be able to use the "Jakarta EE
> Compatible"[2] logo on tomee.apache.org.  We could use the general
> Jakarta EE logo, however.  In this path the project does not need to host
> TCK result summaries on tomee.apache.org.  The entry for Apache TomEE on
> the jakarta.ee website will contain one link to said Strategic Member's
> website for the TCK results summary and one link to download Apache TomEE
> at tomee.apache.org.
> >
> > I'm confident we can make either work.
> >
> > This vote will close on April 14th so Rob can make his recommendation to
> the Board in time for the April 21st Board Meeting.  Additionally, the
> Jakarta EE 9.1 release is scheduled to go up for vote end of April and
> there is some chance we could be compatible by then.
> >
> > Note: Even if we vote A, that does not guarantee Apache will join the
> Working Group.  It would just be an indication that's what we desire.  The
> desires of all projects and the foundation in general will be considered
> and it's ultimately Rob and the Board who make this decision.
> >
> >
> > -David
> >
> >
> > [1] https://jakarta.ee/compatibility/
> > [2]
> https://jakarta.ee/images/jakarta/jakarta-ee-compatible-logo-color.svg
>


-- 
Atentamente:
César Hernández.

Re: TomEE-2966: JUnit5 OpenEJB Extension Module - Any thoughts?

[Cesar Hernandez]

Hi,

As a follow-up, I identified that the space in the "Pull Request" Jenkins
job name may have been the issue on the failing test [1] we have been
seeing in PR's results.

I made local tests for tomee/examples/webservice-ssl-client-cert and I just
renamed the job and trigger a rebuild:
https://ci-builds.apache.org/job/TomEE/job/pull-request/
If this fixes the issue we can also scape quotes in the Keystore and key
generation that occurs during the integration between the ant run and shell
script generateKeyPair.bat and generateServerKey.bat. But let's see first
the result we get.

[1]
..
/home/jenkins/jenkins-agent/workspace/Tomee/*Pull Requests*
/examples/webservice-ssl-client-cert/target/classes
..
do.sun.jdk:
 [echo] *** Running on a Sun JDK ***
 [echo] generate server keys
 [java] Illegal option:*
 Requests/examples/webservice-ssl-client-cert/target/serverStore.jks*
 [java] keytool -genkeypair [OPTION]...


El lun, 8 feb 2021 a las 0:30, Jean-Louis Monteiro (<
jlmonte...@tomitribe.com>) escribió:

> I agree.
> Would be awesome to have something more stable. It's better than it was.
> But still some work to do.
>
> Le ven. 5 févr. 2021 à 19:55, Zowalla, Richard <
> richard.zowa...@hs-heilbronn.de> a écrit :
>
> > Hi Cesar,
> >
> > would be very much appreciated, I guess.
> >
> > I noticed, that the PR jenkins job shows a different behaviour compared
> to
> > the master job in terms of reproducability.
> > In general, we should have a deeper look at the config to make the CI
> > behave more robust.
> >
> > Gruss
> > Richard
> > --
> > Richard Zowalla, M.Sc.
> > Wissenschaftlicher Mitarbeiter
> >
> > Medizinische Informatik
> > Hochschule Heilbronn
> > Max-Planck-Str. 39
> > D-74081 Heilbronn
> >
> > Mail: richard.zowa...@hs-heilbronn.de
> >
> >
> > 
> > Von: Cesar Hernandez [cesargu...@gmail.com]
> > Gesendet: Dienstag, 2. Februar 2021 22:01
> > An: dev@tomee.apache.org
> > Betreff: Re: TomEE-2966: JUnit5 OpenEJB Extension Module - Any thoughts?
> >
> > >
> > > They even work locally. Might bei Jenkins / CI related?
> >
> >
> > It could be, I've been also following up with an issue on the Jenkins Job
> > we have for Pull request.
> >
> > My proposal would be to start migrating the jobs to Jenkins pipelines so
> we
> > can have a better way to collaborate in the jobs configuration.
> >
> >
> > El mar, 2 feb 2021 a las 10:43, Zowalla, Richard (<
> > richard.zowa...@hs-heilbronn.de>) escribió:
> >
> > > Hi Cesar,
> > >
> > > it seems, that the master build is fine again. The last run did
> succeed,
> > > so I guess the tests failed with some sort of race condition. They even
> > > work locally. Might bei Jenkins / CI related?
> > >
> > > Gruss
> > > Richard
> > >
> > > 
> > > Von: Cesar Hernandez [cesargu...@gmail.com]
> > > Gesendet: Dienstag, 2. Februar 2021 17:05
> > > An: dev@tomee.apache.org
> > > Betreff: Re: TomEE-2966: JUnit5 OpenEJB Extension Module - Any
> thoughts?
> > >
> > > Hi Richard,
> > >
> > > Thank you for the PR and context provided.
> > > We now have back the Jenkins job on master at demand, I left yesterday
> a
> > > build[1] and after 6 hours we got 4 tests[2] but as far as I can see
> they
> > > are not related to this new extension module :).
> > >
> > >
> > >
> > > [1] https://ci-builds.apache.org/job/TomEE/job/master-build-full/72/
> > > [2]
> > > org.apache.ziplock.maven.MvnTest.main
> > > org.apache.ziplock.maven.MvnTest.test
> > > org.superbiz.mvc.MvcTest.org.superbiz.mvc.MvcTest
> > > org.superbiz.mvc.MvcTest.org.superbiz.mvc.MvcTest
> > >
> > >
> > >
> > > El lun, 1 feb 2021 a las 3:12, Zowalla, Richard (<
> > > richard.zowa...@hs-heilbronn.de>) escribió:
> > >
> > > > I went ahead with it and merged it. This shouldn't influence anything
> > > > on the master as it is just a new module.
> > > >
> > > > However, it enables some of our users to upgrade their legacy testing
> > > > (without application composer or arquillian) environments to pure
> > > > junit5.
> > > >
> > > > Gruss
> > > > Richard
> > > >
> > > > Am Mittwoch, den 27.01.2021, 17:25 + schrieb Zowalla, Richard:
> > > >

Re: TomEE-2966: JUnit5 OpenEJB Extension Module - Any thoughts?

[Cesar Hernandez]

>
> They even work locally. Might bei Jenkins / CI related?


It could be, I've been also following up with an issue on the Jenkins Job
we have for Pull request.

My proposal would be to start migrating the jobs to Jenkins pipelines so we
can have a better way to collaborate in the jobs configuration.


El mar, 2 feb 2021 a las 10:43, Zowalla, Richard (<
richard.zowa...@hs-heilbronn.de>) escribió:

> Hi Cesar,
>
> it seems, that the master build is fine again. The last run did succeed,
> so I guess the tests failed with some sort of race condition. They even
> work locally. Might bei Jenkins / CI related?
>
> Gruss
> Richard
>
> ________
> Von: Cesar Hernandez [cesargu...@gmail.com]
> Gesendet: Dienstag, 2. Februar 2021 17:05
> An: dev@tomee.apache.org
> Betreff: Re: TomEE-2966: JUnit5 OpenEJB Extension Module - Any thoughts?
>
> Hi Richard,
>
> Thank you for the PR and context provided.
> We now have back the Jenkins job on master at demand, I left yesterday a
> build[1] and after 6 hours we got 4 tests[2] but as far as I can see they
> are not related to this new extension module :).
>
>
>
> [1] https://ci-builds.apache.org/job/TomEE/job/master-build-full/72/
> [2]
> org.apache.ziplock.maven.MvnTest.main
> org.apache.ziplock.maven.MvnTest.test
> org.superbiz.mvc.MvcTest.org.superbiz.mvc.MvcTest
> org.superbiz.mvc.MvcTest.org.superbiz.mvc.MvcTest
>
>
>
> El lun, 1 feb 2021 a las 3:12, Zowalla, Richard (<
> richard.zowa...@hs-heilbronn.de>) escribió:
>
> > I went ahead with it and merged it. This shouldn't influence anything
> > on the master as it is just a new module.
> >
> > However, it enables some of our users to upgrade their legacy testing
> > (without application composer or arquillian) environments to pure
> > junit5.
> >
> > Gruss
> > Richard
> >
> > Am Mittwoch, den 27.01.2021, 17:25 + schrieb Zowalla, Richard:
> > > Hi all,
> > >
> > > a few days ago, I had a (virtual) coffee discussion with my colleguae
> > > Martin W. about moving some of our research projects towards pure
> > > JUnit
> > > 5.
> > >
> > > The missing thing: An openejb-junit module, which comes without a
> > > transient compile dependency towards junit4.
> > >
> > > Today, I had some time and implemented a first draft towards an
> > > additional openejb-junit5 module, which does not depend on junit4
> > > anymore.
> > >
> > > The PR is open for discussion / review, see [1].
> > >
> > > If someone has additional ideas, thoughts or improvements, I would be
> > > very happy about them!
> > >
> > > Gruss
> > > Richard
> > >
> > >
> > > [1] https://github.com/apache/tomee/pull/759
> > --
> > Richard Zowalla, M.Sc.
> > Research Associate, PhD Student | Medical Informatics
> >
> > Hochschule Heilbronn – University of Applied Sciences
> > Max-Planck-Str. 39
> > D-74081 Heilbronn
> > phone: +49 7131 504 6791
> > mail: richard.zowa...@hs-heilbronn.de
> > web: https://www.mi.hs-heilbronn.de/
> >
>
>
> --
> Atentamente:
> César Hernández.
>


-- 
Atentamente:
César Hernández.

Re: TomEE-2966: JUnit5 OpenEJB Extension Module - Any thoughts?

[Cesar Hernandez]

Hi Richard,

Thank you for the PR and context provided.
We now have back the Jenkins job on master at demand, I left yesterday a
build[1] and after 6 hours we got 4 tests[2] but as far as I can see they
are not related to this new extension module :).



[1] https://ci-builds.apache.org/job/TomEE/job/master-build-full/72/
[2]
org.apache.ziplock.maven.MvnTest.main
org.apache.ziplock.maven.MvnTest.test
org.superbiz.mvc.MvcTest.org.superbiz.mvc.MvcTest
org.superbiz.mvc.MvcTest.org.superbiz.mvc.MvcTest



El lun, 1 feb 2021 a las 3:12, Zowalla, Richard (<
richard.zowa...@hs-heilbronn.de>) escribió:

> I went ahead with it and merged it. This shouldn't influence anything
> on the master as it is just a new module.
>
> However, it enables some of our users to upgrade their legacy testing
> (without application composer or arquillian) environments to pure
> junit5.
>
> Gruss
> Richard
>
> Am Mittwoch, den 27.01.2021, 17:25 + schrieb Zowalla, Richard:
> > Hi all,
> >
> > a few days ago, I had a (virtual) coffee discussion with my colleguae
> > Martin W. about moving some of our research projects towards pure
> > JUnit
> > 5.
> >
> > The missing thing: An openejb-junit module, which comes without a
> > transient compile dependency towards junit4.
> >
> > Today, I had some time and implemented a first draft towards an
> > additional openejb-junit5 module, which does not depend on junit4
> > anymore.
> >
> > The PR is open for discussion / review, see [1].
> >
> > If someone has additional ideas, thoughts or improvements, I would be
> > very happy about them!
> >
> > Gruss
> > Richard
> >
> >
> > [1] https://github.com/apache/tomee/pull/759
> --
> Richard Zowalla, M.Sc.
> Research Associate, PhD Student | Medical Informatics
>
> Hochschule Heilbronn – University of Applied Sciences
> Max-Planck-Str. 39
> D-74081 Heilbronn
> phone: +49 7131 504 6791
> mail: richard.zowa...@hs-heilbronn.de
> web: https://www.mi.hs-heilbronn.de/
>


-- 
Atentamente:
César Hernández.

TOMEE-2960 Add github actions for tomee-7.1.x branch

[Cesar Hernandez]

Hi,

I created TOMEE-2960 [1] to explain the why and track the addition of
GitHub actions for tomee-7.1.x branch.
The current PR is ready for review and the scope covers:  Compile without
tests, pmd, and checkstyle.

Once this is reviewed and merged I'll follow up with some issues I'm seeing
locally when executing the `rat:check -Prat" profile to then jump into the
full tests to run.


[1] https://issues.apache.org/jira/browse/TOMEE-2960

-- 
Atentamente:
César Hernández.

TOMEE-2958 TOMEE-2959 Tomcat and jackson update

[Cesar Hernandez]

Hi all,

I created the following JIRAS and also a PR is now available for review:

Update to Tomcat 8.5.61
https://issues.apache.org/jira/browse/TOMEE-2958

Update to jackson 2.12.0
https://issues.apache.org/jira/browse/TOMEE-2959

PR: https://github.com/apache/tomee/pull/728
-- 
Atentamente:
César Hernández.

Re: TOMEE-2927: Translate to Portuguese: examples/serverless-tomee-microprofile

[Cesar Hernandez]

Hi Daniel,
I just review the structure, +1, Thanks much.

Any Portuguese speaker is welcome to do the copy edit :).

El lun, 18 ene 2021 a las 11:09, Daniel Dias Dos Santos (<
daniel.dias.analist...@gmail.com>) escribió:

> Hello,
>
> I opened a ticket in Jira [1] and a PR [2], can anyone revise
> the translation?
>
> thank you
>
> [1] https://issues.apache.org/jira/browse/TOMEE-2927
> [2] https://github.com/apache/tomee/pull/751
>


-- 
Atentamente:
César Hernández.

Re: [TCK] EJB 3.2 timers

[Cesar Hernandez]

thanks for sharing the awesome news!

El lun, 18 ene 2021 a las 7:51, Jean-Louis Monteiro (<
jlmonte...@tomitribe.com>) escribió:

> https://tck.work/tomee/build?id=1610964398253
>
> 100% green on EJB32 !!!
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Fri, Jan 15, 2021 at 4:18 PM Jonathan Gallimore <
> jonathan.gallim...@gmail.com> wrote:
>
> > Fantastic - thank you!
> >
> > On Fri, Jan 15, 2021 at 3:11 PM Jean-Louis Monteiro <
> > jlmonte...@tomitribe.com> wrote:
> >
> > > Went ahead and merged this PR and marked the jira as being resolved.
> I'm
> > > waiting for the build to finish and I'll fire a new TCK run over the
> > > weekend maybe so we can validate if it fixed or not the issue.
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
> > >
> > >
> > > On Thu, Jan 14, 2021 at 10:52 AM Jean-Louis Monteiro <
> > > jlmonte...@tomitribe.com> wrote:
> > >
> > > > Here is the PR https://github.com/apache/tomee/pull/749
> > > >
> > > > I'm building locally and I'll run the EJB32 related tests locally
> first
> > > > --
> > > > Jean-Louis Monteiro
> > > > http://twitter.com/jlouismonteiro
> > > > http://www.tomitribe.com
> > > >
> > > >
> > > > On Thu, Jan 14, 2021 at 10:45 AM Jean-Louis Monteiro <
> > > > jlmonte...@tomitribe.com> wrote:
> > > >
> > > >> Hi community,
> > > >>
> > > >> Finally got some time to think about this and fix it (I think ;-) )
> > > >>
> > > >> There is one scenario where it is relevant.
> > > >> Let's imagine you restart an application, the timer may have expired
> > > >> because the end is already in the past, but we don't want to have to
> > > change
> > > >> the binary in order to set a valid end date to restart a server.
> > > >>
> > > >> In that case, we are expecting the server to successfully start, but
> > the
> > > >> timer to never trigger.
> > > >>
> > > >> I'll create a PR so you can double check before I merge it.
> > > >> --
> > > >> Jean-Louis Monteiro
> > > >> http://twitter.com/jlouismonteiro
> > > >> http://www.tomitribe.com
> > > >>
> > > >>
> > > >> On Thu, Nov 19, 2020 at 9:08 AM Jean-Louis Monteiro <
> > > >> jlmonte...@tomitribe.com> wrote:
> > > >>
> > > >>> Thanks Richard for the quick feedback.
> > > >>>
> > > >>> I am totally with you. Can't think of a valid reason to do that or
> > even
> > > >>> think it should be a tested requirement in TCK.
> > > >>> If using endTime before startTime is the only way to specify a
> timer
> > > >>> never expires, something is wrong to me.
> > > >>>
> > > >>> I'll go ahead and see if I can adjust and at the same time raise an
> > > >>> issue on the TCK/EE side.
> > > >>>
> > > >>> --
> > > >>> Jean-Louis Monteiro
> > > >>> http://twitter.com/jlouismonteiro
> > > >>> http://www.tomitribe.com
> > > >>>
> > > >>>
> > > >>> On Thu, Nov 19, 2020 at 9:03 AM Zowalla, Richard <
> > > >>> richard.zowa...@hs-heilbronn.de> wrote:
> > > >>>
> > >  Hi,
> > > 
> > >  I think it is a bit odd in this tck test case, that the creation
> of
> > a
> > >  timer with an end time before the start time should even be
> > possible,
> > >  but nevermind :)
> > > 
> > >  I do not quite understand the reason why this behaviour was chosen
> > in
> > >  the first place. I might miss something as I am not long enough in
> > the
> > >  EE world.
> > > 
> > >  The exception itself sounds valid to me.
> > > 
> > >  Maybe:
> > > 
> > >  For now: Pre-check and adjustment? Seems to be specific to the
> > quartz
> > >  impl.
> > > 
> > >  Parallel: Asking on the TCK/spec lists?
> > > 
> > >  Best
> > >  Richard Z
> > > 
> > >  Am Mittwoch, den 18.11.2020, 22:52 +0100 schrieb Jean-Louis
> > Monteiro:
> > >  > Hi community,
> > >  >
> > >  > I found another thing I wanted to discuss and get feedback on.
> > >  > On the EJB 3.2 section of the TCK we are down to 5 failures all
> > >  > related to
> > >  > schedule/timers.
> > >  >
> > >  > To run them, use the following command
> > >  >
> > >  > ./runtests --web tomee-plume
> > >  > com.sun.ts.tests.ejb32.lite.timer.schedule.expire.Client
> > >  >
> > >  > This is the part failing
> > >  >
> > >  >
> > > 
> > >
> >
> https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/src/com/sun/ts/tests/ejb32/lite/timer/schedule/expire/Client.java#L231
> > >  >
> > >  > java.lang.IllegalArgumentException: End time cannot be before
> > start
> > >  > time
> > >  > >at
> > >  > >
> > > org.apache.openejb.quartz.impl.triggers.CronTriggerImpl.setEndTime(
> > >  > > CronTriggerImpl.java:417)
> > >  > >at
> > >  > >
> > > org.apache.openejb.core.timer.EJBCronTrigger.(EJBCronTrigger.
> > >  > > java:121)
> > >  > >at
> > >  > >
> > > org.apache.openejb.core.timer.CalendarTimerData.initializeTrigger(C
> > >  > 

Re: [VOTE] Release Apache TomEE 8.0.6

[Cesar Hernandez]

+1 (plus one)

El jue, 14 ene 2021 a las 13:17, Zowalla, Richard (<
richard.zowa...@hs-heilbronn.de>) escribió:

> Hi,
>
> +1 from my side.
>
> I tested the 8.0.6 plus artifact with our fullstack EAR app.
>
> Thanks, John for your time / work in preparing this release artifact :)
>
> Gruss
> Richard
>
> Am Donnerstag, den 14.01.2021, 16:05 + schrieb Jonathan Gallimore:
> > Hi All,
> >
> > This is a first attempt at a vote for a release of Apache TomEE
> > 8.0.6.
> >
> > Maven Repo:
> >
> https://repository.apache.org/content/repositories/orgapachetomee-1179
> >
> > Binaries & Source:
> >
> https://dist.apache.org/repos/dist/dev/tomee/staging-1179/tomee-8.0.6/
> >
> > Source code:
> >
>
> https://dist.apache.org/repos/dist/dev/tomee/staging-1179/tomee-8.0.6/tomee-project-8.0.6-source-release.zip
> >
> > Tags:
> >
>
> https://gitbox.apache.org/repos/asf?p=tomee.git;a=tag;h=refs/tags/tomee-8.0.6
> >
> > Release notes:
> >
> >
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12349403
> >
> > (Developers - please review and adjust your tickets if necessary!)
> >
> > Please VOTE:
> >
> > [+1] Yes, release it
> > [+0] Not fussed
> > [-1] Don't release, there's a showstopper (please specify what the
> > showstopper is)
> >
> > Vote will be open for 72 hours.
> >
> > Thanks
> >
> > Jon
>


-- 
Atentamente:
César Hernández.

Re: [TCK] Building the TCK?

[Cesar Hernandez]

Hi Richard,

 Therefore, I guess, that [2] is a pre-built version of the TCK.

Yes,  it's recommended to use a pre-build TCK version instead of manually
build it.

Any thoughts on this?
> If there are no objections, I would try to create a related PR with a
> README enhancement.


 Sure, go ahead. Thank you!

El mié, 13 ene 2021 a las 10:15, Zowalla, Richard (<
richard.zowa...@hs-heilbronn.de>) escribió:

> Just a short update: The build using [1] went fine. It produced a ZIP
> archive, which has an equal size to [2]. Therefore, I guess, that [2]
> is a pre-built version of the TCK.
>
> The new URL for downloading the TCK was introduced with TOMEE-2849 with
> PR-12 [3]. Consequently, we might need to update the README
> accordingly.
>
> Any thoughts on this?
>
> If there are no objections, I would try to create a related PR with a
> README enhancement.
>
> Gruss
> Richard
>
> [1] https://github.com/eclipse-ee4j/jakartaee-tck/releases/tag/8.0.2
> [2]
>
> https://download.eclipse.org/jakartaee/platform/8/jakarta-jakartaeetck-8.0.2.zip
> [3] https://github.com/apache/tomee-tck/pull/12
>
>
>
> Am Mittwoch, den 13.01.2021, 14:43 + schrieb Zowalla, Richard:
> > Hi all,
> >
> > today, I had some time and tried to setup the TomEE-TCK on my machine
> > as I was curios on running the TCK locally.
> >
> > From previous mails, I identified the related repository on GitHub
> > [1]
> > and cloned it. The documentation states:
> >
> > 1. Download the TCK & Unzip it [2]
> > 2. Set some env variables as explained in the README of [1]
> > 3. Run the shell script to build the
> > tck: $WORKSPACE/docker/build_jakartaeetck.sh
> >
> > The first task is pretty straightforward. Setting up ant as well as
> > jdk8 is also straightforward.
> >
> > However, the execution of the actual build script fails as it seems
> > to
> > reference an "install" folder inside the "jakartaeetck" folder, which
> > does not exist by default. The output of the script is here: [3].
> >
> > So basically my questions are:
> >
> > 1. Did I miss something important?
> > 2. Is there any other or some additional documentation (besides the
> > README.adoc in [4]), which explains setting up the tck? :)
> >
> > Downloading the tck tagged as 8.0.2 directly from GitHub [5] provides
> > a
> > rather small zip file (80MB compared to the 655MB file mentioned in
> > the
> > README) but contains the missing "install" directory. The build from
> > this ZIP [5] seems to work but I am quite confused now.
> >
> > Gruss & Thx
> > Richard
> >
> > [1] https://github.com/apache/tomee-tck
> > [2]
> >
> https://download.eclipse.org/jakartaee/platform/8/jakarta-jakartaeetck-8.0.2.zip
> > [3] https://gist.github.com/rzo1/325ee0b6909b2d960db86cd38d511017
> > [4] https://github.com/apache/tomee-tck/blob/master/README.adoc
> > [5] https://github.com/eclipse-ee4j/jakartaee-tck/releases/tag/8.0.2
> --
> Richard Zowalla, M.Sc.
> Research Associate, PhD Student | Medical Informatics
>
> Hochschule Heilbronn – University of Applied Sciences
> Max-Planck-Str. 39
> D-74081 Heilbronn
> phone: +49 7131 504 6791
> mail: richard.zowa...@hs-heilbronn.de
> web: https://www.mi.hs-heilbronn.de/
>


-- 
Atentamente:
César Hernández.

Re: [ANN] Welcome new Apache TomEE Committer Richard Zowalla

[Cesar Hernandez]

Congratulations  Richard!
Your hard work is reflected in your contribution, reviews, etc.  We all are
delighted to keep working with you and keep having the fun of learning,
sharing and caring for the TomEE community :)

El mar, 12 ene 2021 a las 18:34, Daniel Dias Dos Santos (<
daniel.dias.analist...@gmail.com>) escribió:

> Congratulations Richard very deserved 
>


-- 
Atentamente:
César Hernández.

Re: Master build on CI

[Cesar Hernandez]

Hi Jean-Louis

Hi, as a follow up for this thread, I just updated the test build we have
in GitHub actions with the new -Pstyle,rat we are using in Jenkins.

https://github.com/apache/tomee/pull/745 [merged already since it only
updated Github actions file]

During the process I notice that boms pom.xml files contained references to
org.apache.johnzon:johnzon-core:jar:1.2.9-SNAPSHOT so I proceed to execute
org.apache.tomee.bootstrap.GenerateBoms and created a PR:
https://github.com/apache/tomee/pull/746  [*Ready For Review*]

This brings back again GitHub actions into a green status for building
master with compilation and sanity checks (skipping test).
Feel free to review the PR.
https://github.com/apache/tomee/pull/746/checks?check_run_id=1672172377

I also notice that locally the rat check was failing when using IntelliJ.
I opened the following PR to fix this:
https://github.com/apache/tomee/pull/747 [*Ready For Review*]

El jue, 3 dic 2020 a las 8:36, Zowalla, Richard (<
richard.zowa...@hs-heilbronn.de>) escribió:

> thanks
>
> Am Donnerstag, den 03.12.2020, 15:23 +0100 schrieb Jean-Louis Monteiro:
> > For sanity: mvn -U --show-version --fail-at-end clean install
> > -Pstyle,rat
> > -DskipTests
> > For quick: mvn -U --show-version --fail-at-end clean install -Pquick
> > For full: mvn -U --show-version --fail-at-end clean install -Pall-
> > adapters
> > For OWASP: mvn -U --show-version --fail-at-end clean install -Powasp-
> > check
> > -DskipTests
> >
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Thu, Dec 3, 2020 at 3:17 PM Zowalla, Richard <
> > richard.zowa...@hs-heilbronn.de> wrote:
> >
> > > Hi,
> > >
> > > thanks for your work!
> > >
> > > Could you add the related job configuration / maven configuration
> > > used
> > > for these build jobs?
> > >
> > > We would like to replicate it on our university infrastructure as
> > > well.
> > > Thanks!
> > >
> > > Best
> > > Richard
> > >
> > > Am Donnerstag, den 03.12.2020, 14:58 +0100 schrieb Jean-Louis
> > > Monteiro:
> > > > Hi community,
> > > >
> > > > As I'm actively working on TCK, I might break stuff when pushing
> > > > changes.
> > > > Without CI it's quite hard to know where you are and where you
> > > > go.
> > > >
> > > > So I went and spent some time this morning to rework a bit of our
> > > > CI
> > > > on
> > > > Jenkins.
> > > >
> > > > https://ci-builds.apache.org/job/Tomee/
> > > >
> > > > I created a couple of jobs
> > > >
> > > > *master-sanity-checks* (triggered on commit)
> > > > The goal here is to run checkstyle, pmd, rat and a quick compile
> > > > of
> > > > sources
> > > > without tests.
> > > > This is because our full build takes a lot of time, and it's
> > > > frustrating to
> > > > pretty much be at the end of the build and realize you missed an
> > > > unused
> > > > import and the full build is aborted.
> > > >
> > > > *master-build-quick* (triggered after sanity checks if
> > > > successful)
> > > > If the previous build passes, this one is triggered and runs a
> > > > clean
> > > > install with profile quick. Does not run examples, all arquillian
> > > > adapters,
> > > > tck and itests.
> > > > Not sure if it's relevant, but it runs minimum things to have a
> > > > good
> > > > confidence on TomEE build.
> > > >
> > > > *master-build-full* (executed every day)
> > > > This one does not run on commit. It can be executed manually or
> > > > it
> > > > will run
> > > > every day anyway.
> > > > It runs everything possible in TomEE but it will take hours.
> > > >
> > > > *master-owasp-check* (to be triggered manually). For the moment
> > > > it
> > > > takes
> > > > too much time to have it in other builds. To be discussed.
> > > >
> > > > I pushed some changes already to codebase in order to add missing
> > > > headers,
> > > > and fix the build already. So far sanity passed and triggered the
> > > > quick.
> > > > I'll monitor and see what happens
> > > >
> > > >
> > >

Re: Releases?

[Cesar Hernandez]

+1 on a new release.
btw, this one is a pending dependency update in case still make it for the
release. The CI result got stuck base on the WIP I'm troubleshooting in the
Jenkins TomEE PR job: https://github.com/apache/tomee/pull/729

El vie, 8 ene 2021 a las 10:25, Zowalla, Richard (<
richard.zowa...@hs-heilbronn.de>) escribió:

> Hi,
>
> great idea - no objections from my side
>
> Gruss
> Richard
>
> 
> Von: Jonathan Gallimore [jonathan.gallim...@gmail.com]
> Gesendet: Freitag, 8. Januar 2021 14:15
> An: dev@tomee.apache.org
> Betreff: Releases?
>
> Hi All,
>
> Any objections if I kick off a 8.0.6 release? I think there are some
> dependency updates that it would be useful to get included (specifically
> Tomcat), and also there's a regression with using a non-transactional
> ActiveMQ connection factory in a transactional method that I have fixed as
> well.
>
> Thanks
>
> Jon
>


-- 
Atentamente:
César Hernández.

Re: CI job for tomee-7.0.x

[Cesar Hernandez]

Hi All,

Jenkis job and github actions for apache/tomee-7.0.x are both green now
with full tests  passing :) [1] [2]

During the process, I identified that GitHub actions default maven
settings.xml doesn't play nicely with shrinkwrap-resolve [3] so the
workaround was to override the instance settings.xml with a vanilla one [4]
as part of the Actions file.

I'll open a new thread for both Jenkins PR and Master branch CI since this
one is still not green.


[1] https://github.com/apache/tomee/runs/1579968827?check_suite_focus=true
[2] https://ci-builds.apache.org/job/Tomee/job/tomee-7.0.x/17/
[3] Exception: Unable to get security configuration from
/home/runner/.m2/settings-security.xml
[4]
https://github.com/apache/tomee/commit/b39ec68871f8f0efc7c96b44a123d22e938bc893#diff-7829468e86c1cc5d5133195b5cb48e1ff6c75e3e9203777f6b2e379d9e4882b3R31-R36





El mié, 16 dic 2020 a las 21:09, Cesar Hernandez ()
escribió:

> Hi All,
>
> I merged today the last test fix and now tomee-7.0.x is back to green
> (blue in current apache jenkins job):
> https://ci-builds.apache.org/job/Tomee/job/tomee-7.0.x/10/
>
> In parallel I'm troubleshooting the current Jenkins Job we have for Pull
> Requests [1] and also adding Github actions for tomee-7.0.x branch [2].
> Github actions is a WIP as I'm applying the lessons learned in the
> iteration performed over master branch.
>
> [1] https://ci-builds.apache.org/job/Tomee/job/Pull%20Requests/20/
> [2] https://github.com/apache/tomee/pull/735
>
>
> El mar, 15 dic 2020 a las 14:40, Cesar Hernandez ()
> escribió:
>
>> Thank you Richard and Jean-Louis for the work done.
>>
>> As promise, I created the ticket for DeployInWebAppsDirectoryTest issue:
>> https://issues.apache.org/jira/browse/TOMEE-2942
>>
>> Also, a PR is available with the fix based on the nice patch Richard did
>> previously with TOMEE-2930.
>> https://github.com/apache/tomee/pull/727
>>
>> El jue, 10 dic 2020 a las 6:39, Jean-Louis Monteiro (<
>> jlmonte...@tomitribe.com>) escribió:
>>
>>> Reviewing and merging now.
>>> Thanks for the reminder
>>> --
>>> Jean-Louis Monteiro
>>> http://twitter.com/jlouismonteiro
>>> http://www.tomitribe.com
>>>
>>>
>>> On Thu, Dec 10, 2020 at 12:29 PM Zowalla, Richard <
>>> richard.zowa...@hs-heilbronn.de> wrote:
>>>
>>> > Just a friendly reminder. The PRs for this are still pending:
>>> >
>>> > https://github.com/apache/tomee/pull/720
>>> > https://github.com/apache/tomee/pull/722
>>> >
>>> >
>>> > Am Dienstag, den 01.12.2020, 08:02 + schrieb Zowalla, Richard:
>>> > > Hi,
>>> > >
>>> > > forgot to send an eMail to the list. The related PRs are available:
>>> > >
>>> > > https://github.com/apache/tomee/pull/720
>>> > > https://github.com/apache/tomee/pull/722
>>> > >
>>> > > Best
>>> > > Richard Z
>>> > >
>>> > >
>>> > > Am Freitag, den 27.11.2020, 13:09 + schrieb Zowalla, Richard:
>>> > > > Will also check the third one :) - will create a related JIRA.
>>> > > >
>>> > > > Best,
>>> > > > Richard
>>> > > >
>>> > > >
>>> > > > Am Freitag, den 27.11.2020, 08:24 + schrieb Zowalla, Richard:
>>> > > > > Hi Cesar,
>>> > > > >
>>> > > > > i will give
>>> > > > >
>>> > > > > > The second failing test trowed a: [Fatal Error] :8:23: Invalid
>>> > > > > > byte 2 of
>>> > > > > > 2-byte UTF-8 sequence. error.
>>> > > > > >
>>> >
>>> https://ci-builds.apache.org/job/Tomee/job/tomee-7.0.x/org.superbiz$moviefun-functional-test/3/testReport/junit/org.superbiz.moviefun/MoviesArquillianHtmlUnitTest/org_superbiz_moviefun_MoviesArquillianHtmlUnitTest/
>>> > > > >
>>> > > > > a try and create a related JIRA.
>>> > > > >
>>> > > > > Best,
>>> > > > > Richard
>>> > > > >
>>> > > > > Am Donnerstag, den 26.11.2020, 20:35 -0600 schrieb Cesar
>>> > > > > Hernandez:
>>> > > > > > Hi All,
>>> > > > > >
>>> > > > > > Today I set up a CI job for tomee 7.0.x.
>>> > > > > > I initially set up Java 7 but I got 

Re: CI job for tomee-7.0.x

[Cesar Hernandez]

Hi All,

I merged today the last test fix and now tomee-7.0.x is back to green (blue
in current apache jenkins job):
https://ci-builds.apache.org/job/Tomee/job/tomee-7.0.x/10/

In parallel I'm troubleshooting the current Jenkins Job we have for Pull
Requests [1] and also adding Github actions for tomee-7.0.x branch [2].
Github actions is a WIP as I'm applying the lessons learned in the
iteration performed over master branch.

[1] https://ci-builds.apache.org/job/Tomee/job/Pull%20Requests/20/
[2] https://github.com/apache/tomee/pull/735


El mar, 15 dic 2020 a las 14:40, Cesar Hernandez ()
escribió:

> Thank you Richard and Jean-Louis for the work done.
>
> As promise, I created the ticket for DeployInWebAppsDirectoryTest issue:
> https://issues.apache.org/jira/browse/TOMEE-2942
>
> Also, a PR is available with the fix based on the nice patch Richard did
> previously with TOMEE-2930.
> https://github.com/apache/tomee/pull/727
>
> El jue, 10 dic 2020 a las 6:39, Jean-Louis Monteiro (<
> jlmonte...@tomitribe.com>) escribió:
>
>> Reviewing and merging now.
>> Thanks for the reminder
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>>
>> On Thu, Dec 10, 2020 at 12:29 PM Zowalla, Richard <
>> richard.zowa...@hs-heilbronn.de> wrote:
>>
>> > Just a friendly reminder. The PRs for this are still pending:
>> >
>> > https://github.com/apache/tomee/pull/720
>> > https://github.com/apache/tomee/pull/722
>> >
>> >
>> > Am Dienstag, den 01.12.2020, 08:02 + schrieb Zowalla, Richard:
>> > > Hi,
>> > >
>> > > forgot to send an eMail to the list. The related PRs are available:
>> > >
>> > > https://github.com/apache/tomee/pull/720
>> > > https://github.com/apache/tomee/pull/722
>> > >
>> > > Best
>> > > Richard Z
>> > >
>> > >
>> > > Am Freitag, den 27.11.2020, 13:09 + schrieb Zowalla, Richard:
>> > > > Will also check the third one :) - will create a related JIRA.
>> > > >
>> > > > Best,
>> > > > Richard
>> > > >
>> > > >
>> > > > Am Freitag, den 27.11.2020, 08:24 + schrieb Zowalla, Richard:
>> > > > > Hi Cesar,
>> > > > >
>> > > > > i will give
>> > > > >
>> > > > > > The second failing test trowed a: [Fatal Error] :8:23: Invalid
>> > > > > > byte 2 of
>> > > > > > 2-byte UTF-8 sequence. error.
>> > > > > >
>> >
>> https://ci-builds.apache.org/job/Tomee/job/tomee-7.0.x/org.superbiz$moviefun-functional-test/3/testReport/junit/org.superbiz.moviefun/MoviesArquillianHtmlUnitTest/org_superbiz_moviefun_MoviesArquillianHtmlUnitTest/
>> > > > >
>> > > > > a try and create a related JIRA.
>> > > > >
>> > > > > Best,
>> > > > > Richard
>> > > > >
>> > > > > Am Donnerstag, den 26.11.2020, 20:35 -0600 schrieb Cesar
>> > > > > Hernandez:
>> > > > > > Hi All,
>> > > > > >
>> > > > > > Today I set up a CI job for tomee 7.0.x.
>> > > > > > I initially set up Java 7 but I got the "Unsupported
>> > > > > > major.minor version
>> > > > > > 52.0" error so the job currently uses Java 8 and maven 3.3.9.
>> > > > > > The current branch status is here
>> > > > > > https://ci-builds.apache.org/job/Tomee/job/tomee-7.0.x/3/
>> > > > > >
>> > > > > >
>> > > > > > One of the failing test is because one of the examples requires
>> > > > > > the usage
>> > > > > > of 7.0.8-SNAPSHOT:zip:plus.
>> > > > > >
>> >
>> https://github.com/apache/tomee/blob/tomee-7.0.x/examples/connector-ear/connector-sample-functional-tests/src/test/java/org/superbiz/moviefun/DeployInWebAppsDirectoryTest.java#L108
>> > > > > >
>> > > > > > I'll open a JIRA and a Patch for that test.
>> > > > > >
>> > > > > > The second failing test trowed a: [Fatal Error] :8:23: Invalid
>> > > > > > byte 2 of
>> > > > > > 2-byte UTF-8 sequence. error.
>> > > > > >
>> >
>> https://ci-builds.apache.org/job/Tomee/job/tomee-7.0.x/

TOMEE-2943 Updating configuration for TomEE repository

[Cesar Hernandez]

Hi All,

I found that JIRA integration is currently broken even when the current
TomEE repository configuration contains it:
https://gitbox.apache.org/schemes.cgi?tomee

After a follow-up from the INFRA team [1] it seems now repository
configuration is done via the .asf.yaml file.

I created TOMEE-2943 to describe the current status and what the project
gets with the inclusion of the .asf.yaml file.
https://issues.apache.org/jira/browse/TOMEE-2943

A PR is now also available for review:
https://github.com/apache/tomee/pull/734


[1] https://issues.apache.org/jira/browse/INFRA-21176

-- 
Atentamente:
César Hernández.

Re: CI job for tomee-7.0.x

[Cesar Hernandez]

Thank you Richard and Jean-Louis for the work done.

As promise, I created the ticket for DeployInWebAppsDirectoryTest issue:
https://issues.apache.org/jira/browse/TOMEE-2942

Also, a PR is available with the fix based on the nice patch Richard did
previously with TOMEE-2930.
https://github.com/apache/tomee/pull/727

El jue, 10 dic 2020 a las 6:39, Jean-Louis Monteiro (<
jlmonte...@tomitribe.com>) escribió:

> Reviewing and merging now.
> Thanks for the reminder
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Thu, Dec 10, 2020 at 12:29 PM Zowalla, Richard <
> richard.zowa...@hs-heilbronn.de> wrote:
>
> > Just a friendly reminder. The PRs for this are still pending:
> >
> > https://github.com/apache/tomee/pull/720
> > https://github.com/apache/tomee/pull/722
> >
> >
> > Am Dienstag, den 01.12.2020, 08:02 + schrieb Zowalla, Richard:
> > > Hi,
> > >
> > > forgot to send an eMail to the list. The related PRs are available:
> > >
> > > https://github.com/apache/tomee/pull/720
> > > https://github.com/apache/tomee/pull/722
> > >
> > > Best
> > > Richard Z
> > >
> > >
> > > Am Freitag, den 27.11.2020, 13:09 + schrieb Zowalla, Richard:
> > > > Will also check the third one :) - will create a related JIRA.
> > > >
> > > > Best,
> > > > Richard
> > > >
> > > >
> > > > Am Freitag, den 27.11.2020, 08:24 + schrieb Zowalla, Richard:
> > > > > Hi Cesar,
> > > > >
> > > > > i will give
> > > > >
> > > > > > The second failing test trowed a: [Fatal Error] :8:23: Invalid
> > > > > > byte 2 of
> > > > > > 2-byte UTF-8 sequence. error.
> > > > > >
> >
> https://ci-builds.apache.org/job/Tomee/job/tomee-7.0.x/org.superbiz$moviefun-functional-test/3/testReport/junit/org.superbiz.moviefun/MoviesArquillianHtmlUnitTest/org_superbiz_moviefun_MoviesArquillianHtmlUnitTest/
> > > > >
> > > > > a try and create a related JIRA.
> > > > >
> > > > > Best,
> > > > > Richard
> > > > >
> > > > > Am Donnerstag, den 26.11.2020, 20:35 -0600 schrieb Cesar
> > > > > Hernandez:
> > > > > > Hi All,
> > > > > >
> > > > > > Today I set up a CI job for tomee 7.0.x.
> > > > > > I initially set up Java 7 but I got the "Unsupported
> > > > > > major.minor version
> > > > > > 52.0" error so the job currently uses Java 8 and maven 3.3.9.
> > > > > > The current branch status is here
> > > > > > https://ci-builds.apache.org/job/Tomee/job/tomee-7.0.x/3/
> > > > > >
> > > > > >
> > > > > > One of the failing test is because one of the examples requires
> > > > > > the usage
> > > > > > of 7.0.8-SNAPSHOT:zip:plus.
> > > > > >
> >
> https://github.com/apache/tomee/blob/tomee-7.0.x/examples/connector-ear/connector-sample-functional-tests/src/test/java/org/superbiz/moviefun/DeployInWebAppsDirectoryTest.java#L108
> > > > > >
> > > > > > I'll open a JIRA and a Patch for that test.
> > > > > >
> > > > > > The second failing test trowed a: [Fatal Error] :8:23: Invalid
> > > > > > byte 2 of
> > > > > > 2-byte UTF-8 sequence. error.
> > > > > >
> >
> https://ci-builds.apache.org/job/Tomee/job/tomee-7.0.x/org.superbiz$moviefun-functional-test/3/testReport/junit/org.superbiz.moviefun/MoviesArquillianHtmlUnitTest/org_superbiz_moviefun_MoviesArquillianHtmlUnitTest/
> > > > > >
> > > > > > If someone wants to take a swing on this, feel free to pick it
> > > > > > up. Remember
> > > > > > to create a JIRA and notify the mailing list to avoid
> > > > > > duplication of work.
> > > > > >
> > > > > > The thrid failing test: javax.ws.rs.NotSupportedException: HTTP
> > > > > > 415
> > > > > > Unsupported Media Type
> > > > > >
> >
> https://ci-builds.apache.org/job/Tomee/job/tomee-7.0.x/org.superbiz$tomee-webprofile-embedded/3/testReport/junit/org.superbiz.movie/MovieServiceTest/addMovie/
> > > > > >
> > > > > > If someone wants to take a swing on this, feel free to pick it
> > > > > > up. Remember
> > > > > > to create a JIRA and notify the mailing list to avoid
> > > > > > duplication of work.
> > > > > >
> > --
> > Richard Zowalla, M.Sc.
> > Research Associate, PhD Student | Medical Informatics
> >
> > Hochschule Heilbronn – University of Applied Sciences
> > Max-Planck-Str. 39
> > D-74081 Heilbronn
> > phone: +49 7131 504 6791
> > mail: richard.zowa...@hs-heilbronn.de
> > web: https://www.mi.hs-heilbronn.de/
> >
>


-- 
Atentamente:
César Hernández.

TOMEE-2939 Update bcprov-jdk15on to 1.67

[Cesar Hernandez]

Hi all,

I created the following JIRA related to bouncycastle bcprov-jdk15on to
1.67.
https://issues.apache.org/jira/browse/TOMEE-2939

PR's are also available for review.

tomee-7.0.x
https://github.com/apache/tomee/pull/727

tomee-7.1.x
https://github.com/apache/tomee/pull/728

master
https://github.com/apache/tomee/pull/729

-- 
Atentamente:
César Hernández.

CI job for tomee-7.0.x

[Cesar Hernandez]

Hi All,

Today I set up a CI job for tomee 7.0.x.
I initially set up Java 7 but I got the "Unsupported major.minor version
52.0" error so the job currently uses Java 8 and maven 3.3.9.
The current branch status is here
https://ci-builds.apache.org/job/Tomee/job/tomee-7.0.x/3/

One of the failing test is because one of the examples requires the usage
of 7.0.8-SNAPSHOT:zip:plus.
https://github.com/apache/tomee/blob/tomee-7.0.x/examples/connector-ear/connector-sample-functional-tests/src/test/java/org/superbiz/moviefun/DeployInWebAppsDirectoryTest.java#L108
I'll open a JIRA and a Patch for that test.

The second failing test trowed a: [Fatal Error] :8:23: Invalid byte 2 of
2-byte UTF-8 sequence. error.
https://ci-builds.apache.org/job/Tomee/job/tomee-7.0.x/org.superbiz$moviefun-functional-test/3/testReport/junit/org.superbiz.moviefun/MoviesArquillianHtmlUnitTest/org_superbiz_moviefun_MoviesArquillianHtmlUnitTest/
If someone wants to take a swing on this, feel free to pick it up. Remember
to create a JIRA and notify the mailing list to avoid duplication of work.

The thrid failing test: javax.ws.rs.NotSupportedException: HTTP 415
Unsupported Media Type
https://ci-builds.apache.org/job/Tomee/job/tomee-7.0.x/org.superbiz$tomee-webprofile-embedded/3/testReport/junit/org.superbiz.movie/MovieServiceTest/addMovie/
If someone wants to take a swing on this, feel free to pick it up. Remember
to create a JIRA and notify the mailing list to avoid duplication of work.

-- 
Atentamente:
César Hernández.

Re: How can I help?

[Cesar Hernandez]

Hi Jorge,

Welcome!
The following is a crosspost of the latest activity:

We have prepared some materials to help people like you who are new to
TomEE at the following link:
http://tomee.apache.org/community/contributing/contribution-tips.html

There are a couple of items for you to choose from:

- Documentation translation is a great opportunity for new contributions.
Check for instance these tickets:
Portuguese:https://issues.apache.org/jira/browse/TOMEE-2473
Spanish: https://issues.apache.org/jira/browse/TOMEE-2442

Additional TomEE website development resources:
https://www.tomitribe.com/blog/how-to-contribute-to-the-tomee-website/

- When you are ready you can go to JIRA and look through the various tickets
that are still unassigned. Feel free to ask as many questions as you like
in the mailing list before, during, and after your first contribution!

https://issues.apache.org/jira/projects/TOMEE/issues/TOMEE-2496?filter=allopenissues

The recent work in progress:

 - Jakarta EE 8 and EE 9 compliance: Immediate: some help getting people to
know how to run the TCK. Long-term: help to fix tests

 - User list: there might be some questions you know the answers to.

Let us know what kind of things sounds interesting and we'll see what might
fit.

El mié, 25 nov 2020 a las 10:38, Jorge Luis Morales Reyes (<
jorgeluismre...@gmail.com>) escribió:

> --
> *Jorge Luis Morales Reyes*
> -- Claro: 8925-8285
> -- Mov: 8552-3626
>


-- 
Atentamente:
César Hernández.

Re: Master build on CI

[Cesar Hernandez]

@Richard Zowalla,

In terms of Jenkis job configuration, what is your Job configuration set up
in the University?

Current Apache TomEE master job has the following configurations:

-Java: latest Java 8
-Maven: 3.3.9 version with MAVEN_OPTS -Xmx1536m
-Maven command: -U --show-version --fail-at-end clean install -Pall-adapters
-Junit patter for post-build actions: **/target/surefire-reports/TEST-*.xml

Buildbot had 3 steps (temp folder creation, checkstyle, pmd, install
without test) before executing the full project tests.
https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/1426
I wonder if you included the same steps build bot has or if you went
straight to `clean install` like the Job we currently have in Apache CI Job.

El mié., 18 nov. 2020 a las 5:12, Jonathan Gallimore (<
jonathan.gallim...@gmail.com>) escribió:

> I'll dig into the log... thanks for the pointers. Its too bad that Jenkins
> shows the modules in a weird order though. Things like that add to my
> frustration with it.
>
> Jon
>
> On Wed, Nov 18, 2020 at 9:06 AM Zowalla, Richard <
> richard.zowa...@hs-heilbronn.de> wrote:
>
>> Hi Jon,
>>
>> the module order shown on the start page does not necessarily reflect the
>> build order.
>>
>> We are building TomEE Master from GitHub on our university Jenkins CI
>> infrastructure  as well.
>>
>> Afaik, the module order is hidden in the CI log files:
>>
>> CI University:
>> https://gist.github.com/rzo1/aded63855dbabda57ab11a89188ada68
>> CI Apache: https://gist.github.com/rzo1/0fe6cb8c67fab5ded2ab566e30b7a4e3
>>
>> Looking at both CI logs, the build order is:
>>
>> Core
>> Assembly
>> Zips
>> Integration
>>
>> as one would expect or did I miss something, Jon?
>>
>> Best
>> Richard
>>
>> FYI: The latest CI Job on our infrastructure failed with 10 tests (tck
>> beanvalidation):
>> https://gist.github.com/rzo1/05ff7f30c034c66355cb95363b35686f
>>
>> Am Dienstag, den 17.11.2020, 22:42 + schrieb Jonathan Gallimore:
>>
>> I'll keep working on this. I got a clean build on my machine here (which
>>
>> takes just under 2 hours), and have gotten a release up for vote. We're
>>
>> definitely seeing 'odd' things on this instance.
>>
>>
>> Jon
>>
>>
>> On Tue, Nov 17, 2020 at 9:32 PM David Blevins <
>>
>> david.blev...@gmail.com
>>
>> >
>>
>> wrote:
>>
>>
>> On Nov 17, 2020, at 1:50 AM, Jonathan Gallimore <
>>
>> jonathan.gallim...@gmail.com
>>
>> > wrote:
>>
>>
>> I kicked off a run of this last night:
>>
>> https://ci-builds.apache.org/job/Tomee/job/master/10/
>>
>>  - which completed
>>
>> (it
>>
>> was hanging before), with 38 test failures, looking to be OWB related.
>>
>> The
>>
>> tests I've looked at so far locally pass ok - I'm wondering if this is
>>
>> specific to Jenkins, or timing related (as the build went past midnight,
>>
>> and so old snapshots may be picked up.
>>
>>
>> Kicked off another full build on Jenkins, and also a full build locally
>>
>> (which take about half the time of the CI). I'll report back.
>>
>>
>> I tried some time ago to set us up in the Apache setup for Jenkins and got
>>
>> failures along with a very not intuitive reactor order.
>>
>>
>> For example, in module order from this build:
>>
>>
>>  -
>>
>> https://ci-builds.apache.org/job/Tomee/job/master/10/
>>
>>
>>
>> This is not a complete summary, but a highlight the most odd ordering I
>>
>> see:
>>
>>
>> Unstable TomEE :: Arquillian Adaptors Parent :: Tests :: Web Profile
>>
>>   29 min
>>
>> ...
>>
>> Success TomEE :: TomEE :: Apache TomEE  1 min 53 sec
>>
>> ...
>>
>> Success TomEE :: Assembly   3.6 sec
>>
>> ...
>>
>> Success TomEE :: Container :: Core
>>
>>
>> The above is the opposite of what I'd expect, which is:
>>
>>
>>  - Build the core code (TomEE :: Container :: Core)
>>
>>  - Assemble the webapps (TomEE :: Assembly)
>>
>>  - Create the Apache TomEE distribution zips (TomEE :: TomEE :: Apache
>>
>> TomEE)
>>
>>  - Integration test the zips (TomEE :: Arquillian Adaptors Parent :: Tests
>>
>> :: Web Profile)
>>
>>
>> Instead we have:
>>
>>
>>  - Test the zips we haven't built yet
>>
>>  - Build the zips from webapps we haven't created yet
>>
>>  - Build the webapps from code we haven't compiled yet
>>
>>  - Now compile the code
>>
>>
>> It's completely baffling.  We get the correct order on our machines and in
>>
>> buildbot.  It's just this Jenkins that seems to create such a completely
>>
>> unintelligible result.
>>
>>
>> It's like there is some invisible setting or "optimization" enabled.
>>
>>
>>
>> -David
>>
>>
>>
>> --
>>
>> Richard Zowalla, M.Sc.
>> Research Associate, PhD Student | Medical Informatics
>>
>>
>>
>> Hochschule Heilbronn – University of Applied Sciences
>> Max-Planck-Str. 39
>> D-74081 Heilbronn
>> phone: +49 7131 504 6791
>> mail: richard.zowa...@hs-heilbronn.de
>> web: http://www.mi.hs-heilbronn.de/
>>
>

-- 
Atentamente:
César Hernández.

Re: [VOTE] Release Apache TomEE 8.0.5 and 9.0.0-M3

[Cesar Hernandez]

+1

El mar., 17 nov. 2020 a las 16:44, Jonathan Gallimore (<
jonathan.gallim...@gmail.com>) escribió:

> If there's a re-roll, I'll definitely pull that in. I've fought against
> various dependency updates pretty much all day to get a clean build, so
> I'll hold off re-rolling right this moment.
>
> Jon
>
> On Tue, Nov 17, 2020 at 10:32 PM Thomas Andraschko <
> andraschko.tho...@gmail.com> wrote:
>
> > Not a showstopper but it would be great if it could contain MyFaces 2.3.7
> > (there is already a PR for it) but it's also ok for me to have it in
> 8.0.6.
> >
> > Am Di., 17. Nov. 2020 um 23:11 Uhr schrieb Jonathan Gallimore <
> > jonathan.gallim...@gmail.com>:
> >
> > > Hi All,
> > >
> > > This is a first attempt at a vote for a release of Apache TomEE
> 9.0.0-M3
> > > and Apache TomEE 8.0.5.
> > >
> > > Maven Repo:
> > > https://repository.apache.org/content/repositories/orgapachetomee-1177
> > > https://repository.apache.org/content/repositories/orgapachetomee-1178
> > >
> > > Binaries & Source:
> > > https://dist.apache.org/repos/dist/dev/tomee/staging-1177/tomee-8.0.5/
> > >
> >
> https://dist.apache.org/repos/dist/dev/tomee/staging-1178/tomee-9.0.0-M3/
> > >
> > > Source code:
> > > TomEE 8.0.5:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/tomee/staging-1177/tomee-8.0.5/tomee-project-8.0.5-source-release.zip
> > > TomEE Jakarta Conversion for 9.0.0-M3:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/tomee/staging-1173/tomee-8.0.4/apache-tomee-9.0.0-M2-source-release.zip
> > >
> > > Tags:
> > >
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=tomee.git;a=tag;h=refs/tags/tomee-8.0.5
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=tomee-jakarta.git;a=tag;h=refs/tags/tomee-9.0.0-M3
> > >
> > > Release notes:
> > >
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12348622
> > >
> > > (I'll be going through issues and correcting them where they haven't
> been
> > > marked as complete)
> > >
> > > Please VOTE:
> > >
> > > [+1] Yes, release it
> > > [+0] Not fussed
> > > [-1] Don't release, there's a showstopper (please specify what the
> > > showstopper is)
> > >
> > > Vote will be open for 72 hours.
> > >
> > > Thanks
> > >
> > > Jon
> > >
> >
>


-- 
Atentamente:
César Hernández.

Re: Dockerfiles for 7.1.4

[Cesar Hernandez]

Thanks for the update Rodney.

El jue., 5 nov. 2020 a las 16:12, Jenkins, Rodney J (Rod) (<
jenki...@nationwide.com>) escribió:

> All,
>
> I noticed that 7.1.4 was missed on the last updated.  I will get a card to
> get this done during my next sprint.
>
> Thanks,
> Rod.
>
>

-- 
Atentamente:
César Hernández.

Re: [VOTE] Apache TomEE javaee-api-8.0.5

[Cesar Hernandez]

+1

El mar., 20 oct. 2020 a las 7:14, Daniel Cunha ()
escribió:

> +1
>
> Em ter., 20 de out. de 2020 às 07:55, Jonathan Gallimore <
> jonathan.gallim...@gmail.com> escreveu:
>
> > +1
> >
> > Jon
> >
> > On Mon, Oct 19, 2020 at 9:30 PM Mark Struberg  >
> > wrote:
> >
> > > Hi ladies!
> > >
> > > I'd like to call a VOTE on Apache TomEE javaee-api-8.0.5.
> > >
> > > This mostly contains updates to newer bugfix releases of some spec
> jars.
> > > Including an important hasCode glitch in the CDI-2.0 API.
> > >
> > > The staging repo is:
> > >
> https://repository.apache.org/content/repositories/orgapachetomee-1176/
> > >
> > >
> > > The source zip can be found at
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachetomee-1176/org/apache/tomee/javaee-api/8.0-5/
> > > <
> > >
> >
> https://repository.apache.org/content/repositories/orgapachetomee-1176/org/apache/tomee/javaee-api/8.0-5/
> > > >
> > > sha1 is f6e91c15a8f2e08d2c2ad0f42b03df386287992c
> > >
> > > Please VOTE
> > >
> > > [+1] go ship it
> > > [+0] meh, don't care
> > > [-1] stop, there is a ${showstopper}
> > >
> > > The VOTE is open for 72h
> > >
> > > Here is my own one for the start.
> > > +1 (binding)
> > >
> > > txs and LieGrue,
> > > strub
> >
>
>
> --
> Daniel "soro" Cunha
> https://twitter.com/dvlc_
>


-- 
Atentamente:
César Hernández.

TOMEE-2911 geronimo javamail update

[Cesar Hernandez]

Hi All,

I created https://issues.apache.org/jira/browse/TOMEE-2911 ticket to track
the javamail update to the 1.6 version.
PR is also available now open for review:
https://github.com/apache/tomee/pull/711

-- 
Atentamente:
César Hernández.

Re: How can I help

[Cesar Hernandez]

My opinion would be to do it using only javax namespace.
As far as I understand, current website will automatically auto-generate
the Jakarta version of the example.

El vie., 14 ago. 2020 a las 12:59, José Fernando Málaga Cardoza (<
malag...@tcd.ie>) escribió:

> Hi guys,
>
> I think trying to contribute to examples would be a great place for me to
> start as I always have that feeling that I could make
> better examples than most guides whenever I look at some examples from any
> documentation. Guess it is time to try and
> prove that I can. I saw this:
>
> https://issues.apache.org/jira/browse/TOMEE-2535
>
> and was thinking I could work on this since it looks quite simple. A
> question is would the example have to be done using
> the jakarta namespace or the javax namespace or both?
>
> Best regards,
> Jose Fernado
>
>
> On Tue, 11 Aug 2020 at 19:31, Cesar Hernandez 
> wrote:
>
> > Hi José,
> >
> > Welcome!
> > The following is a crosspost of latest activity:
> >
> > We have prepared some materials to help people like you who are new to
> > TomEE at the following link:
> > http://tomee.apache.org/community/contributing/contribution-tips.html
> >
> > There are a couple of items for you to choose from:
> >
> > - Documentation translation is a great opportunity for new contributions.
> > Check for instance these tickets:
> > Portuguese:https://issues.apache.org/jira/browse/TOMEE-2473
> > Spanish: https://issues.apache.org/jira/browse/TOMEE-2442
> > Additional TomEE website development resources:
> > https://www.tomitribe.com/blog/how-to-contribute-to-the-tomee-website/
> >
> > - When you are ready you can go to JIRA and look through the various
> > tickets
> > that are still unassigned. Feel free to ask as many questions as you like
> > in the mailing list before, during, and after your first contribution!
> >
> >
> >
> https://issues.apache.org/jira/projects/TOMEE/issues/TOMEE-2496?filter=allopenissues
> >
> > The recent work in progress:
> >
> >  - Jakarta EE 8 compliance: Immediate: some help getting people to know
> how
> > to run the TCK. Long-term: help fixing tests
> >
> >  - Jakarta EE 9 compliance: Immediate: help kicking the tires on the
> > prototype 'jakarta' TomEE server; i.e. writing apps that use
> > jakarta.ws.rs.Post, jakarta.persistence.Entity, etc and report issues.
> >
> >  - User list: there might be some questions you know the answers to.
> >
> > Base on your email it seems you gain experience migrating your
> application
> > from javax to jakarta namespace, that is a green field in terms of
> examples
> > and documentation that you can also contribute:
> >
> > Let us know what kind of things sounds interesting and we'll see what
> might
> > fit.
> >
> >
> >
> > El mar., 11 ago. 2020 a las 7:54, José Fernando Málaga Cardoza (<
> > malag...@tcd.ie>) escribió:
> >
> > > Hi guys,
> > >
> > > I have been using TomEE mainly as a way to learn and to practice
> working
> > > with JavaEE. Recently I downloaded the 9.0.0 version and had some
> issues
> > > getting an old project to work on it. After lots of work and reading
> the
> > > comment in the downloads section I saw my issue and that is what made
> me
> > > decide to try and help TomEE. I am currently working as a software
> > > developer in Zurich and have been working with Java for 5 years now and
> > > most of the time I have worked with JavaEE or Spring.
> > >
> > > I guess my main area of interest is in working with online technologies
> > so
> > > if I could contribute there, that would be a plus.
> > >
> > > Best regards,
> > > Jose Fernando
> > >
> >
> >
> > --
> > Atentamente:
> > César Hernández.
> >
>


-- 
Atentamente:
César Hernández.

Re: How can I help

[Cesar Hernandez]

Hi José,

Welcome!
The following is a crosspost of latest activity:

We have prepared some materials to help people like you who are new to
TomEE at the following link:
http://tomee.apache.org/community/contributing/contribution-tips.html

There are a couple of items for you to choose from:

- Documentation translation is a great opportunity for new contributions.
Check for instance these tickets:
Portuguese:https://issues.apache.org/jira/browse/TOMEE-2473
Spanish: https://issues.apache.org/jira/browse/TOMEE-2442
Additional TomEE website development resources:
https://www.tomitribe.com/blog/how-to-contribute-to-the-tomee-website/

- When you are ready you can go to JIRA and look through the various tickets
that are still unassigned. Feel free to ask as many questions as you like
in the mailing list before, during, and after your first contribution!

https://issues.apache.org/jira/projects/TOMEE/issues/TOMEE-2496?filter=allopenissues

The recent work in progress:

 - Jakarta EE 8 compliance: Immediate: some help getting people to know how
to run the TCK. Long-term: help fixing tests

 - Jakarta EE 9 compliance: Immediate: help kicking the tires on the
prototype 'jakarta' TomEE server; i.e. writing apps that use
jakarta.ws.rs.Post, jakarta.persistence.Entity, etc and report issues.

 - User list: there might be some questions you know the answers to.

Base on your email it seems you gain experience migrating your application
from javax to jakarta namespace, that is a green field in terms of examples
and documentation that you can also contribute:

Let us know what kind of things sounds interesting and we'll see what might
fit.



El mar., 11 ago. 2020 a las 7:54, José Fernando Málaga Cardoza (<
malag...@tcd.ie>) escribió:

> Hi guys,
>
> I have been using TomEE mainly as a way to learn and to practice working
> with JavaEE. Recently I downloaded the 9.0.0 version and had some issues
> getting an old project to work on it. After lots of work and reading the
> comment in the downloads section I saw my issue and that is what made me
> decide to try and help TomEE. I am currently working as a software
> developer in Zurich and have been working with Java for 5 years now and
> most of the time I have worked with JavaEE or Spring.
>
> I guess my main area of interest is in working with online technologies so
> if I could contribute there, that would be a plus.
>
> Best regards,
> Jose Fernando
>


-- 
Atentamente:
César Hernández.

Re: [VOTE] Missing artifact - TomEE 8.0.4

[Cesar Hernandez]

+1

On Tue, Aug 11, 2020 at 06:49 Daniel Dias Dos Santos <
daniel.dias.analist...@gmail.com> wrote:

> +1
> --
>
> *Daniel Dias dos Santos*
> Java Developer
> SouJava & JCP Member
> GitHub: https://github.com/Daniel-Dos
> Linkedin: www.linkedin.com/in/danieldiasjava
> Twitter: http://twitter.com/danieldiasjava
>
>
> Em ter., 11 de ago. de 2020 às 06:53, Zowalla, Richard <
> richard.zowa...@hs-heilbronn.de> escreveu:
>
> > +1
> >
> > Am Dienstag, den 11.08.2020, 09:58 +0100 schrieb Jonathan Gallimore:
> > > Hi All,
> > >
> > > We're missing an artifact on our download page for TomEE 8.0.4
> > > Webprofile
> > > (thanks Richard Zowalla for pointing this out).
> > >
> > > This is already in Maven:
> > > https://repo1.maven.org/maven2/org/apache/tomee/apache-tomee/8.0.4/,
> > > but
> > > was missed in the staging directory for the vote, and hence is
> > > missing from
> > > the promotion to the website.
> > >
> > > I don't know if a vote is needed to add the missing artifact, but I
> > > think
> > > it covers us well to have one anyway. Here's the reference to the
> > > original
> > > vote:
> > >
> > >
> >
> https://lists.apache.org/thread.html/r5d6b2fe8998da647fdcf405ab721e6f882d40f271b9a92527257bd45%40%3Cdev.tomee.apache.org%3E
> > >
> > > I've added the missing artifacts to the staging area here:
> > > https://dist.apache.org/repos/dist/dev/tomee/staging-1173/tomee-8.0.4/
> > >
> > > Please VOTE:
> > >
> > > [+1] Yes, release it
> > > [+0] Not fussed
> > > [-1] Don't release, there's a showstopper (please specify what the
> > > showstopper is)
> > >
> > > Vote will be open for 72 hours.
> > >
> > > Thanks
> > >
> > > Jon
> >
>
-- 
Atentamente:
César Hernández.

Re: [VOTE] Release Apache TomEE 7.0.9

[Cesar Hernandez]

+1

On Wed, Aug 5, 2020 at 14:49 Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:

> Hi All,
>
> I am delighted to present a vote for Apache TomEE 7.0.9
>
>
> Maven Repo:
> https://repository.apache.org/content/repositories/orgapachetomee-1175/
>
> Binaries & Source:
> https://dist.apache.org/repos/dist/dev/tomee/staging-1175/tomee-7.0.9/
>
> Source code:
>
> https://dist.apache.org/repos/dist/dev/tomee/staging-1175/tomee-7.0.9/tomee-project-7.0.9-source-release.zip
>
> Tags:
>
> https://gitbox.apache.org/repos/asf?p=tomee.git;a=tag;h=refs/tags/tomee-7.0.9
>
> Release notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12348295
>
> Please VOTE:
>
> [+1] Yes, release it
> [+0] Not fussed
> [-1] Don't release, there's a showstopper (please specify what the
> showstopper is)
>
> Vote will be open for 72 hours.
>
> Here is my +1.
>
> Thanks
>
> Jon
>
-- 
Atentamente:
César Hernández.

Re: [VOTE] Release TomEE 7.1.4

[Cesar Hernandez]

+1

On Wed, Aug 5, 2020 at 14:44 Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:

> Hi All,
>
> I am delighted to present a vote for Apache TomEE 7.1.4
>
>
> Maven Repo:
> https://repository.apache.org/content/repositories/orgapachetomee-1174/
>
> Binaries & Source:
> https://dist.apache.org/repos/dist/dev/tomee/staging-1174/tomee-7.1.4/
>
> Source code:
>
> https://dist.apache.org/repos/dist/dev/tomee/staging-1174/tomee-7.1.4/tomee-project-7.1.4-source-release.zip
>
> Tags:
>
> https://gitbox.apache.org/repos/asf?p=tomee.git;a=tag;h=refs/tags/tomee-7.1.4
>
> Release notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12348433
>
> Please VOTE:
>
> [+1] Yes, release it
> [+0] Not fussed
> [-1] Don't release, there's a showstopper (please specify what the
> showstopper is)
>
> Vote will be open for 72 hours.
>
> Here is my +1.
>
> Thanks
>
> Jon
>
-- 
Atentamente:
César Hernández.

Re: PR - Issue of the Jira TOMEE-2874

[Cesar Hernandez]

Thank you for the PR.
PR is now merged and Jira was also updated.

El mié., 29 jul. 2020 a las 5:17, Evaldo Junior ()
escribió:

> Please, anybody revise my translation, the link of the issue is
> https://issues.apache.org/jira/browse/TOMEE-2874.
> <https://issues.apache.org/jira/browse/TOMEE-2855>
> PR - https://github.com/apache/https://github.com/apache/tomee/pull/694
>
>
> Regards,
>
>
> Evaldo Junior
>
> <https://github.com/apache/tomee/pull/694>
>
> Em ter., 14 de jul. de 2020 às 19:46, Cesar Hernandez <
> cesargu...@gmail.com>
> escreveu:
>
> > Thank you Evaldo.
> > Looking forward to review your PR.
> >
> > El mar., 14 jul. 2020 a las 7:27, Evaldo Junior (<
> evaldoapjun...@gmail.com
> > >)
> > escribió:
> >
> > > I go make the translation of the documentation, according to issue
> 2874.
> > > Follow the link of the issue:
> > > https://issues.apache.org/jira/browse/TOMEE-2874
> > > <https://issues.apache.org/jira/browse/TOMEE-2857>
> > >
> > >
> > > Regards,
> > >
> > >
> > > Evaldo Junior
> > >
> >
> >
> > --
> > Atentamente:
> > César Hernández.
> >
>


-- 
Atentamente:
César Hernández.

Re: How can I help?

[Cesar Hernandez]

Hi Chaitanya

Welcome, the following is a crosspost of latest activity:

We have prepared some materials to help people like you who are new to
TomEE at the following link:
http://tomee.apache.org/community/contributing/contribution-tips.html

There are a couple of items for you to choose from:

- Documentation translation is a great opportunity for new contributions.
Check for instance these tickets:

   - Portuguese:https://issues.apache.org/jira/browse/TOMEE-2473
   - Spanish: https://issues.apache.org/jira/browse/TOMEE-2442

Additional TomEE website development resources:
https://www.tomitribe.com/blog/how-to-contribute-to-the-tomee-website/

- When you are ready you can go to JIRA and look through the various tickets
that are still unassigned. Feel free to ask as many questions as you like
in the mailing list before, during, and after your first contribution!

https://issues.apache.org/jira/projects/TOMEE/issues/TOMEE-2496?filter=allopenissues

The recent work in progress:

 - Jakarta EE 8 compliance: Immediate: some help getting people to know how
to run the TCK. Long-term: help fixing tests

 - Jakarta EE 9 compliance: Immediate: help kicking the tires on the
prototype 'jakarta' TomEE server; i.e. writing apps that use
jakarta.ws.rs.Post, jakarta.persistence.Entity, etc and report issues.

 - User list: there might be some questions you know the answers to.

Let us know what kind of things sounds interesting and we'll see what might
fit.

El vie., 24 jul. 2020 a las 9:46, Chaitanya Chunduri (<
chaitanyach...@gmail.com>) escribió:

> Hi Team,
>
> My name is Chaitanya, I’m a full stack developer. I work from Hyderabad,
> India, but because of current pandemic situation I’m working from my home
> village Karamchedu, which is small village inside Andhra Pradesh, India. I
> would like to contribute to J2EE and TomEE projects. My skill set is Java,
> Kotlin, Sprint Boot, Javascript and React JS. My interests are
> Micro-profile, Dependency Injection, JSON Parsing, Transaction Management.
> I’m good at developing front end pages as well. I request you to assign
> some task to me so that I’lll get started with the TomEE contribution.
>
>
> Thanks and Regards,
> Chaitanya Chunduri



-- 
Atentamente:
César Hernández.

Re: [VOTE] Release TomEE 8.0.4 and 9.0.0-M2

[Cesar Hernandez]

+1 thank you!.

El mié., 22 jul. 2020 a las 9:24, Vicente Rossello ()
escribió:

> +1 for tomee 8.0.4  Tested in our project
>
> I can't vote 9.0.0-M2 since I haven't tested it.
>
> On Wed, Jul 22, 2020 at 4:57 PM Jonathan Gallimore <
> jonathan.gallim...@gmail.com> wrote:
>
> > Hi All,
> >
> > I am delighted to present a vote for Apache TomEE 9.0.0-M2 and Apache
> TomEE
> > 8.0.4.
> >
> >
> > Maven Repo:
> > https://repository.apache.org/content/repositories/orgapachetomee-1173/
> >
> > Binaries & Source:
> > https://dist.apache.org/repos/dist/dev/tomee/staging-1173/tomee-8.0.4/
> >
> > Source code:
> > TomEE 8.0.4:
> >
> >
> https://dist.apache.org/repos/dist/dev/tomee/staging-1173/tomee-8.0.4/tomee-project-8.0.4-source-release.zip
> > TomEE Jakarta Conversion for 9.0.0-M2:
> >
> >
> https://dist.apache.org/repos/dist/dev/tomee/staging-1173/tomee-8.0.4/apache-tomee-9.0.0-M2-source-release.zip
> >
> > Tags:
> >
> >
> >
> https://gitbox.apache.org/repos/asf?p=tomee.git;a=tag;h=refs/tags/tomee-project-8.0.4
> >
> >
> https://gitbox.apache.org/repos/asf?p=tomee-jakarta.git;a=tag;h=refs/tags/tomee-9.0.0-M2
> >
> > Release notes:
> >
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12348414
> >
> > Please VOTE:
> >
> > [+1] Yes, release it
> > [+0] Not fussed
> > [-1] Don't release, there's a showstopper (please specify what the
> > showstopper is)
> >
> > Vote will be open for 72 hours.
> >
> > Here is my +1.
> >
> > Thanks
> >
> > Jon
> >
>


-- 
Atentamente:
César Hernández.

Re: TOMEE-1399 Potential NPE

[Cesar Hernandez]

Hi David,

+1 on your PR. Thank you much.

The CI errors are related with a work in progress to enable GitHub actions
into the project for proactive PR feedback.
As I recall, currently the feedback we have in buildbot CI and Jenkins is
after a merge reaches master.
https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8
https://builds.apache.org/job/TomEE/

This is how I validated the PR, it may be helpful for newer contributors we
have had in the last couple of months ;).. or to learn a better way to do
it in case one would like to provide feedback.

0. Analyzed the code to understand the change

1. git checkout 
I use hub for github [1], so I get all my work from the command line, I
also create PR using hub after my git push.

2. git pull upstream master
This allowed the latest apache/tomee master to be merged into your PR
locally.

3. mvn clean install -DskipTests
Build without tests to make sure to have all the dependencies in my local
repo that these days have been deleted/recreated due to other duties.

4. mvn --fail-at-end test -Pall-adapters -Dsurefire.useFile=false
-DdisableXmlReport=true -Dopenejb.arquillian.debug=true  -pl
container/openejb-core
I executed only the test related to the maven module related to your PR.
This took around 40 minutes on my laptop.

5. I found one test fail [2], but I notice it was not related with your PR
and actually a test that I have a PR open with a patch already [3].


[1] https://hub.github.com/

[2]
[ERROR] Failures:
[ERROR]   JMS2AMQTest.sendToMdbWithTxAndCheckLeaks:309 expected:<0> but
was:<1>
[INFO]
[ERROR] Tests run: 3945, Failures: 1, Errors: 0, Skipped: 2

[3] https://github.com/apache/tomee/pull/678


El sáb., 11 jul. 2020 a las 4:51, David Salter ()
escribió:

> Thanks Cesar,
>
> I got a notification about that.  Let me know if there is anything I
> need to do on the PR regarding this.  :)
>
> David.
>
> On 11/07/2020 04:50, Cesar Hernandez wrote:
> > Hi David,
> > Thanks for the PR, FYI,  the recently Github Actions setup might throw
> red
> > build on your PR.
> >
> > I'm currently checking the Action to get more stable CI results.
> >
> >
> > El vie., 10 jul. 2020 a las 11:35, Daniel Dias Dos Santos (<
> > daniel.dias.analist...@gmail.com>) escribió:
> >
> >> Hello,
> >>
> >> very good, thanks  :  )
> >> --
> >>
> >> *Daniel Dias dos Santos*
> >> Java Developer
> >> SouJava & JCP Member
> >> GitHub: https://github.com/Daniel-Dos
> >> Linkedin: www.linkedin.com/in/danieldiasjava
> >> Twitter: http://twitter.com/danieldiasjava
> >>
> >>
> >> Em sex., 10 de jul. de 2020 às 14:01, David Salter <
> da...@davidsalter.uk>
> >> escreveu:
> >>
> >>> Hi,
> >>>
> >>> I've been going through open Jira issues and found TOMEE-1399. and just
> >>> submitted a PR for this.
> >>>
> >>> Basically, this is to move an if statement earlier in the code to avoid
> >>> a potential Null Pointer Exception.
> >>>
> >>> https://github.com/apache/tomee/pull/675
> >>>
> >>> Can someone take a look and see if this is OK?
> >>>
> >>>
> >>> Thanks,
> >>>
> >>> David.
> >>>
> >>> --
> >>> David Salter
> >>>
> >>>
> >
> --
> David Salter
>
>
>

-- 
Atentamente:
César Hernández.