Hello Again,
Completed some basic tests with TomEE+ 8.0.13 (more complex tests to
come), but also I ran https://github.com/anchore/grype latest version
on TomEE+ 8.0.12 versus this candidate 8.0.13, with focus on Jackson
CVEs, and here's the outcome:
With TomEE+ 8.0.12, the jackson-databind-2.13.
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, here's the script I'm running:
- c
Good catch. This is expected:
https://issues.apache.org/jira/browse/TOMEE-4021
or
https://lists.apache.org/thread/8tky9dr2sf99cs2hrj95j81w1rhrtdfn
Gruß
Richard
Am Dienstag, dem 11.10.2022 um 22:23 +0200 schrieb Alex The Rocker:
> okay I probably make a mistake somewhere.
> Also I see ehcache
okay I probably make a mistake somewhere.
Also 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 --batch --keyserver h
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
g
github-actions[bot] opened a new pull request, #943:
URL: https://github.com/apache/tomee/pull/943
Found some uncommited changes (from BOM regeneration) after running build on
TomEE main
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
Sorry previous mail sent too quickly.
What's wrong here ?
$ gpg --verify /tmp/tomee8013.asc apache-tomee-8.0.13-plus.tar.gz
gpg: Signature made Tue 11 Oct 2022 01:14:04 PM CEST using RSA key ID E5B8A431
gpg: Can't check signature: No public key
Le mar. 11 oct. 2022 à 22:03, Alex The Rocker a éc
Hum... what's wrong here:
Le mar. 11 oct. 2022 à 21:22, Alex The Rocker a écrit :
>
> +1 for more frequent releases (at least based on CVE with at least
> high severity)
> and yes, I have a relatively large test base ; stay tuned!
>
> Le mar. 11 oct. 2022 à 21:16, Richard Zowalla a écrit :
> >
>
+1 for more frequent releases (at least based on CVE with at least
high severity)
and yes, I have a relatively large test base ; stay tuned!
Le mar. 11 oct. 2022 à 21:16, Richard Zowalla a écrit :
>
> Hi Alex,
>
> we can maybe get into the habit of realising more often (yes, I know:
> we discusse
Hi Alex,
we can maybe get into the habit of realising more often (yes, I know:
we discussed this over and over on the list...).
I was just copying from the VOTE template docs, which mention to write
"first attempt" and so on... - so no regrets just copy & paste.
I don't expect any suprises but w
Hi Richard,
Thanks for this quick TomEE 8.0.3 release after not so long discussions!
I'll run some tests ASAP and then give my vote (non-binding).
Why do you mention "1st attempt"? Any regrets ?
Alex
Le mar. 11 oct. 2022 à 20:01, Richard Zowalla a écrit :
>
> Hi all,
>
> this is a first attempt
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
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 dow
> On Oct 11, 2022, at 5:53 AM, Zoltán Tichov wrote:
>
> How to activate the OpenTracingInterceptor from
> org.apache.tomee.microprofile.opentracing package?
Set this property to `true` and it should start TomEE with debug enabled and
listening to port 5005.
> I think I overestimated my knowled
Yes you are correct. This is a possible problem.
Digging down a bit
TomEE :: TCK :: MicroProfile Config TCK 1 mn 38 s
TomEE :: TCK :: MicroProfile Fault Tolerance TCK 1 h 11 mn
TomEE :: TCK :: MicroProfile Health TCK 5 mn 6 s
TomEE :: iTests :: Mi
> On Oct 11, 2022, at 2:33 AM, Jean-Louis Monteiro
> wrote:
>
> I can't measure without investing a lot of time, but looking at what Maven
> reports
> CDI + BVal TCK around 25 min
> MicroProfile TCK 2 hours and a half
There's definitely something going on with the build machines as the
MicroPr
Hi!
I have two questions now:
How to activate the OpenTracingInterceptor from
org.apache.tomee.microprofile.opentracing package?
I want to debug the opentracing TCK from NetBeans but it caused the
following error:
ERROR: transport error 202: connect failed: Connection refused
ERROR: JDWP Transpo
I pushed a fix for it. Let's see what happens
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Tue, Oct 11, 2022 at 12:06 PM Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:
> Richard asked for help on a BVal failure for TomEE 8 and I realised, we
> had
Hey Zlotan,
checking out to see if you need help or if there are questions we could
answer.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Wed, Sep 14, 2022 at 6:27 PM Zoltán Tichov
wrote:
> Hi!
>
> Unfortunately, I don't fully see the implementation pro
Richard asked for help on a BVal failure for TomEE 8 and I realised, we had
a failure on TomEE 9. So I was looking at the BVal failure on my side but
it does not fail alone on my side. It only fails when running part of the
entire TCK. So maybe a state.
Did not test yet the other failures.
I just
We have a couple of other challenges in my opinion.
Deps - all the shading is a pain but also takes a significant amount of time
Examples - they are somehow also some testing code for our server, but they
take time
TCK - more and more TCK are now standalone and we can run them easily. As a
result
21 matches
Mail list logo