AW: Next TomEE+ 7.1.x release

[Zowalla, Richard]

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
> > > https://issues.apache.org/jira/browse/OPENEJB-2145
> > >
> > > Here is the patch:
> > >
> > > TOMEE-2919 : Fix for ConcurrentModificationException error deploying
> > > … by
> > > gnarayan1 · Pull Request #868 · apache/tomee · GitHub
> > > 
> > >
> > > Thanks.
> > >
> > > Geeth
> >
>

How can I help?

[Zoltán Tichov]

Hi!

I live in Hungary. I am working at an IT company as a software developer, I
develop java
webapps with jsf (PrimeFaces) and microservice like apps without any
container technology
and Oracle database.

We want to switch to jakarta ee 9 at the company, but unfortunately we ran
into problems with tomee 9 and I would like to contribute to fixing these
bugs and possibly improving tomee jakarta 10. (I'm sorry to read on another
tomee mailing list, that you had to skip jakarta ee 8 and 9 compliance
entirely)
I use java 11 and netbeans on windows 10. If we don't have to, we don't
want to use another app server because we've been using tomee since 1.7.3.

Best regards: Zoltán Tichov

Re: Re: Re: Follow-up to 8.0.11: Update of release documentation

[Jenkins, Rodney J (Rod)]

Thank you!


On 4/23/22, 4:18 AM, "Zowalla, Richard"  
wrote:

Hi Rod,

I updated the release tools (with TOMEE-3921), so we are now creating
consistent hashes regardless of the tooling used (homebrew release
tools vs linux onboard), i.e. it will be " filename".

Gruß
Richard

Am Freitag, dem 22.04.2022 um 21:41 + schrieb Jenkins, Rodney J
(Rod):
> <<
> Do you have a preference for automation in your environment and
> for
> docker?
> 
> My only preference is consistency.  I have no technical preference
> one way or the other.  I can script it either way.  I do not want to
> alter Dockerfiles each time we do a release.
> 
> Thanks,
> Rod.
> 
> 
> On 4/22/22, 11:32 AM, "Richard Zowalla"  wrote:
> 
> Nationwide Information Security Warning: This is an EXTERNAL
> email. Use CAUTION before clicking on links, opening attachments, or
> responding. (Sender: 
> dev-return-29302-JENKIR14=nationwide@tomee.apache.org)
> 
> -
> -
> 
> 
> Hi Rod
> 
> > My counterparts have reported that the sha files are in
> different 
> > format than the last version, but the same as 8.0.7. 
> 
> >It would be nice if we could have a permanent standard.   When
> we
> >change the formats, it breaks automation on our end and in the
> docker
> >images.
> 
> I agree - this time, the SHA512 hashes are created using our 
> https://github.com/apache/tomee-release-tools 
> 
> I quickly checked the other releases (1.7.x, 7.x, 7.1.x), which
> follow
> the same pattern.
> 
> BUT I agree, that it was different in previous TomEE 8 releases -
> perhaps the SHA512 hashes were not created using the tomee-
> release-
> tools. Nevertheless, we can enhance the release tools to follow
> the
> unix like pattern:
> 
>  filename
> 
> instead of
> 
> 
> 
> I have no preference ;) - for the first option, we need to update
> the
> release tools to include the filename to the .sha512 files. That
> would
> beconsistent in case the release hashs aren't created via the
> tomee-
> release-tools.
> 
> Do you have a preference for automation in your environment and
> for
> docker?
> 
> Gruß 
> Rchard
> 
> 
> 
> 
> Am Freitag, dem 22.04.2022 um 15:26 + schrieb Jenkins, Rodney
> J
> (Rod):
> > Richard,
> > 
> > Thank you for the release and congrats on your 1st release.
> > 
> > My counterparts have reported that the sha files are in
> different
> > format than the last version, but the same as 8.0.7.
> > 
> > It would be nice if we could have a permanent standard.   When
> we
> > change the formats, it breaks automation on our end and in the
> docker
> > images.
> > 
> > I've not had the time to verify this for myself, I will get to
> that
> > in the next couple of days.
> > 
> > Thank you,
> > Rod.
> > 
> > From: Zowalla, Richard 
> > Sent: Friday, April 22, 2022 1:37 AM
> > To: dev@tomee.apache.org 
> > Subject: [EXTERNAL] Follow-up to 8.0.11: Update of release
> > documentation
> > 
> > Hi all,
> > 
> > after conducting my first release, I put my notes together and
> > updated
> > our release documentation:
> > https://tomee.apache.org/dev/release-tomee.html
> > 
> > It might not be complete and might require some further
> polishing but
> > I
> > think, that this will help others in conducting a release. The
> > initial
> > ASF-related setup + GPG keys requires some effort ;)
> > 
> > In general, we learned that teaming up (committer + pmc) for a
> > release
> > works quite well and it was a pleassure to work with JL on
> 8.0.11 :)
> > 
> > Most of the mechanical steps can be conducted with committer
> access
> > privileges (building, tagging, nexus/maven deploy, staging
> artifacts
> > to
> > dist/dev); some formal steps like open/close the VOTE, moving
> the
> > artifacts from dist/dev to dist/release require a PMC member to
> be
> > involved.
> > 
> > Gruß
> > Richard
> 
> 

