No objections.
Am Mittwoch, dem 21.12.2022 um 10:18 +0100 schrieb Jean-Louis Monteiro:
> No objections. It was also on top of my head to do it before end of
> the
> year.
>
>
> I need to look at the failures. I got some exchanges with Tomcat
> folks and
> Tomcat passes the TCK. But they said
Hi JL,
+1 - let's roll out an M9 / RC1.
Feedback from the community is super valuable at this stage.
Gruß
Richard
Am Freitag, dem 28.10.2022 um 10:01 +0200 schrieb Jean-Louis Monteiro:
> Hi all,
>
> It's been a hard and long journey, but we are there.
>
> We implemented the last
Hi,
I dropped a message in the builds slack channel to get some thoughts on
our PR issue. Maybe they can give us some hints to docs.
If the topic is to broad / wide for a quick slack chat, I will sent a
mail to builds@ to get some thoughts / ideas.
I agree with David, that we cannot be the
t; > git pull
> org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout
> conflict
> with files:
> docs/comparison.adoc
>
> i'll update to do a reset hard on remote instead of pull
>
> and commit that as a pull request, if it can help
>
>
> On Thu, 20 O
Might be related to "master" -> "main" switch a while back.
I added a commit, I had already made in my local repository after
preparing release notes.
Don't know, if this solves the issue but could be a thing to look at.
Am Donnerstag, dem 20.10.2022 um 16:53 +0200 schrieb Swell:
> looked and
Hi Zoltan,
the arquillian config is located in
/src/test/java/resources/arquillian.xml.
In this file, you can find a "debug" property, which you can set to
"true" to enable the debug capabilities of TomEE (i.e. start with a
debugger backend).
You can debug single tests by editing "tck-dev.xml"
Here is my own +1 (binding)
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.
> >
> >
"or as long as needed" ;-) - waiting for PMC votes.
Am Dienstag, dem 18.10.2022 um 08:36 +0200 schrieb Alex The Rocker:
> Hi here, the vote for TomEE 8.0.13 launched 1 week ago was supposed
> to
> hold for 72 hours...
> Is it still valid or will a new release candidate show up ?
>
> Alex
>
>
Hi,
I am starting this test on a virtual machine in our infra now.
@all For building main you need to either use a JDK 11 or JDK 17. This
information is also relevant as well as the Maven version used to for
building.
In addition, it might be required to switch the git repo url in the sh
script
ced tests
> with 8.0.13 candidate release.
>
> Thanks,
> Alex
>
> Le mar. 11 oct. 2022 à 22:28, Zowalla, Richard
> a écrit :
> > Good catch. This is expected:
> >
> > https://issues.apache.org/jira/browse/TOMEE-4021
> >
> > or
> >
> &
I see ehcache*.jar is removed in TomEE+ 8.0.13 => is it
> intentional (I love seeing less JARs;) ?
>
> Alex
>
> Le mar. 11 oct. 2022 à 22:17, Zowalla, Richard
> a écrit :
> >
> > I am currently not on my dev system but I checked via:
> >
> > $ gpg --bat
I am currently not on my dev system but I checked via:
$ gpg --batch --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys
B83D15E72253ED1104EB4FBBDAB472F0E5B8A431
$ gpg --verify apache-tomee-8.0.13-plus.tar.gz.asc apache-tomee-8.0.13-
plus.tar.gz
gpg: Signatur vom Di 11 Okt 2022 13:14:04 CEST
Perhaps worth a mail to build@ ?
I can't imagine that others do not run into same issues related to
random number generations / entropy issues.
Gruß
Richard
Am Dienstag, dem 11.10.2022 um 17:50 +0200 schrieb Jean-Louis Monteiro:
> Yes you are correct. This is a possible problem.
>
> Digging
Hi,
The INFRA docs [1] do not mention any constraint that the PR needs to
come from the same repository.
It is also a problem, that we need to rely on different versions of
Java based on a given branch, i.e. Java 8 for 8.x and Java 11 for 9.x,
etc - there is no easy way to decide which one to
> One thing we need to start removing for TomEE 10 is all the shading
> operations we do on various libraries, CXF being one of them. They
make
>TomEE development harder and also break dependency management.
+1 - it is definitley a pain ;)
Am Montag, dem 10.10.2022 um 10:28 +0200 schrieb
> TomEE 8.0.12 is already affected by these 2 CVE, right?
Yes (+ some others as discussed in the 'Cut a 8.0.13' thread).
Gruß
Richard
Am Sonntag, dem 09.10.2022 um 10:59 +0200 schrieb Swell:
> TomEE 8.0.12 is already affected by these 2 CVE, right?
>
> i am unsure in terms of corporate image.
.
Gruß
Richard
[1] https://lists.apache.org/thread/rzww6qqt06wmvcf9hv607o63ddm8mzzt
Am Samstag, dem 08.10.2022 um 11:33 + schrieb Zowalla, Richard:
> Hi David,
>
> good catch! Looks like we didn't were that far with the build in
> July,
> so didn't notice that one :)
>
&
Hi David,
good catch! Looks like we didn't were that far with the build in July,
so didn't notice that one :)
It looks like CXF 3.5.x depends on xmslec 2.3.0 - I tested it with
2.3.0, but no luck either. Needs some digging, upgrade / patching.
For now, I will revert the upgrade commit to the
-Louis
Monteiro:
> I'm fully focused on TomEE 9 at the moment. I'll have a look to the
> BVal
> failure though in case it comes to my mind.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Thu, Oct 6, 2022 at 2:31 PM Zow
for:
> >
> > CVE-2021-43980 Apache Tomcat - Information Disclosure
> >
> > Kind regards,
> > Alex
> >
> > Le mer. 28 sept. 2022 à 18:45, Zowalla, Richard
> > a écrit :
> > > Hi all,
> > >
> > > our last 8.x release was in
Thanks David for the work!
The CI looks good (compared to main):
https://ci-builds.apache.org/job/Tomee/job/TOMEE-4050/
Gruß
Richard
Am Montag, dem 03.10.2022 um 21:47 +0200 schrieb Jean-Louis Monteiro:
> That sounds great.
> Good feature in addition to the bean validation support for claims.
MEE-4053) are triggered.
Gruß
Richard
Am Donnerstag, dem 29.09.2022 um 11:53 + schrieb Zowalla, Richard:
> We have some results from two runs, which are close in terms of
> failed
> test + they look similar to the ones on master ;-)
>
> Looks like our last dependency update ki
ard !
>
> while it builds i'll clean some props on my own branch using David
> suggestions :
>
> removing api, tck, and impl prefixes and have separate props for
> microprofile api and smallrye impl
>
> --
> Swell
>
> On Wed, 28 Sept 2022 at 20:21, Zowalla, Richard
Regarding CI:
I just pushed Swell's branch as a branch named TOMEE-4053 to the TomEE
main repo and we will get some CI results via
https://ci-builds.apache.org/job/Tomee/job/TOMEE-4053/ soon (6-8h) ;-)
I have no hard opinion regarding version.foo vs version.groupid.foo as
long as we are
Hi,
yeah, such PRs are difficult to review by nature :)
Thanks for the effort to make it consistent and more clear!
Personally, I am fine with the proposal.
If we don't want to do the "big bang integration" approach, we can
easily setup a CI job on jenkins (similar to our full build by simply
I think, that we are an app server first and not a logging framework
(;-)), so I am fine with
"I have no idea what all that code does and I'm happy when I don't have to look
at it".
However, I agree with JL, that we are really close to passing the TCK again,
which would allow to cut a sweet &
Hi JL,
really great news!
Thanks a lot.
Richard
Am Mittwoch, dem 21.09.2022 um 17:01 +0200 schrieb Jean-Louis Monteiro:
> Hi all,
>
> After working quite hard moving TomEE to jakarta namespace (TomEE 9
> for EE
> 9.1), we started implementing MicroProfile 5.0 using SmallRye.
>
> Looks like we
Hi all,
our last 8.x release was in June and we have 22 pending updates/issues
for 8.0.13. Mostly dependency updates (johnzon, dbcp2, myfaces, hsqldb,
tomcat, jakarta faces), and some minor bugs (windows, jdk17+ related
backports), see below.
We might need to go through the 3rd party libs again
Sure.
I created a related Jira: TOMEE-4025
In addition, I already asked INFRA, if this is a self service thing or if they
need a ticket to switch the "default" branch for the GitHub/GitBox sync things.
Gruß
Richard
Von: Jean-Louis Monteiro
Gesendet: Dienstag,
nto my mind while thinking about it. A similar
> > > > > discussion needs to be done for 1.7.x and 7.0.x if we find
> > > > > some
> > > > > consensus for the 7.1.x series.
> > > > >
> > > > > I am a bit torn apar
Hi,
thanks for the concerns raised. Better to check the CVE report and do a re-roll
;-)
@JL: Will take a look.
@Alex Thanks. We might not be able to address all CVEs as some of the libs used
for EE7 aren't patched / updated anymore. I will have a look.
Gruß
Richard
Hi,
we had a discussion regarding a release of TomEE 7.1.x in April 22 [1].
After the discussion I fixed the CI build and updated some dependencies
mentioned in the discussion.
The (current) changelog looks like:
Bug
[TOMEE-2125] - Datasource config: MaxWait,
timeBetweenEvictionRunsMillis and
Thanks Jon!
Both should be fixed now :)
Am Montag, dem 04.07.2022 um 13:13 +0200 schrieb Jean-Louis Monteiro:
> Thanks Jon,
>
> Created 2 issues (TOMEE-4007 and TOMEE-4008) under
> https://issues.apache.org/jira/browse/TOMEE-3862
>
>
> --
> Jean-Louis Monteiro
>
Hi JL,
sounds good :) - +1
Gruß
Richard
Am Freitag, dem 24.06.2022 um 11:57 +0200 schrieb Jean-Louis Monteiro:
> Hi,
>
> We have now completed all releases on libraries (specs for
> activation,
> mail, mail provider, BatchEE, OWB, BVal, Johnzon, etc). So we should
> be
> able to release it
Hi,
I can confirm, that the ZIP files are corrupted:
https://dist.apache.org/repos/dist/dev/tomee/tomee-8.0.12/apache-tomee-8.0.12-microprofile.zip
https://dist.apache.org/repos/dist/dev/tomee/tomee-8.0.12/apache-tomee-8.0.12-plume.zip
<https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://www.packtpub.com/application-development/
+1
Von: Jean-Louis Monteiro
Gesendet: Freitag, 3. Juni 2022 08:49:23
An: dev@tomee.apache.org
Betreff: Release TomEE 8.0.12
Hi all,
We have a couple of requested fixes on the TomEE 8.x branch. Should we do a
release?
--
Jean-Louis Monteiro
erwise, we will need to take a dive into the
imap spec / server-side impl to get any clues :)
Gruß
Richard
Am Dienstag, dem 24.05.2022 um 19:46 +0000 schrieb Zowalla, Richard:
> Hi,
>
> I spend some more time on the mail tck and got some additional
> insights:
>
> There is
be.com
> > >
> > >
> > > On Thu, May 12, 2022 at 9:29 AM Wiesner, Martin <
> > > martin.wies...@hs-heilbronn.de> wrote:
> > >
> > > > +1
> > > >
> > > > Best
> >
nt website and the dev/admin/migration
> documentation
> would also benefit from a careful review and a subsequent review and
> revise.
>
> Thank you
> -AD
>
> On Mon, May 9, 2022 at 12:07 AM Zowalla, Richard <
> richard.zowa...@hs-heilbronn.de> wrote:
>
> > Hi AD
Am Mittwoch, dem 25.05.2022 um 02:28 +0200 schrieb Jean-Louis Monteiro:
> For 2/ I can help you tomorrow if you want/need.
Would be very much appreciated to get a second pair of eyes.
Gruß
Richard
smime.p7s
Description: S/MIME cryptographic signature
uß
Richard
Am Dienstag, dem 24.05.2022 um 17:13 + schrieb Zowalla, Richard:
> To give a more detailed view / update from the spec tck party
> regarding
> activation and mail:
>
> (A) Geronimo Activation 2.0
>
> After a first milestone (M1) and some additional fixes
> >
> > Am 11.05.2022 um 19:00 schrieb Cesar Hernandez <
> > cesargu...@gmail.com
> > <mailto:cesargu...@gmail.com>>:
> >
> > +1, Thank you!
> >
> >
> > El mié, 11 may 2022 a las 9:06, Daniel Dias Dos Santos (<
> &g
+1
Am Montag, dem 23.05.2022 um 10:02 +0200 schrieb Jean-Louis Monteiro:
> Hi folks!
>
> I'd like to call a VOTE on Apache TomEE javaee-api-8.0.6.
>
> This mostly contains 2 fixes to remove non EE APIs such as
> javax.cache and
> more important javax.xml because it's messing up with JDK11
Hi Alex,
afaik, the difference is as follows:
The JAR "javaee-api-XY.jar" contains all required APIs for a given EE
release.
Tomcat - by design - also includes some EE APIs. To avoid duplicates
with the APIs brought in by Tomcat, there is "javaee-api-XY-
tomcat.jar", which excludes those
Hi,
isn't it:
javaee-api-8.0-6-tomcat.jar Mon May 23 07:51:38 UTC 2022966046
See:
https://repository.apache.org/content/repositories/orgapachetomee-1202/org/apache/tomee/javaee-api/8.0-6/
Or:
les, but the main build itself is green.
> I'll get the examples fixed and start the javaee-api release in
> parallel.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Mon, May 23, 2022 at 8:25 AM Zowalla, Richard <
> ri
one it and made sure the build was still green. Sent a new
> email to
> see if there are objections to release it and then TomEE 8.x
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Fri, May 20, 2022 at 7:35 AM Zowalla,
I am fine and have no objections.
If you need help or some supporting hands, just give a ping.
Gruß
Richard
Am Sonntag, dem 22.05.2022 um 20:36 +0200 schrieb Jean-Louis Monteiro:
> Hi all,
>
> I'm planning to start some releases.
>
> First the javaee-api 8.0.x which essentially fixes some
I see no issues.
We would need to add a clear list of APIs, which will be removed and
document them in an Jira. We can then reference it in any potential
release note, to indicate, that were was a change which might impact
consumers.
Gruß
Richard
Am Dienstag, dem 17.05.2022 um 13:21 -0700
Thanks for your view, David.
I created TOMEE-3968 to track this change/feature.
Notice to the community: It might be a beginner friendly task to work
on if someone has some available cycles - as I debugged it for
Deltaspike my memory is quite fresh and I can give some pointers were
to look at
Hi,
it's about the same Jira Issue, so it's fine to use this pull request.
Many thanks for your contribution!
Gruß
Richard
Von: Zoltán Tichov
Gesendet: Samstag, 14. Mai 2022 21:16:03
An: dev@tomee.apache.org
Betreff: Re: [GitHub] [tomee] rzo1 commented on a
term: Do not do any of that and avoid opening that can
> > > > of worms
> > > > at all cost. Get the file to parse with the minimum change
> > > > possible.
> > Get
> > > > some experience with the code and a successful contribution in
> > > > th
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/ji
Hi,
the ASF impls of the MP specifications are hosted by the Geronimo
project.
Yes - you are right. We would need to update every MP specification in
Geronimo and add / update the related implementation. That involves
finding the differences between each version, writing tests, etc.
In the end
Hi,
you can find the MP TCK Harness (which is run in the TomEE build) here:
https://github.com/apache/tomee/tree/master/tck/microprofile-tck/jwt
The actual MP JWT TCK tsts are in this artifact
org.eclipse.microprofile.jwt
microprofile-jwt-auth-tck
the related repository of the MP JWT TCK
We have enough binding votes (JL, Jon, Cesar) to proceed with it?
Gruß
Richard
Am Donnerstag, dem 05.05.2022 um 22:08 +0200 schrieb Jean-Louis
Monteiro:
> +1
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Thu, May 5, 2022 at 4:52 PM
gt; , on tomeetribe etc etc , but still no luck at ..but gaining lot of
> knowledge and experience
>
> Hope I can get some ideas/inputs to solve this , so i will have
> certainly
> have time to contribute here a lot
>
> Thank you
> -AD
>
> On Mon, May 9, 2022 at 12:0
ld like to know here how and where I can contribute , is it
> only in
> the Tomee world ? or is there something else as well .
>
> Would be great if you can brief out the areas typically where we can
> contribute
>
> Thank you so much
> -AD
>
>
>
>
>
>
Hi AD,
welcome to the mailing list and TomEE community.
Do you have areas of expertise or a special field or topic of interest,
you would like to contribute to?
We are currently working on TomEE 9. Therefore, we moved away from our
previous byte code transformation approach and switched TomEE
> 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, e.g
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
>
> 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. Tha
Thanks Rod!!
Am Montag, dem 02.05.2022 um 17:33 + schrieb Jenkins, Rodney J
(Rod):
> All,
>
> I have added the Semeru images for Java 11 and 17 for TomEE 8 and 9.
>
> Anything else anyone wants?
>
> Thanks,
> Rod.
>
>
>
> On 4/30/22, 12:35 PM, "
that or 8, 11,
and 17?
>
> I do not see an alpine image, so it would just be adding a ubuntu image.
>
> Rod.
>
>
> On 4/30/22, 1:30 AM, "Zowalla, Richard"
wrote:
>
> Nationwide Information Security Warning: This
Hi,
I think, that Alpine would be a great addition to shrink the images
sizes if it isn't too much work.
I am also wondering, if we should provide a Semeru/OpenJ9
runtime - but I guess, that there isn't too much need for it, so it is
super low prio :D
Gruß
Richard
Am Freitag, dem 29.04.2022
e, 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
+1
Am Donnerstag, dem 28.04.2022 um 11:19 +0200 schrieb Jean-Louis
Monteiro:
> 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
> >
wo errors in Tomee 9.0.0-M7. Should I make tickets for
> these
> errors and try to fix them?
> Although they may have been fixed in the next version (9.0.0-M8)
>
> Zoltán
>
> On Sun, Apr 24, 2022 at 11:06 AM Zowalla, Richard <
> richard.zowa...@hs-heilbronn.de> wrote:
>
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, 202
fies the
isntallation)
(6) Run the TCK and have fun.
Nevertheless, we need to fix the javamail (javax vs jakarta) thing
first, but afterwards any new volunteer can happily start TCK work.
Gruß
Richard
Am Dienstag, dem 26.04.2022 um 18:34 + schrieb Zowalla, Richard:
> Thanks & Yo
: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.
> >
>
ck isn't big enough to handle it in
> Java
> 11.
>
> I moved to a newer JDK like 14 or 17 and it worked.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Tue, Apr 26, 2022 at 7:42 PM Zowalla, Richard <
> richard.zo
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
6f7d7bae9d2e8da
Am Dienstag, dem 26.04.2022 um 09:59 +0000 schrieb Zowalla, Richard:
> Hi,
>
> I changed the script pointing to the released ee9.1 tck now and
> updated
> the README accordingly. If the instructions are followed carefully,
> it
> will lead to a fresh ins
gree with your prior statements about updating the README, branching
> for TomEE 8 and making TomEE 9 the master branch in the tomee-tck
> project.
>
>
> > On Apr 24, 2022, at 11:14 PM, Zowalla, Richard <
> > richard.zowa...@hs-heilbronn.de> wrote:
> &
Hi,
a few weeks ago, I noticed, that a lot of mails are generated by
@dependabot on the TomEE repositories.
It contains a lot of false positives (i.e. in the examples) and often
requires additional efforts (i.e. code changes, xml adjustments) to
upgrade.
We are updating the dependencies before
pdate" script and make it an "install"
script.
That would ease the necessary setup steps. Wdyt?
Gruß
Richard
Am Montag, dem 25.04.2022 um 05:54 +0000 schrieb Zowalla, Richard:
> > > The trick is that setup is difficult to maintain and can be quite
> > > intimidat
ess gap we
> do need to eventually fill.
>
>
> -David
>
>
> > On Apr 24, 2022, at 2:06 AM, Zowalla, Richard <
> > richard.zowa...@hs-heilbronn.de> wrote:
> >
> > Hi Zoltán,
> >
> > It's very great from you and it's truly awesom
Hi Zoltán,
It's very great from you and it's truly awesome when a long time user
of TomEE decides to contribute :)
First of all, do not get intimidated by your first ticket. If it ends
up being too hard or just not fun, let's find something else for you.
There is always plenty of work to do.
date 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 &
> >
> > 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 fo
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
>
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
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
ll have them "per-
> > > > version"
> > > > uncommited, already linking to specs by precise version
> > > >
> > > > so it wont be too hard for me to turn around, and give you
> > > > these
> > > vers
Alright - I will prepare the artifacts. Thanks!
Am Samstag, dem 16.04.2022 um 23:03 +0200 schrieb Jean-Louis Monteiro:
> Of course. Go ahead.
>
> Le sam. 16 avr. 2022 à 07:14, Zowalla, Richard <
> richard.zowa...@hs-heilbronn.de> a écrit :
>
> > Hi all,
> >
&g
Hi all,
I included a fix for TOMEE-3903, so we can configure, if created
*.tar.gz files are attached to the build or not.
Before that, we attached the *.tar.gz files multiple times, which leads
to unexpected behaviour in new Maven versions, e.g. deploying *.tar.gz
files as jars (see the first
e 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 updat
, dem 12.04.2022 um 09:33 + schrieb Zowalla, Richard:
> +1
>
> Question: We once talked about sharing knowledge about doing releases
> [1], so I am wondering, if we should use 8.0.11 as a pilot test for
> this approach?
>
> For reference changes currently targeted
+1
Question: We once talked about sharing knowledge about doing releases
[1], so I am wondering, if we should use 8.0.11 as a pilot test for
this approach?
For reference changes currently targeted for 8.0.11 (from Jira)
attached below.
Gruß
Richard
[1]
So we basically have to options (if I understand the discussion
correctly):
(A) Put some effort / resources into upgrade our MP impls to the latest
versions to fully support Jakarta namespace. From my understanding
maintaining these impls is a bit PITA as MP tends to break its API
every few
o talk about each
> > distribution at a high level. Sort of like the "TomEE Flavors"
> > section of our website main page (https://tomee.apache.org) but a
> > more complete page where there is kind of an image and description
> > of each distribution. People can then u
I went ahead and merged the changes by Swell. @Swell: Thank you!!
Cherry picked them to master (9.x) as well.
Now the distributions contain the libs specified on the website.
Gruß
Richard
Am Montag, dem 28.03.2022 um 08:18 + schrieb Zowalla, Richard:
> As we merged the comparision page,
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).
>
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.
>
> C
clearer.
> here is the current version of the web page in the PR :
> https://issues.apache.org/jira/secure/attachment/13041581/image-2022-03-25-11-19-03-406.png
>
> On Fri, 25 Mar 2022 at 06:18, Zowalla, Richard <
> richard.zowa...@hs-heilbronn.de> wrote:
>
> > Hi all,
> &
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:
>
Hi all,
Thanks for your mail and your work in making the page more clear,
Swell! Your work is very much appreciated.
> Total side note to the wider dev list, we really need to get JBatch
> into Plume! Those distributions are supposed to be the same minus
> the JPA and JSF providers.
I created
I like the idea of pairing people to act as release managers. That is a
great way to transfer knowledge and open the circle of people "who
know".
By doing so, it might be even possible to have some sort of (mostly) up
2 date release documentation, which could then be integrated in the
release
1 - 100 of 303 matches
Mail list logo
