> artifacts must be placed. Once I understand the process, I can see
> > about making it repeatable.
> >
> > Personally, I would like to see it done in a way that someone with
> > lesser skills (like, but not necessarily, me) does releases. The
> > way I see it now
e
> a dummy TomEE release candidate. Create some dummy destinations that mimic
> where the artifacts must be placed. Once I understand the process, I can see
> about making it repeatable.
>
> Personally, I would like to see it done in a way that someone with lesser
> skills (
gt;
> > > In total, it leads to (non) reproducable builds (as you
> > > described).
> > >
> > > I am strongly +1 for replacing the range syntax by plain versions
> > > in
> > > the examples.
> > >
> > > Gruß
> > >
t;> Am Sonntag, dem 20.02.2022 um 22:51 -0500 schrieb David Blevins:
>>> I've been digging through the build trying to eliminate dependencies
>>> older releases.
>>>
>>> We've been inconsistently updating the versions in the examples, so
>>>
rsions in
> the examples.
>
> Gruß
> Richard
>
> Am Sonntag, dem 20.02.2022 um 22:51 -0500 schrieb David Blevins:
> > I've been digging through the build trying to eliminate dependencies
> > older releases.
> >
> > We've been inconsistently updating
Richard
Am Sonntag, dem 20.02.2022 um 22:51 -0500 schrieb David Blevins:
> I've been digging through the build trying to eliminate dependencies
> older releases.
>
> We've been inconsistently updating the versions in the examples, so
> I've gone and fixed a few of thos
I've been digging through the build trying to eliminate dependencies older
releases.
We've been inconsistently updating the versions in the examples, so I've gone
and fixed a few of those. We had some tools like the TomEE Patch Plugin
indirectly pulling 8.0.0-M3 artifacts --
+1 : )
Em sex., 22 de jan. de 2021 às 12:33, exabrial12
escreveu:
> So we haven't had any issues running the 8.0.6-SNAPSHOT in production!
>
> Looking forward to the release. Cheers,
> -Jonathan
>
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>
So we haven't had any issues running the 8.0.6-SNAPSHOT in production!
Looking forward to the release. Cheers,
-Jonathan
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
We've got this deployed and will let it run for a few hours. Hopefully that
bug is crushed!
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
We're going into a 3 day weekend, and I have a "don't deploy on a Friday
rule" for the dept 😂 but I think we could flip one of the nodes to the
master snapshot in the cluster over starting Tuesday morning. It generally
takes about 1-3 days for the server to OOME after that. I wouldn't delay the
rel
Do you know if it's fixed by the current master?
Just want to make sure it's fixed lol
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Thu, Jan 14, 2021 at 10:58 PM exabrial12 wrote:
> We've been have some applications in prod OOME. I took a heap dump of one
We've been have some applications in prod OOME. I took a heap dump of one and
saw a bunch of Johnzon CDI instances, so this is a welcome release.
Thanks everyone!
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
I have posted a vote for 8.0.6. I'll follow up with 7.x versions. This does
include Tomcat 9.0.41. Please do note that ActiveMQ just started a new
release vote for 5.16.1 just before I posted this, which is *not* included.
We can certainly followup with an 8.0.7 if needed or include it if a reroll
Hi Alexandre
The Tomcat version for 8.0.6 will be 9.0.41, and I am cutting the release
now. This will include the fix for CVE-2021-24122, announced on Tomcat's
mailing list today.
Kind Regards
Jon
On Thu, Jan 14, 2021 at 2:26 PM Alex The Rocker
wrote:
> yes, for example CVE-2021-24122, for
yes, for example CVE-2021-24122, for which fix exists in Tomcat 9.0.40
/ 8.5.60 / etc.
I hope this will be at least Tomcat's version embedded in upcoming TomEE 8.0.6
Kind regards,
Alexandre
Le mer. 13 janv. 2021 à 12:53, Jonathan Gallimore
a écrit :
>
> Yes. Is there a specific concern you have?
Yes. Is there a specific concern you have?
On Wed, Jan 13, 2021 at 10:40 AM Alex The Rocker
wrote:
> Hello Jon,
>
> Would you please make sure that this 8.0.6 TomEE release will include
> latest CVEs fixes (from TomEE, ActiveMQ, etc) ?
>
> Kind regards;
> Alexandre
>
> Le ven. 8 janv. 2021 à 14:
Hello Jon,
Would you please make sure that this 8.0.6 TomEE release will include
latest CVEs fixes (from TomEE, ActiveMQ, etc) ?
Kind regards;
Alexandre
Le ven. 8 janv. 2021 à 14:15, Jonathan Gallimore
a écrit :
>
> Hi All,
>
> Any objections if I kick off a 8.0.6 release? I think there are som
cation
>>>>
>>>> I stopped the build here after it ran for 8 hours. I'm taking a look at
>>>> this today.
>>>>
>>>> Jon
>>>>
>>>> On Fri, Jan 8, 2021 at 10:25 PM Cesar Hernandez
>>>> wrote:
>>>>
>>>>>
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
>>>>
>>>
escribió:
>>>
>>> > Hi,
>>> >
>>> > great idea - no objections from my side
>>> >
>>> > Gruss
>>> > Richard
>>> >
>>> >
>>> > Von: Jonathan Gallimo
a, Richard (<
>> richard.zowa...@hs-heilbronn.de>) escribió:
>>
>> > Hi,
>> >
>> > great idea - no objections from my side
>> >
>> > Gruss
>> > Richard
>> >
>> >
>> >
eat 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
chard (<
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
>
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
Hi Jon,
Yes great proposal, i'm 100% for a 8.0.6, and I will provide
feedbacks based on our apps when RC (Release Candidate) will be
available (please don't forget Arquillian embedded TomEE 8.0.6 in RC).
Kind regards,
Alexandre
Le ven. 8 janv. 2021 à 14:15, Jonathan Gallimore
a écrit :
>
>
Thanks! Getting this underway now.
On Fri, Jan 8, 2021 at 2:25 PM Wiesner, Martin <
martin.wies...@hs-heilbronn.de> wrote:
> Thx Jon for getting things rolling. Much appreciated!
>
> Best
> Martin
> -
> https://twitter.com/mawiesne
>
> > Am 08.01.2021 um 14:35 schrieb Jean-Louis Monteiro <
> jlmo
Thx Jon for getting things rolling. Much appreciated!
Best
Martin
-
https://twitter.com/mawiesne
> Am 08.01.2021 um 14:35 schrieb Jean-Louis Monteiro :
>
> Go for it
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Fri, Jan 8, 2021 at 2:15 PM J
Go for it
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Fri, Jan 8, 2021 at 2:15 PM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:
> Hi All,
>
> Any objections if I kick off a 8.0.6 release? I think there are some
> dependency updates that it wou
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
wel
d.
>
>
> From: Jonathan Gallimore
> Sent: Wednesday, December 4, 2019 5:01:38 PM
> To: dev@tomee.apache.org
> Subject: [EXTERNAL] Releases
>
> Nationwide Information Security Warning: This is an external
jeu. 5 déc. 2019 à 00:02, Jonathan Gallimore
> > a écrit :
> > >
> > > Just a heads up that I'm going to roll releases for 7.0.7, 7.1.2 and
> > 8.0.1.
> > > Shout if you need me to stop.
> > >
> > > Thanks
> > >
> > > Jon
> >
ward with the images.
>
> Thanks,
> Rod.
>
>
> From: Jonathan Gallimore
> Sent: Wednesday, December 4, 2019 5:01:38 PM
> To: dev@tomee.apache.org
> Subject: [EXTERNAL] Releases
>
> Nationwide Information Security Warning: This is an external email.
able to push this change for tomee-7.1.x -
> see my comment in this JIRA : maybe would it be nice to have same
> update on 7.0.x for upcoming 7.0.7 release ?
>
> Kind regards,
> Alexandre
>
> Le jeu. 5 déc. 2019 à 00:02, Jonathan Gallimore
> a écrit :
> >
> > Jus
,
Alexandre
Le jeu. 5 déc. 2019 à 00:02, Jonathan Gallimore
a écrit :
>
> Just a heads up that I'm going to roll releases for 7.0.7, 7.1.2 and 8.0.1.
> Shout if you need me to stop.
>
> Thanks
>
> Jon
@tomee.apache.org
Subject: [EXTERNAL] Releases
Nationwide Information Security Warning: This is an external email. Do not
click on links or open attachments unless you trust the sender.
--
Just a heads up that I'm going to
Just a heads up that I'm going to roll releases for 7.0.7, 7.1.2 and 8.0.1.
Shout if you need me to stop.
Thanks
Jon
No objections, but I will time this release with the docker releases, providing
you all are happy with that. That way, we don’t updated then in less than a
week, we put out a new version and have to update docker again.
Thanks,
Rod.
On 11/7/19, 4:47 AM, "Jonathan Gallimore&qu
Reviving this thread. I have one further update that I'd like to get in,
which is to update commons-daemon to the latest version which resolves an
issue running the Windows service with a 32bit JVM on a 64bit server. If
there's no objections, I'll roll releases for 7.0.7, 7.1.2 a
> > >>> yet :)
> > > >>>
> > > >>> Best,
> > > >>> Richard
> > > >>>
> > > >>> Am Dienstag, den 24.09.2019, 10:57 -0500 schrieb Jonathan S.
> Fisher:
> > > >>>
> > &g
gt; > >>> So I've got a test case, but it will likely just be isolated to us.
> We
> > were
> > >>>
> > >>> upgrading the ActiveMQ RAR to 5.15.9 to enable strict host checking
> on
> > TLS
> > >>>
> > >>>
> >>>
> >>> certificates. If we keep the stock ActiveMQ rar/jar we don't see the
> >>>
> >>> problem.
> >>>
> >>>
> >>> So I guess take note of that if someone ever asks for an upgrade, the
> >>>
ilover protocol will collapse a 32m JVM after about 10k messages.
>>>
>>>
>>> On Mon, Sep 23, 2019 at 5:20 PM Jean-Louis Monteiro <
>>>
>>> jlmonte...@tomitribe.com> wrote:
>>>
>>>
>>> I have opened this ticket and pushed a
M Jean-Louis Monteiro <
>>
>> jlmonte...@tomitribe.com> wrote:
>>
>>
>> I have opened this ticket and pushed a fix on both Java EE 7 and 8 API jar.
>>
>> New snapshot deployed.
>>
>>
>> I'm waiting for the full build on master to pa
failover protocol will collapse a 32m JVM after about 10k messages.
>
>
> On Mon, Sep 23, 2019 at 5:20 PM Jean-Louis Monteiro <
>
> jlmonte...@tomitribe.com> wrote:
>
>
> I have opened this ticket and pushed a fix on both Java EE 7 and 8 API jar.
>
> New snapsh
oth Java EE 7 and 8
> API jar.New snapshot deployed.
> I'm waiting for the full build on master to pass and then I'll close
> theticket and fire up the 2 releases so you can move on with TomEE
> --Jean-Louis Monteiro
> http://twitter.com/jlouismonteirohttp://www.tomitribe.com
es. I'm thinking its
> probably time we put out new releases as these branches have seen some
> fixes.
>
> Is there anything that we think is missing before I kick off some releases
> and votes?
>
> I'd like to get the quartz-openejb-shade update if possible - that needs
> some more reviewers and votes.
>
> Jon
7;m waiting for the full build on master to pass and then I'll close the
> ticket and fire up the 2 releases so you can move on with TomEE
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Mon, Sep 23, 2019 at 3
I have opened this ticket and pushed a fix on both Java EE 7 and 8 API jar.
New snapshot deployed.
I'm waiting for the full build on master to pass and then I'll close the
ticket and fire up the 2 releases so you can move on with TomEE
--
Jean-Louis Monteiro
http://twitter.com/jlou
ssue raised earlier today. Would be great to get the fix
> > in
> > > > before rolling.
> > > > --
> > > > Jean-Louis Monteiro
> > > > http://twitter.com/jlouismonteiro
> > > > http://www.tomitribe.com
> > &
omitribe.com
> > >
> > >
> > > On Mon, Sep 23, 2019 at 12:33 PM Jonathan Gallimore <
> > > jonathan.gallim...@gmail.com> wrote:
> > >
> > > > I'm just doing some cleanup on these branches. I'm thinking its
> > > > probably
ribe.com
> >
> >
> > On Mon, Sep 23, 2019 at 12:33 PM Jonathan Gallimore <
> > jonathan.gallim...@gmail.com> wrote:
> >
> > > I'm just doing some cleanup on these branches. I'm thinking its
> > > probably time we put out new releases as these br
ro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Mon, Sep 23, 2019 at 12:33 PM Jonathan Gallimore <
> jonathan.gallim...@gmail.com> wrote:
>
> > I'm just doing some cleanup on these branches. I'm thinking its
> > probably time we put
ome cleanup on these branches. I'm thinking its
> probably time we put out new releases as these branches have seen some
> fixes.
>
> Is there anything that we think is missing before I kick off some releases
> and votes?
>
> I'd like to get the quartz-openejb-shad
I'm just doing some cleanup on these branches. I'm thinking its
probably time we put out new releases as these branches have seen some
fixes.
Is there anything that we think is missing before I kick off some releases
and votes?
I'd like to get the quartz-openejb-shade update if
ause this issue was really a blocking one for us.
> Any release date for TomEE 7.1.2 ?
>
> Best Regards.
>
> -Original Message-
> From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
> Sent: vendredi 28 juin 2019 16:19
> To: us...@tomee.apache.org
> S
: Re: TomEE 7.0.6 and 7.1.1 releases
At the time of the rollback, the artifacts hadn't been released, and therefore
the change ended up breaking the build. I see no reason why we can't update
this to 3.1.18 now, and I'll commit that change.
Jon
On Thu, Jun 27, 2019 at 4:31 PM COU
: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
> > Sent: vendredi 21 juin 2019 15:12
> > To: us...@tomee.apache.org; dev@tomee.apache.org
> > Subject: TomEE 7.0.6 and 7.1.1 releases
> >
> > Hi All,
> >
> > I'm pleased to announce that new releases of
om: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
> Sent: vendredi 21 juin 2019 15:12
> To: us...@tomee.apache.org; dev@tomee.apache.org
> Subject: TomEE 7.0.6 and 7.1.1 releases
>
> Hi All,
>
> I'm pleased to announce that new releases of TomEE - versions 7.0.6 a
r.
No 3.1.18 at all.
Mistake ?
Best Regards.
-Original Message-
From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
Sent: vendredi 21 juin 2019 15:12
To: us...@tomee.apache.org; dev@tomee.apache.org
Subject: TomEE 7.0.6 and 7.1.1 releases
Hi All,
I'm pleased to announc
Hi All,
I'm pleased to announce that new releases of TomEE - versions 7.0.6 and
7.1.1 - are now available. These are maintenance releases of the 7.0.x and
7.1.x branches respectively.
The JIRAs for each release are here:
7.0.6:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?proj
+1, just ping me if you need some help.
LieGrue,
strub
> Am 13.12.2018 um 17:57 schrieb Jonathan Gallimore
> :
>
> There's some stuff I need to finish backporting, but I'm generally in
> favour. We have a Johnzon vote in progress, and could do with an OWB
> release for the 7.0.x and 7.1.x branc
There's some stuff I need to finish backporting, but I'm generally in
favour. We have a Johnzon vote in progress, and could do with an OWB
release for the 7.0.x and 7.1.x branches.
Jon
On Thu, Dec 13, 2018 at 12:16 PM Wiesner, Martin <
martin.wies...@hs-heilbronn.de> wrote:
> Hey guys,
>
> Richa
Hello,
Huge +1, especially if that includes official Java 11 support.
Think about this : Java 12 will be RTM in January, would be a shame if
no TomEE+ release wouldn't even support Java 11 before...
(and yes, we need it for TomEE+ 7.0.6, we're targeting 7.1.x next
year, that's life..)
Kind regard
+1
On Thu, Dec 13, 2018, 10:37 Roberto Cortez Hi Martin,
>
> Yes, my idea was to push for another Milestone release once we stabilise
> the build.
>
> Cheers,
> Roberto
>
> > On 13 Dec 2018, at 12:16, Wiesner, Martin <
> martin.wies...@hs-heilbronn.de> wrote:
> >
> > Hey guys,
> >
> > Richard (Z,
Hi Martin,
Yes, my idea was to push for another Milestone release once we stabilise the
build.
Cheers,
Roberto
> On 13 Dec 2018, at 12:16, Wiesner, Martin
> wrote:
>
> Hey guys,
>
> Richard (Z, @rzo1) and me are having some coffee in the office and are
> discussing several ideas. One them
Hey guys,
Richard (Z, @rzo1) and me are having some coffee in the office and are
discussing several ideas. One them is that we’d like to propose that TomEE
project kicks out a pre-xmas release for 7.1.1 and/or 7.0.6, and even more
interesting: a 8.0.0-M2 milestone preview.
The rationale behin
It's on my list to review that one.
txs and LieGrue,
strub
> Am 17.06.2017 um 22:11 schrieb Svetlin Zarev
> :
>
> Hi Mark,
>
> Have you considered fixing
> https://issues.apache.org/jira/browse/GERONIMO-6569 ? It's about common
> annotations spec compliance.
>
> Kind regards,
> SVetlin
>
>
Hi Mark,
Have you considered fixing
https://issues.apache.org/jira/browse/GERONIMO-6569 ? It's about common
annotations spec compliance.
Kind regards,
SVetlin
2017-06-17 19:37 GMT+03:00 Mark Struberg :
> Hi folks!
>
> I'm about to release the common-annotation-1.3 and jcdi-2.0 APIs over in
> Ge
None done afaik
Le 17 juin 2017 18:37, "Mark Struberg" a écrit :
> Hi folks!
>
> I'm about to release the common-annotation-1.3 and jcdi-2.0 APIs over in
> Geronimo.
> Does TomEE also need some API to be released?
> Would like to do things only once if possible ;)
>
> txs and LieGrue,
> strub
Hi folks!
I'm about to release the common-annotation-1.3 and jcdi-2.0 APIs over in
Geronimo.
Does TomEE also need some API to be released?
Would like to do things only once if possible ;)
txs and LieGrue,
strub
Hi
2017-02-15 14:34 GMT+01:00 Mark Struberg :
> Hi folks!
>
> Just noticed that we did not release a javaee-api.jar with 7.0.2.
> That feels kind of wrong to me (personal opinion so far).
>
> Until now I just had a
>
>
> nnn
>
> in my pom and used this version for all the tomee artifacts.
> Th
Hi folks!
Just noticed that we did not release a javaee-api.jar with 7.0.2.
That feels kind of wrong to me (personal opinion so far).
Until now I just had a
nnn
in my pom and used this version for all the tomee artifacts.
That doesn't work anymore for 7.0.2.
Is there a reason we stopped b
://www.apache.org/dist/tomee
Maven artifacts are also available in the central Maven repository.
The releases are primarily security releases to address CVE-2016-0779, EJBd
protocol allows to exploit 0-day vulnerability in all previous releases.
The Apache TomEE Team
--
Andy Gumbrecht
https
The Apache Team Team is pleased to announce the availability of:
Apache TomEE 7.0.0-M3 and 1.7.4
When downloading, please verify signatures using the KEYS file available at:
http://www.apache.org/dist/tomee
Maven artifacts are also available in the central Maven repository.
The releases are
related to the
issue.
Andy.
--
View this message in context:
http://openejb.979440.n4.nabble.com/Security-releases-tp4667898p4667944.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
I mentioned in the security reporting thread, although we do always
>> use the most recent versions of everything in our releases, we should
>> probably address our timing.
>>
>> Over the lifetime of TomEE we average 4.14 months between releases. Also
>> in the lifetime of
http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
>
> 2014-02-19 20:27 GMT+01:00 Bjorn Danielsson <
> bjorn-apa...@lists.cuspycode.com>:
> > +1 for having quick and minimal effort security-only releases.
> >
> > At least for updatin
://github.com/rmannibucau
2014-02-19 20:27 GMT+01:00 Bjorn Danielsson :
> +1 for having quick and minimal effort security-only releases.
>
> At least for updating the latest release in cases where the
> patch has limited impact on everything else ("minimal effort").
>
> --
> B
+1 for having quick and minimal effort security-only releases.
At least for updating the latest release in cases where the
patch has limited impact on everything else ("minimal effort").
--
Bjorn Danielsson
Cuspy Code AB
David Blevins wrote:
> So as I mentioned in the secur
do always
> use the most recent versions of everything in our releases, we should
> probably address our timing.
>
> Over the lifetime of TomEE we average 4.14 months between releases. Also
> in the lifetime of TomEE, there've been about 18 CVEs that affect us.
> That'
So as I mentioned in the security reporting thread, although we do always use
the most recent versions of everything in our releases, we should probably
address our timing.
Over the lifetime of TomEE we average 4.14 months between releases. Also in
the lifetime of TomEE, there've been
82 matches
Mail list logo