Re: Re: Follow-up to 8.0.11: Update of release documentation

[Zowalla, Richard]

Hi Rod,

I updated the release tools (with TOMEE-3921), so we are now creating
consistent hashes regardless of the tooling used (homebrew release
tools vs linux onboard), i.e. it will be " filename".

Gruß
Richard

Am Freitag, dem 22.04.2022 um 21:41 + schrieb Jenkins, Rodney J
(Rod):
> <<
> Do you have a preference for automation in your environment and
> for
> docker?
> 
> My only preference is consistency.  I have no technical preference
> one way or the other.  I can script it either way.  I do not want to
> alter Dockerfiles each time we do a release.
> 
> Thanks,
> Rod.
> 
> 
> On 4/22/22, 11:32 AM, "Richard Zowalla"  wrote:
> 
> Nationwide Information Security Warning: This is an EXTERNAL
> email. Use CAUTION before clicking on links, opening attachments, or
> responding. (Sender: 
> dev-return-29302-JENKIR14=nationwide@tomee.apache.org)
> 
> -
> -
> 
> 
> Hi Rod
> 
> > My counterparts have reported that the sha files are in
> different 
> > format than the last version, but the same as 8.0.7. 
> 
> >It would be nice if we could have a permanent standard.   When
> we
> >change the formats, it breaks automation on our end and in the
> docker
> >images.
> 
> I agree - this time, the SHA512 hashes are created using our 
> https://github.com/apache/tomee-release-tools 
> 
> I quickly checked the other releases (1.7.x, 7.x, 7.1.x), which
> follow
> the same pattern.
> 
> BUT I agree, that it was different in previous TomEE 8 releases -
> perhaps the SHA512 hashes were not created using the tomee-
> release-
> tools. Nevertheless, we can enhance the release tools to follow
> the
> unix like pattern:
> 
>  filename
> 
> instead of
> 
> 
> 
> I have no preference ;) - for the first option, we need to update
> the
> release tools to include the filename to the .sha512 files. That
> would
> beconsistent in case the release hashs aren't created via the
> tomee-
> release-tools.
> 
> Do you have a preference for automation in your environment and
> for
> docker?
> 
> Gruß 
> Rchard
> 
> 
> 
> 
> Am Freitag, dem 22.04.2022 um 15:26 + schrieb Jenkins, Rodney
> J
> (Rod):
> > Richard,
> > 
> > Thank you for the release and congrats on your 1st release.
> > 
> > My counterparts have reported that the sha files are in
> different
> > format than the last version, but the same as 8.0.7.
> > 
> > It would be nice if we could have a permanent standard.   When
> we
> > change the formats, it breaks automation on our end and in the
> docker
> > images.
> > 
> > I've not had the time to verify this for myself, I will get to
> that
> > in the next couple of days.
> > 
> > Thank you,
> > Rod.
> > 
> > From: Zowalla, Richard 
> > Sent: Friday, April 22, 2022 1:37 AM
> > To: dev@tomee.apache.org 
> > Subject: [EXTERNAL] Follow-up to 8.0.11: Update of release
> > documentation
> > 
> > Hi all,
> > 
> > after conducting my first release, I put my notes together and
> > updated
> > our release documentation:
> > https://tomee.apache.org/dev/release-tomee.html
> > 
> > It might not be complete and might require some further
> polishing but
> > I
> > think, that this will help others in conducting a release. The
> > initial
> > ASF-related setup + GPG keys requires some effort ;)
> > 
> > In general, we learned that teaming up (committer + pmc) for a
> > release
> > works quite well and it was a pleassure to work with JL on
> 8.0.11 :)
> > 
> > Most of the mechanical steps can be conducted with committer
> access
> > privileges (building, tagging, nexus/maven deploy, staging
> artifacts
> > to
> > dist/dev); some formal steps like open/close the VOTE, moving
> the
> > artifacts from dist/dev to dist/release require a PMC member to
> be
> > involved.
> > 
> > Gruß
> > Richard
> 
> 


