> for my PR feedback and also the generated site output. You can
>> announce the release now.
>>
>> Robbie
>>
>> On Mon, 16 Dec 2019 at 19:55, Jean-Baptiste Onofré wrote:
>>>
>>> I tried to build with Jekyll but it failed on my machine.
>&g
the reporter tool unless they show
> important details. It seems like all they show is that it was a
> holiday filled quarter and so some things were lower volume than the
> prior one without thier effect.
>
> I tweaked the 5.15.11 release info to use its actual Nov 25th rele
that it was a
>> holiday filled quarter and so some things were lower volume than the
>> prior one without thier effect.
>>
>> I tweaked the 5.15.11 release info to use its actual Nov 25th release date.
>>
>> Robbie
>>
>> On Mon, 6 Jan 2020 at 07:14, J
0 will
>> be an important milestone with full JDK 9+ support and JMS 2.0 support
>> as well."
>>
>> The example skeleton on reporter.apache.org doesnt include the stats
>> from what I recall as they often asked folks not to include them, so
>> I'd drop t
Hi,
It's done.
Regards
JB
On 20/01/2020 14:16, Colm O hEigeartaigh wrote:
> Hi,
>
> Can someone with the relevant permissions please add me as a contributor to
> AMQ JIRA, so that I can assign issues to myself?
>
> Thanks,
>
> Colm.
>
--
Jean-Baptiste
ll ActiveMQ 5.9 in Windows server 2012?
> Refer:
> https://activemq.apache.org/getting-started.html#InstallationProcedureforWindows
>
>
> Windows: Windows XP SP2, Windows 2000, Windows Vista, Windows 7.
>
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.c
ave a go at fixing some of the issues.
> My registered email address - piyushchugh1...@gmail.com
>
>
> Thanks & Regards,
> Piyush Chugh
>
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
h JDK8
or JDK11 at runtime.
2. I do the changes required to build with JDK11, and then we will only
support JDK11 at runtime.
Thoughts ?
Anyway, I would like to submit 5.16.0 to vote asap, so please, let me
know what you think about JDK support (build or/and runtime).
Regards
JB
--
Jean-Baptis
e it easier on ourselves and remove LevelDB entirely as it
> has been deprecated now for several major versions and there isn't any
> reason to keep it at around at this point.
>
> On Tue, Jan 28, 2020 at 7:58 AM Jean-Baptiste Onofré
> wrote:
>
>> Hi guys
t in 5.16.0 instead of waiting til 5.17.0?
>
> Colm.
>
> On Wed, Jan 29, 2020 at 5:40 AM Jean-Baptiste Onofré
> wrote:
>
>> Hi Christopher,
>>
>> OK, so, I will move forward on 5.16.0 with JDK11 support at runtime.
>>
>> I will focus on JDK11 build
I still lean to the idea that it would
> be a better use of time to just work on improving the migration and feature
> parity of 5.x with Artemis instead of adding JMS 2.0 support as Artemis
> already supports it. If migration is easier and if all the main 5.x
> features people care about work in Artemis then people could just migrate
> to Artemis.
>
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Hi everyone,
Now that we fixed the ASF header issue, I'm submitting ActiveMQ 5.16.0
release to your vote (take #2).
This release is an important milestone as the runtime supports JDK 11.
The full build with JDK 11 is planned for 5.17.0.
It also includes bunch of fixes, improvements and much more
at AMQ it
seems like a last minute thing, and that possible let us forget some
cool stuff. Maybe we should get on the habit and do like Camel and
work on a release notes page during development
- Any other stuff ?
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Tal
et us forget some
cool stuff. Maybe we should get on the habit and do like Camel and
work on a release notes page during development
- Any other stuff ?
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
red solution. This page could be merged and
adapted to be included in the KahaDB one.
WDYT ?
Thanks
Regards
JB
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
t.com
http://blog.garytully.com
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
ease advise the project PMC that
your ICLA has been filed.
Warm Regards,
-- James Carman
Assistant Secretary, Apache Software Foundation
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
binary as Apache ActiveMQ 5.9.0
[ ] -1 Veto the release (provide specific comments)
Here's my +1
--
http://redhat.com
http://blog.garytully.com
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
bugs in the 5.9.0 release that have now been fixed and
perhaps we should cut a release now before any major changes make
their way into trunk?
What do ya guys think?
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
d Hat, Inc.
FuseSource is now part of Red Hat
dbosa...@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/
On Thu, Nov 14, 2013 at 4:33 PM, Jean-Baptiste Onofré wrote:
Hi Hiram,
I'm fully agree.
I have some fix about OSGi and Karaf inte
fixed and
perhaps we should cut a release now before any major changes make
their way into trunk?
What do ya guys think?
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Mojo
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
)
Here's my +1
Regards
--
Dejan Bosanac
--
Red Hat, Inc.
FuseSource is now part of Red Hat
dbosa...@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthr
pache-ActiveMQ-5-10-0-Release-Candidate-2-tp4681721p4681843.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
d use
the information from the release notes to say something about the
highlights.
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
earch-logstash-and-kibana/
Regards
JB
Thanks in advance !
Venu.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-Monitoring-alerts-tp4682028.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
jbono...@apache.org
Board Reports
-
Reports are due from you for the following committees:
- ActiveMQ
--
Regards,
Hiram
Blog: http://hiramchirino.com
Open Source SOA
http://fusesource.com/
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http
s.com
Author of Camel in Action: http://www.manning.com/ibsen
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
gards
--
Dejan Bosanac
--
Red Hat, Inc.
FuseSource is now part of Red Hat
dbosa...@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/
On Tue, Jan 15, 2013 at 1:10 PM, Jean-Baptiste Onofré wrote:
Hi
I would be please to he
It is
strongly recommended that if you have a resolution before the board,
you are encouraged to attend that board meeting.
ASF Board Reports
-
Reports are due from you for the following committees:
- ActiveMQ
--
Jean-Baptiste Onofré
jbono...@apache.org
Hi all,
I guess that most of you already saw this warning e-mail.
Camel, ActiveMQ, and CXF are affected (Karaf is not).
I will start to review ActiveMQ today and Camel tomorrow. Is someone
from CXF can take a quick look ?
I will get back to you soon for ActiveMQ and Camel.
Thanks !
Regards
2
wicket.apache.org 3
wink.apache.org 13
ws.apache.org 22
xalan.apache.org1
xerces.apache.org 5
xml.apache.org 1
xmlbeans.apache.org 3
zookeeper.apache.org18
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend -
airly creates burden on the existing
user base.
Thank you,
-Matt Pavlovich
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
es updates.
I hope to be able to submit the release to vote end of next week.
In the mean time, I will update the log4j2 update on the main branch, heading
to 5.17.0.RC1.
I think a first RC could be available by mid July.
I will keep you posted.
Regards
JB
--
Jean-Baptiste Onofré
Regards
JB
On 7/17/21 7:20 AM, Jean-Baptiste Onofré wrote:
Hi guys,
I'm sorry but I was busy more than expected post relocation ;)
Anyway, I will resume the releases preparation.
About 5.16.3, Matt and I opened several PRs with:
- several dependency updates
- fix/improvement about OSGi an
Hi guys,
as discussed on this thread, 5.16.3 will be submitted to vote tomorrow.
I finished this release preparation.
I would like to take a new look on AMQ-7470 today, but as it's not easy
to identify/reproduce, I might postpone the investigation for 5.16.4.
I also have feedback about secu
Hi everyone,
I submit Apache ActiveMQ 5.16.3 release to your vote.
This release includes important fixes and updates on the 5.16.x series,
especially:
- include java.util package in the deserialization enforcement
- logging improvements on STOMP transport
- improvement on Karaf features to avo
ks the assembly
build on some environment due to long file path.
I will fix by using posix instead of gnu.
Sorry about that, I will submit a new vote soon.
Regards
JB
On 06/08/2021 19:14, Jean-Baptiste Onofré wrote:
Hi everyone,
I submit Apache ActiveMQ 5.16.3 release to your vote.
This releas
+1 (binding)
Just a quick note: the vote section of the email mention 2.4.0, but we
are actually voting on 2.18.0.
Not a big deal ;)
Thanks !
Regards
JB
On 09/08/2021 20:50, Clebert Suconic wrote:
Just wanted to record my +1.
and update the voting template from previous vote (sorry for t
Hi everyone,
I submit Apache ActiveMQ 5.16.3 release to your vote (take #2). This new
vote fixes the assembly long path issue on some environment (AMQ-8352).
This release includes important fixes and updates on the 5.16.x series,
especially:
- include java.util package in the deserialization
Hi everyone,
I submit Apache ActiveMQ 5.16.3 release to your vote (take #2). This new
vote fixes the assembly long path issue on some environment (AMQ-8352).
This release includes important fixes and updates on the 5.16.x series,
especially:
- include java.util package in the deserialization
+1 (binding)
Regards
JB
On 10/08/2021 09:08, Jean-Baptiste Onofré wrote:
Hi everyone,
I submit Apache ActiveMQ 5.16.3 release to your vote (take #2). This new
vote fixes the assembly long path issue on some environment (AMQ-8352).
This release includes important fixes and updates on the
Hi guys,
I created pull request
https://github.com/apache/activemq-website/pull/56 on website to remove
the nabble link from the contact page.
Since nabble downgraded their servers capacity, a bunch of forums linked
to mailing list are not available anymore. It's the case for several
Apache
Justin already merged the PR, so I guess we are good ;)
Thanks !
Regards
JB
On 13/08/2021 16:48, Jean-Baptiste Onofré wrote:
Hi guys,
I created pull request
https://github.com/apache/activemq-website/pull/56 on website to remove
the nabble link from the contact page.
Since nabble
Hi everyone,
The ActiveMQ team is pleased to announce Apache ActiveMQ 5.16.3 feature.
https://activemq.apache.org/activemq-5016003-release
This release includes updates, improvements and important fixes, especially:
- fix on potential connection deadlock
- fix on broker plugin allowing java.ut
Hi Rich,
It's pretty open on my side, just have to know at least 24 hours before.
Regards
JB
On 27/08/2021 22:11, Rich Bowen wrote:
I'm certainly not opposed to having more than one person on the interview, but
it does make scheduling more challenging, because time zones are hard.
How about
Thanks Rich !
And thanks for Justin, Clebert and Matt as well ;)
Regards
JB
On 03/09/2021 17:42, Rich Bowen wrote:
Thank you so much for everyone that participated in the call. I'll edit and run
a draft by this list before publishing.
--Rich
On 2021/08/27 16:55:14, Rich Bowen wrote:
Hi, A
Hi Bruca,
I started the ActiveMQ part, I will add some more details today.
Regards
JB
On 29/09/2021 17:55, Bruce Snyder wrote:
I hope everyone is healthy and continuing to stay safe during this
umpteenth COVID wave.
Please take a just a few minutes to contribute to the latest board report
at
Hi,
What's your contribution or use of ActiveMQ ?
Commercial Support (https://activemq.apache.org/support) is listing
people providing ActiveMQ support/consulting.
Regards
JB
On 17/11/2021 05:57, praveen.ma...@techigai.io wrote:
Hi,
My name is Praveen and I work forTechigai. Techigai is a
Hi,
Did you try:
mvn clean install -DskipTests ?
It works fine for me and on Jenkins.
Regards
JB
On 03/01/2022 14:54, Laurent Blanquet wrote:
Hello,
I'm trying to build ActiveMQ latest release from the sources, and I cannot
switch off testing.
I use the following command (found at https:
gards
JB
On 03/01/2022 15:05, Laurent Blanquet wrote:
It does not work for me (Windows 10 + JDK 17).
I've just installed Maven, not Jenkins.
Regards,
Laurent
-Message d'origine-
De : Jean-Baptiste Onofré
Envoyé : lundi 3 janvier 2022 14:56
À : dev@activemq.apache.org
Objet
Log4j2 is only impacted, not log4j 1.x.
It's what I meant: ActiveMQ 5.16.x/5.15.x are not affected by log4shell
vulnerability.
Regards
JB
On 03/01/2022 17:30, Xeno Amess wrote:
Just show the log4j2 cve list to that customer, and persuade him no hurry to
migrate.
XenoAmess
_
Hi Jon
No problem at all ;)
I think I have a fix. I will create a PR, if you have time to take a
look, it would be great.
Thanks !
Regards
JB
On 04/01/2022 17:07, Jonathan Gallimore wrote:
Hi JB
This has come about from merging in my PR (thank you for that, by the way).
I can see the test
Yes, it should be done for ActiveMQ as well.
I will tackle that as well.
Regards
JB
On 05/01/2022 20:33, Tetreault, Lucas wrote:
Does ActiveMQ "Classic" need the same update?
On 2022-01-05, 11:16 AM, "Clebert Suconic" wrote:
CAUTION: This email originated from outside of the organizat
ew pass on Jira, we are good to go with this
release, I will submit it to vote soon
Regards
JB
On 04/01/2022 18:10, Jonathan Gallimore wrote:
Of course, I'd be more than happy to - thank you!
Jon
On Tue, Jan 4, 2022 at 4:57 PM Jean-Baptiste Onofré wrote:
Hi Jon
No problem at all ;)
I
Hi all,
ActiveMQ provides activemq-camel component.
This component is "old" (using Camel 2.25.x) and has been replaced by
camel-activemq and/or camel-jms.
I propose to remove ActiveMQ Camel from the ActiveMQ code.
Thoughts ?
Regards
JB
janv. 2022 à 12:32, Jonathan Gallimore <
jonathan.gallim...@gmail.com> a écrit :
Hi JB,
That PR looks good in my tests here - thanks for the fix!
Jon
On Wed, Jan 12, 2022 at 7:51 AM Jean-Baptiste Onofré
wrote:
Hi guys,
I fixed the SSLTransport issue (about the SSLParameters s
Hi,
Thanks for your contribution !
PR on main branch is enough: we do the review and test on this PR and
then we cherry pick on active branches.
Regards
JB
On 25/01/2022 09:57, Endre Stølsvik wrote:
It is ActiveMQ Classic.
I just went ahead, hoping that it is OK: PR to main branch:
https://
Hi,
As some features have been tested manually (you did a pass, I did a
quick pass on some as well), it's good enough for the release.
Agree with Chris that we should add test to "secure" the code
coverage/regression, but it should be done.
Either way is fine for me: if we consider it's blocker
b 3, 2022 at 3:44 AM Jean-Baptiste Onofré wrote:
Hi,
As some features have been tested manually (you did a pass, I did a
quick pass on some as well), it's good enough for the release.
Agree with Chris that we should add test to "secure" the code
coverage/regression, but it should be
ntime. only cancel the release if
you actually find an issue.
On Thu, Feb 3, 2022 at 8:15 AM Jean-Baptiste Onofré wrote:
Hi Chris,
OK, fair enough for me. I will cancel the vote and work with Matt to add
the tests.
Thanks,
Regards
JB
On 03/02/2022 13:57, Christopher Shannon wrote:
JB,
I would r
Hi all,
as discussed on this thread, I cancel this vote in order to:
- replace log4j 1.x by reload4j
- add tests on new features/improvements added for 5.16.4
I will submit a new vote asap.
Regards
JB
On 01/02/2022 21:41, Jean-Baptiste Onofre wrote:
Hi everyone,
I submit Apache ActiveMQ 5.1
FrameSizeCleanupTest/testMaxFrameSizeCleanupAutoNio/
This is the exact reason why I gave a -1 vote and considered no tests a
blocker because this Jira had no tests to verify the behavior change and
furthermore existing tests that actually found the issue were not noticed.
On Fri, Feb 4, 2022 at 9
issue were not noticed.
On Fri, Feb 4, 2022 at 9:52 AM Jean-Baptiste Onofré wrote:
Hi all,
as discussed on this thread, I cancel this vote in order to:
- replace log4j 1.x by reload4j
- add tests on new features/improvements added for 5.16.4
I will submit a new vote asap.
Regards
JB
On 0
issue were not noticed.
On Fri, Feb 4, 2022 at 9:52 AM Jean-Baptiste Onofré wrote:
Hi all,
as discussed on this thread, I cancel this vote in order to:
- replace log4j 1.x by reload4j
- add tests on new features/improvements added for 5.16.4
I will submit a new vote asap.
Regards
JB
On 01/0
Hi all,
I submit Apache ActiveMQ 5.16.4 release to your vote (take #2).
This release includes important fixes and updates on the 5.16.x
series, especially:
- log4j 1.x has been replaced by reload4j including the latest security fixes
- fix OSGi imports
- fix couple of warnings/issues on JDK16
- f
Hi guys,
unfortunately, we found an issue with reload4j switch:
https://issues.apache.org/jira/browse/AMQ-8484
I cancel this vote to prepare a new one with reload4j scope fixed in modules.
Regards
JB
On Thu, Feb 10, 2022 at 9:33 PM Jean-Baptiste Onofré wrote:
>
> Hi all,
>
> I s
d to 5.16.x.
> I'd pick them now but previously you force-pushed the branch rather
> than revert the release commits, are you going to do the same again?
>
> On Fri, 11 Feb 2022 at 12:36, Jean-Baptiste Onofré wrote:
> >
> > Hi guys,
> >
> > unfortunatel
Just: git reset --hard origin/activemq-5.16.x to be sure you have the
right history ;)
On Fri, Feb 11, 2022 at 1:52 PM Jean-Baptiste Onofré wrote:
>
> It's done: I forced pushed to got back to just before the release. So
> you can cherry pick now, or I can do it if you provide the
Hi all,
I submit Apache ActiveMQ 5.16.4 release to your vote (take #3).
This release includes important fixes and updates on the 5.16.x
series, especially:
- log4j 1.x has been replaced by reload4j including the latest security fixes
- fix OSGi imports
- fix couple of warnings/issues on JDK16
- f
My own +1 (binding)
Regards
JB
Le ven. 11 févr. 2022 à 19:47, Jean-Baptiste Onofré a
écrit :
> Hi all,
>
> I submit Apache ActiveMQ 5.16.4 release to your vote (take #3).
>
> This release includes important fixes and updates on the 5.16.x
> series, especially:
> - log4j
entral and dist. Then, I will
update the website, Jira, reporter and I will send the announcement.
Thanks all for your vote!
Regards
JB
On Fri, Feb 11, 2022 at 7:47 PM Jean-Baptiste Onofré wrote:
>
> Hi all,
>
> I submit Apache ActiveMQ 5.16.4 release to your vote (take #3).
>
The Apache ActiveMQ team is pleased to announce Apache ActiveMQ 5.16.4 release.
This release is an important release on the 5.16.x series containing:
- switch from log4j 1.x to reload4j fixing important security issues
in log4j 1.x
- upgrade to xerces 2.22.2 fixing security issue in xerces
- fix t
Hi Jean-Louis,
It's actually planned for ActiveMQ 5.17.0 (switching to jakarta-ee).
I'm working on some updates/fixes for 5.17.0, hopefully I should be
able to submit to vote next week.
Not yet the case for 5.16.x.
Regards
JB
On Wed, Feb 16, 2022 at 4:07 PM Jean-Louis Monteiro
wrote:
>
> Hi,
>
Hi guys,
I worked on the log4j2 update PR this weekend, fixing almost all unit
tests using a custom appender. I just have to fix the
activemq-web-demo test and squash, and the PR will be good to be
merged. I will do that today.
Then, later today and tomorrow I will work on using jetty modules
ins
New update: I just pushed the fix on activemq-web-console on
https://github.com/apache/activemq/pull/662
Regards
JB
On Mon, Feb 21, 2022 at 5:55 AM Jean-Baptiste Onofré wrote:
>
> Hi guys,
>
> I worked on the log4j2 update PR this weekend, fixing almost all unit
> tests using a
and tests things to a reasonable level thats less likely to
> see even trivial use cases fail to work.
>
> Robbie
>
> On Mon, 21 Feb 2022 at 04:55, Jean-Baptiste Onofré wrote:
> >
> > Hi guys,
> >
> > I worked on the log4j2 update PR this weekend, fixing almost
t; misleading (to me anyway) to add it now all on its own. It has waited
> this long, it seems better it could wait just a little longer until it
> is actually implemented in a following 5.18.x series, which neednt be
> far very away at all once it is actually ready.
>
> On Mon, 21
mo.specs
> geronimo-jms_1.1_spec
>
>
>
>
> Another approach is just having both API deps on the classpath, e.g
> brought in by the app deps explicitly, or just another component - if
> the stuff being done only needs a 1.1 impl functionality it as likely
> effectively reverted, it makes no sense to me on its own. Then all of
> > this stuff then worked on towards a 5.18.x release that actually
> > implements and tests things to a reasonable level thats less likely to
> > see even trivial use cases fail to work.
> >
> >
gt; > > > 5.17.x to be branched and proceed without this. Theres a load of stuff
> > > > in it already that is long overdue like the JDK11 build etc. I would
> > > > go so far as to say the prior API jar change from early November
> > > > (https://github.c
17.0 is almost ready from this standpoint.
As I would like to start the vote asap, It would be great to act about
JMS2. Do you want me to start with different options ?
Regards
JB
On Mon, Feb 21, 2022 at 5:55 AM Jean-Baptiste Onofré wrote:
>
> Hi guys,
>
> I worked on the log4j2 updat
e to keep arguing
> anymore over a version...5.18.0 can literally go out whenever we want.
>
> On Tue, Feb 22, 2022 at 8:50 AM Jean-Baptiste Onofré
> wrote:
>>
>> Hi guys,
>>
>> Quick update about 5.17.0 release:
>>
>> - I fixed/squash log4j2 update PR
n anything jakarta related — we add another
> > >> active
> > >>>>> branch to maintain. As log4j showed us, having a bunch of active
> > >> branches
> > >>>>> out there is a lot of work when it is time to crank out se
ail.com> wrote:
> >
> > > +1, i've never liked including jetty-all and might as well keep it up to
> > > date with a major release.
> > >
> > > I think we are good to go , I did a review of a 5.17.0 snapshot build last
> > > week and things looke
t; >> >>>
> >> >>> On Mon, Feb 28, 2022 at 9:01 AM Christopher Shannon <
> >> >>> christopher.l.shan...@gmail.com> wrote:
> >> >>>
> >> >>>> +1, i've never liked including jetty-all and might
+1
I merged the Jetty PR in the meantime.
Regards
JB
On Tue, Mar 1, 2022 at 3:29 PM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> I'll open a PR for revert it
>
> On Tue, Mar 1, 2022 at 8:33 AM Jean-Baptiste Onofré
> wrote:
>
> > Hi
> >
o set CI run: https://github.com/apache/activemq/pull/786
> There were a couple of minor conflicts but nothing major to fix.
>
> I bumped the version on the main branch to 5.18.0-SNAPSHOT
>
> If CI is good I think we should be ok to proceed with the release.
>
> On Tue, Mar 1, 202
/pull/786
> There were a couple of minor conflicts but nothing major to fix.
>
> I bumped the version on the main branch to 5.18.0-SNAPSHOT
>
> If CI is good I think we should be ok to proceed with the release.
>
> On Tue, Mar 1, 2022 at 9:38 AM Jean-Baptiste Onofré
> wrote:
Hi guys,
*Finally*, after several weeks waiting, I'm pleased to submit Apache
ActiveMQ 5.17.0 release to your vote.
This release is an important milestone in ActiveMQ roadmap, including 200
issues, especially:
- support Spring 5.x
- support log4j 2.x (2.17.1)
- JDK 11+ support for both build and
gt; > +1 (non-binding)Tested with some internal projects.Thanks
> > JB!regardsFrançois
> > Message d'origine De : Jean-Baptiste Onofré <
> > j...@nanthrax.net> Date : 07/03/2022 18:25 (GMT+01:00) À :
> > dev@activemq.apache.org Objet : [VO
ue). We can also go ahead and merge in
> AMQ-8530
> > > (and some other test fixes)
> > >
> > > On Tue, Mar 8, 2022 at 3:18 PM francois.papon <
> > francois.pa...@openobject.fr>
> > > wrote:
> > >
> > > > +1 (non-binding)Tested w
Hi guys,
due to AMQ-8533, I cancel this vote to prepare a new take.
The new take will include geronimo jar update and fix for AMQ-8533.
I will submit the release to vote tomorrow morning (my time).
Regards
JB
On Mon, Mar 7, 2022 at 6:24 PM Jean-Baptiste Onofré wrote:
> Hi guys,
>
>
Hi guys,
I submit ActiveMQ 5.17.0 release (take #2) to your vote. Compared to the
first attempt, we fixed geronimo jar version and shading of
activemq-client, activemq-pool, activemq-jms-pool artifacts.
This release is an important milestone in ActiveMQ roadmap, including 200
issues, especially:
+1 (binding)
Regards
JB
On Thu, Mar 10, 2022 at 6:10 AM Jean-Baptiste Onofré
wrote:
> Hi guys,
>
> I submit ActiveMQ 5.17.0 release (take #2) to your vote. Compared to the
> first attempt, we fixed geronimo jar version and shading of
> activemq-client, activemq-pool, ac
hese tasks will probably need a day or so.
Thanks all for your vote !
Regards
JB
On Thu, Mar 10, 2022 at 6:10 AM Jean-Baptiste Onofré
wrote:
> Hi guys,
>
> I submit ActiveMQ 5.17.0 release (take #2) to your vote. Compared to the
> first attempt, we fixed geronimo jar version and s
The ActiveMQ team is pleased to announce ActiveMQ 5.17.0 has been released.
ActiveMQ 5.17.0 is a major milestone in ActiveMQ roadmap, bringing lot of
changes, fixes and improvements, especially:
- JDK 11+ required for build and run now
- Spring 5.3.16
- Log4j 2.17.1
- Jetty 9.4.45 using atomic jar
** ERROR: directory is already being watched! **
>
> Directory: /../activemq-website/src/maven/5.17.0/apidocs
>
> is already being watched through:
> /.../activemq-website/src/maven/5.17.0/apidocs
>
> MORE INFO: https://github.com/guard/listen/blob/maste
> >
> > Directory: /../activemq-website/src/maven/5.17.0/apidocs
> >
> > is already being watched through:
> > /.../activemq-website/src/maven/5.17.0/apidocs
> >
> > MORE INFO: https://github.com/guard/listen/blob/master/README.md
&g
ppen to read a stale announcement /
> page / etc its good that they end up getting something newer instead.
>
> On Tue, 15 Mar 2022 at 13:03, Jean-Baptiste Onofré wrote:
> >
> > Hi again ;)
> >
> > As the announcement is specifically for 5.17.0, I think it's
101 - 200 of 588 matches
Mail list logo