smime.p7s
Description: S/MIME cryptographic signature

Re: Re: [ANN] Apache TomEE 8.0.11

[Zowalla, Richard]

Hi,

added some comments regarding the "uid" used in the comment.
The rest looks good to me. Thanks for preparing!

Gruß
Richard


Am Freitag, dem 22.04.2022 um 22:13 + schrieb Jenkins, Rodney J
(Rod):
> Richard,
> 
> I added your key to the Docker files.  Can you please verify your
> information here:
> 
> https://github.com/tomitribe/docker-tomee/pull/65/files
> 
> 
> Also, if someone would review the changes, I would appreciate it.  If
> it is not approved on Monday, I will merge.
> 
> Thank you,
> Rod.
> 
> 
> On 4/22/22, 11:32 AM, "Richard Zowalla"  wrote:
> 
> Nationwide Information Security Warning: This is an EXTERNAL
> email. Use CAUTION before clicking on links, opening attachments, or
> responding. (Sender: 
> dev-return-29303-JENKIR14=nationwide@tomee.apache.org)
> 
> -
> -
> 
> 
> Thanks, Rod!
> 
> Am Freitag, dem 22.04.2022 um 15:21 + schrieb Jenkins, Rodney
> J
> (Rod):
> > I will get started on the Docker images.
> > 
> > Thank you,
> > Rod.
> > 
> > From: Richard Zowalla 
> > Sent: Friday, April 22, 2022 5:00:58 AM
> > To: dev@tomee.apache.org ; 
> > us...@tomee.apache.org ; 
> annou...@apache.org
> > 
> > Subject: [EXTERNAL] [ANN] Apache TomEE 8.0.11
> > 
> > Nationwide Information Security Warning: This is an EXTERNAL
> email.
> > Use CAUTION before clicking on links, opening attachments, or
> > responding. (Sender: 
> > users-return-28024-JENKIR14=nationwide@tomee.apache.org)
> > 
> > -
> --
> > ---
> > 
> > 
> > The Apache TomEE team is pleased to announce the availability
> of
> > TomEE
> > 8.0.11
> > 
> > Apache TomEE delivers enterprise application containers and
> services
> > based on, but not limited to the Enterprise JavaBeans
> Specification
> > and
> > Java Enterprise Edition Specifications.
> > 
> > These releases primarily provide bug fixes, documentation and
> update
> > the dependencies TomEE uses.
> > 
> > Full release notes:
> > 
> > - https://tomee.apache.org/8.0.11/release-notes.html
> > -
> > 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12351352
> > 
> > Downloads are available at: 
> https://tomee.apache.org/download.html
> > 
> > - The Apache TomEE team
> > 
> 
> 


smime.p7s
Description: S/MIME cryptographic signature