You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2022/03/14 13:25:56 UTC
[RESULT][VOTE] Apache ActiveMQ 5.17.0 release (take #2)
Hi everyone,
this vote passed with the following result:
+1 (binding): Chris Shannon, Tim Bish, JB Onofré, Clebert Suconic
+1 (non binding): Robbie Gemmell, WBD, Matt Pavlovich
I'm promoting the artifacts on Maven Central and dist.apache.org.
Then, I will prepare two PRs updates for the website:
1. announcement (download links, javadoc update, etc)
2. quick "update guide" listing major changes between ActiveMQ 5.16.x and
5.17.x (JDK, Spring, ...) and introducing target roadmap for ActiveMQ 5.18.x
Once the website is up to date, I will send the announcement email.
These 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é <jb...@nanthrax.net>
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, activemq-jms-pool artifacts.
>
> 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 runtime
> - remove of activemq-camel component (replaced by camel-activemq and
> camel-jms components)
> - remove leveldb
> - tons of fixes and dependency updates
>
> Please take a look on the Release Notes for details:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12346476
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1248/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.17.0/
>
> Git tag: activemq-5.17.0
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB
>
Re: [RESULT][VOTE] Apache ActiveMQ 5.17.0 release (take #2)
Posted by Robbie Gemmell <ro...@gmail.com>.
Leaving latest at 'apidocs' and having e.g '5.16.x' seems simple. I
see no point putting 5.15.x up at this point personally.
On Tue, 15 Mar 2022 at 13:01, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> Hi Robbie,
>
> Thanks for the fix. And yes, I saw the issue about apidocs symlink as
> well, just wanted to avoid duplicating folders. But you are right, let
> me fix that.
>
> Regarding the other apidocs version, I forgot git add to add it on the
> website. Basically, I wanted to push the latest 5.15.15 and 5.16.4
> apidocs versions.
>
> Gonna fix that as well.
>
> Thanks !
> Regards
> JB
>
> On Tue, Mar 15, 2022 at 12:39 PM Robbie Gemmell
> <ro...@gmail.com> wrote:
> >
> > I have fixed the updated website so that 5.17.0 is actually considered
> > a 'current' release, meaning it actually gets listed properly on the
> > main download page, and has the correct download links etc added. It
> > is generally good to look at the site update before publishing it
> > (using scripted 'jekyll serve'), and certainly before announcing.
> >
> > To the 'checking before publish' point, the change to delete the
> > src/maven/apidocs/ folder and replace it with a symlink to
> > src/maven/5.17.0 is causes an error from the Jekyll test server (as
> > below) since it ends up watching the target folder twice, directly and
> > then again via the symlink.
> >
> > I didnt change this back, but personally I think it makes sense to
> > skip the symlink and just use the apidocs folder. It would avoid such
> > an error, and also means the diff for adding each release would only
> > need to show difference in the javadoc files rather than containing
> > literally the entire content of the javadoc, as the commit adding
> > 5.17.0 does (in addition to complete content of removing the prior
> > apidocs content, and for some reason 5.15.8, even though a 5.15.9
> > folder remains).
> >
> >
> > Server address: http://127.0.0.1:4000
> > Server running... press ctrl-c to stop.
> > ** 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/master/README.md
> > LiveReload: Browser connected
> >
> >
> >
> > On Mon, 14 Mar 2022 at 13:26, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> > >
> > > Hi everyone,
> > >
> > > this vote passed with the following result:
> > >
> > > +1 (binding): Chris Shannon, Tim Bish, JB Onofré, Clebert Suconic
> > > +1 (non binding): Robbie Gemmell, WBD, Matt Pavlovich
> > >
> > > I'm promoting the artifacts on Maven Central and dist.apache.org.
> > >
> > > Then, I will prepare two PRs updates for the website:
> > > 1. announcement (download links, javadoc update, etc)
> > > 2. quick "update guide" listing major changes between ActiveMQ 5.16.x and
> > > 5.17.x (JDK, Spring, ...) and introducing target roadmap for ActiveMQ 5.18.x
> > >
> > > Once the website is up to date, I will send the announcement email.
> > >
> > > These 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é <jb...@nanthrax.net>
> > > 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, activemq-jms-pool artifacts.
> > > >
> > > > 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 runtime
> > > > - remove of activemq-camel component (replaced by camel-activemq and
> > > > camel-jms components)
> > > > - remove leveldb
> > > > - tons of fixes and dependency updates
> > > >
> > > > Please take a look on the Release Notes for details:
> > > >
> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12346476
> > > >
> > > > Maven Staging Repository:
> > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1248/
> > > >
> > > > Dist Staging Repository:
> > > > https://dist.apache.org/repos/dist/dev/activemq/activemq/5.17.0/
> > > >
> > > > Git tag: activemq-5.17.0
> > > >
> > > > Please vote to approve this release:
> > > > [ ] +1 Approve the release
> > > > [ ] -1 Don't approve the release (please provide specific comments)
> > > >
> > > > This vote will be open for at least 72 hours.
> > > >
> > > > Thanks !
> > > > Regards
> > > > JB
> > > >
Re: [RESULT][VOTE] Apache ActiveMQ 5.17.0 release (take #2)
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Robbie,
Thanks for the fix. And yes, I saw the issue about apidocs symlink as
well, just wanted to avoid duplicating folders. But you are right, let
me fix that.
Regarding the other apidocs version, I forgot git add to add it on the
website. Basically, I wanted to push the latest 5.15.15 and 5.16.4
apidocs versions.
Gonna fix that as well.
Thanks !
Regards
JB
On Tue, Mar 15, 2022 at 12:39 PM Robbie Gemmell
<ro...@gmail.com> wrote:
>
> I have fixed the updated website so that 5.17.0 is actually considered
> a 'current' release, meaning it actually gets listed properly on the
> main download page, and has the correct download links etc added. It
> is generally good to look at the site update before publishing it
> (using scripted 'jekyll serve'), and certainly before announcing.
>
> To the 'checking before publish' point, the change to delete the
> src/maven/apidocs/ folder and replace it with a symlink to
> src/maven/5.17.0 is causes an error from the Jekyll test server (as
> below) since it ends up watching the target folder twice, directly and
> then again via the symlink.
>
> I didnt change this back, but personally I think it makes sense to
> skip the symlink and just use the apidocs folder. It would avoid such
> an error, and also means the diff for adding each release would only
> need to show difference in the javadoc files rather than containing
> literally the entire content of the javadoc, as the commit adding
> 5.17.0 does (in addition to complete content of removing the prior
> apidocs content, and for some reason 5.15.8, even though a 5.15.9
> folder remains).
>
>
> Server address: http://127.0.0.1:4000
> Server running... press ctrl-c to stop.
> ** 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/master/README.md
> LiveReload: Browser connected
>
>
>
> On Mon, 14 Mar 2022 at 13:26, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> >
> > Hi everyone,
> >
> > this vote passed with the following result:
> >
> > +1 (binding): Chris Shannon, Tim Bish, JB Onofré, Clebert Suconic
> > +1 (non binding): Robbie Gemmell, WBD, Matt Pavlovich
> >
> > I'm promoting the artifacts on Maven Central and dist.apache.org.
> >
> > Then, I will prepare two PRs updates for the website:
> > 1. announcement (download links, javadoc update, etc)
> > 2. quick "update guide" listing major changes between ActiveMQ 5.16.x and
> > 5.17.x (JDK, Spring, ...) and introducing target roadmap for ActiveMQ 5.18.x
> >
> > Once the website is up to date, I will send the announcement email.
> >
> > These 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é <jb...@nanthrax.net>
> > 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, activemq-jms-pool artifacts.
> > >
> > > 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 runtime
> > > - remove of activemq-camel component (replaced by camel-activemq and
> > > camel-jms components)
> > > - remove leveldb
> > > - tons of fixes and dependency updates
> > >
> > > Please take a look on the Release Notes for details:
> > >
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12346476
> > >
> > > Maven Staging Repository:
> > > https://repository.apache.org/content/repositories/orgapacheactivemq-1248/
> > >
> > > Dist Staging Repository:
> > > https://dist.apache.org/repos/dist/dev/activemq/activemq/5.17.0/
> > >
> > > Git tag: activemq-5.17.0
> > >
> > > Please vote to approve this release:
> > > [ ] +1 Approve the release
> > > [ ] -1 Don't approve the release (please provide specific comments)
> > >
> > > This vote will be open for at least 72 hours.
> > >
> > > Thanks !
> > > Regards
> > > JB
> > >
Re: [RESULT][VOTE] Apache ActiveMQ 5.17.0 release (take #2)
Posted by Justin Bertram <jb...@apache.org>.
+1
Justin
On Tue, Mar 15, 2022 at 8:39 AM Robbie Gemmell <ro...@gmail.com>
wrote:
> I think as all the useful info is on the download page that makes the
> most sense, its where people looking to download should always go, to
> get the latest release. If they happen 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é <jb...@nanthrax.net>
> wrote:
> >
> > Hi again ;)
> >
> > As the announcement is specifically for 5.17.0, I think it's more
> > "natural" to link to the specific release page.
> >
> > However, "overall" download could work as well as it drives users to
> > the same page.
> >
> > Either way is fine with me ;)
> >
> > Regards
> > JB
> >
> > On Tue, Mar 15, 2022 at 12:51 PM Robbie Gemmell
> > <ro...@gmail.com> wrote:
> > >
> > > Separately, I'd like to suggest the 5.x announcement mails link to the
> > > 'download page' rather than the 'release page'.
> > >
> > > So, use https://activemq.apache.org/components/classic/download/
> > > rather than e.g https://activemq.apache.org/activemq-5017000-release
> > >
> > > It's nicer/more succinct, yet has most of the same info, and links to
> > > the release page if needed...but nicely means when people follow older
> > > links as they quite often tend to do, they actually get directed to
> > > the latest 'current' release(s) first, which is what they should
> > > really be using. If they really really want older releases then those
> > > pages are also linked to from there.
> > >
> > > On Tue, 15 Mar 2022 at 11:39, Robbie Gemmell <ro...@gmail.com>
> wrote:
> > > >
> > > > I have fixed the updated website so that 5.17.0 is actually
> considered
> > > > a 'current' release, meaning it actually gets listed properly on the
> > > > main download page, and has the correct download links etc added. It
> > > > is generally good to look at the site update before publishing it
> > > > (using scripted 'jekyll serve'), and certainly before announcing.
> > > >
> > > > To the 'checking before publish' point, the change to delete the
> > > > src/maven/apidocs/ folder and replace it with a symlink to
> > > > src/maven/5.17.0 is causes an error from the Jekyll test server (as
> > > > below) since it ends up watching the target folder twice, directly
> and
> > > > then again via the symlink.
> > > >
> > > > I didnt change this back, but personally I think it makes sense to
> > > > skip the symlink and just use the apidocs folder. It would avoid such
> > > > an error, and also means the diff for adding each release would only
> > > > need to show difference in the javadoc files rather than containing
> > > > literally the entire content of the javadoc, as the commit adding
> > > > 5.17.0 does (in addition to complete content of removing the prior
> > > > apidocs content, and for some reason 5.15.8, even though a 5.15.9
> > > > folder remains).
> > > >
> > > >
> > > > Server address: http://127.0.0.1:4000
> > > > Server running... press ctrl-c to stop.
> > > > ** 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/master/README.md
> > > > LiveReload: Browser connected
> > > >
> > > >
> > > >
> > > > On Mon, 14 Mar 2022 at 13:26, Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
> > > > >
> > > > > Hi everyone,
> > > > >
> > > > > this vote passed with the following result:
> > > > >
> > > > > +1 (binding): Chris Shannon, Tim Bish, JB Onofré, Clebert Suconic
> > > > > +1 (non binding): Robbie Gemmell, WBD, Matt Pavlovich
> > > > >
> > > > > I'm promoting the artifacts on Maven Central and dist.apache.org.
> > > > >
> > > > > Then, I will prepare two PRs updates for the website:
> > > > > 1. announcement (download links, javadoc update, etc)
> > > > > 2. quick "update guide" listing major changes between ActiveMQ
> 5.16.x and
> > > > > 5.17.x (JDK, Spring, ...) and introducing target roadmap for
> ActiveMQ 5.18.x
> > > > >
> > > > > Once the website is up to date, I will send the announcement email.
> > > > >
> > > > > These 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é <
> jb@nanthrax.net>
> > > > > 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, activemq-jms-pool artifacts.
> > > > > >
> > > > > > 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 runtime
> > > > > > - remove of activemq-camel component (replaced by camel-activemq
> and
> > > > > > camel-jms components)
> > > > > > - remove leveldb
> > > > > > - tons of fixes and dependency updates
> > > > > >
> > > > > > Please take a look on the Release Notes for details:
> > > > > >
> > > > > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12346476
> > > > > >
> > > > > > Maven Staging Repository:
> > > > > >
> https://repository.apache.org/content/repositories/orgapacheactivemq-1248/
> > > > > >
> > > > > > Dist Staging Repository:
> > > > > > https://dist.apache.org/repos/dist/dev/activemq/activemq/5.17.0/
> > > > > >
> > > > > > Git tag: activemq-5.17.0
> > > > > >
> > > > > > Please vote to approve this release:
> > > > > > [ ] +1 Approve the release
> > > > > > [ ] -1 Don't approve the release (please provide specific
> comments)
> > > > > >
> > > > > > This vote will be open for at least 72 hours.
> > > > > >
> > > > > > Thanks !
> > > > > > Regards
> > > > > > JB
> > > > > >
>
>
Re: Re: [RESULT][VOTE] Apache ActiveMQ 5.17.0 release (take #2)
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Just to be clear: just remove this from your activemq.xml:
<!-- Allows accessing the server log -->
<bean id="logQuery" class="io.fabric8.insight.log.log4j.Log4jLogQuery"
lazy-init="false" scope="singleton"
init-method="start" destroy-method="stop">
</bean>
You can see the change here:
https://github.com/apache/activemq/commit/472dcf84979f063a375e5413d794e56117e52a9f
Regards
JB
On Thu, Mar 17, 2022 at 3:58 PM Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> Hi,
>
> You are using a custom activemq.xml right ?
>
> If you take a look on the activemq.xml provided with ActiveMQ 5.17.x,
> you can see that fabric8 insight log has been removed simply because
> it supports only log4j 1.x, not log4j 2.x.
>
> So you have to remove the fabric8-insight-log bean from activemq.xml
> or ask fabric8 an update to log4j2.
>
> Regards
> JB
>
> On Thu, Mar 17, 2022 at 1:58 PM Shank, Charles R <SH...@nationwide.com> wrote:
> >
> > Good day
> >
> > I am trying to install the version 5.17.0 and when I try to start my broker I am receiving this message
> >
> > ERROR: java.lang.RuntimeException: Failed to execute start task. Reason: org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [io.fabric8.insight.log.log4j.Log4jLogQuery] for bean with name 'logQuery' defined in class path resource [activemq.xml]; nested exception is java.lang.ClassNotFoundException: io.fabric8.insight.log.log4j.Log4jLogQuery
> > java.lang.RuntimeException: Failed to execute start task. Reason: org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [io.fabric8.insight.log.log4j.Log4jLogQuery] for bean with name 'logQuery' defined in class path resource [activemq.xml]; nested exception is java.lang.ClassNotFoundException: io.fabric8.insight.log.log4j.Log4jLogQuery
> >
> > any suggestions on how to resolve?
> >
> > Chuck Shank
> > Consultant, Technology Engineer
> > Middleware Technology
> > W 614-249-6672
> > shankc1@nationwide.com
> >
> >
> >
> > -----Original Message-----
> > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> > Sent: Tuesday, March 15, 2022 9:48 AM
> > To: dev@activemq.apache.org
> > Subject: [EXTERNAL] Re: [RESULT][VOTE] Apache ActiveMQ 5.17.0 release (take #2)
> >
> > Nationwide Information Security Warning: This is an EXTERNAL email. Use CAUTION before clicking on links, opening attachments, or responding. (Sender: dev-return-73178-SHANKC1=nationwide.com@activemq.apache.org)
> >
> > ------------------------------------------------------------------------------
> >
> >
> > OK, ack for next releases. Thanks.
> >
> > Regards
> > JB
> >
> > On Tue, Mar 15, 2022 at 2:29 PM Robbie Gemmell <ro...@gmail.com> wrote:
> > >
> > > I think as all the useful info is on the download page that makes the
> > > most sense, its where people looking to download should always go, to
> > > get the latest release. If they happen 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é <jb...@nanthrax.net> wrote:
> > > >
> > > > Hi again ;)
> > > >
> > > > As the announcement is specifically for 5.17.0, I think it's more
> > > > "natural" to link to the specific release page.
> > > >
> > > > However, "overall" download could work as well as it drives users to
> > > > the same page.
> > > >
> > > > Either way is fine with me ;)
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > On Tue, Mar 15, 2022 at 12:51 PM Robbie Gemmell
> > > > <ro...@gmail.com> wrote:
> > > > >
> > > > > Separately, I'd like to suggest the 5.x announcement mails link to
> > > > > the 'download page' rather than the 'release page'.
> > > > >
> > > > > So, use https://activemq.apache.org/components/classic/download/
> > > > > rather than e.g
> > > > > https://activemq.apache.org/activemq-5017000-release
> > > > >
> > > > > It's nicer/more succinct, yet has most of the same info, and links
> > > > > to the release page if needed...but nicely means when people
> > > > > follow older links as they quite often tend to do, they actually
> > > > > get directed to the latest 'current' release(s) first, which is
> > > > > what they should really be using. If they really really want older
> > > > > releases then those pages are also linked to from there.
> > > > >
> > > > > On Tue, 15 Mar 2022 at 11:39, Robbie Gemmell <ro...@gmail.com> wrote:
> > > > > >
> > > > > > I have fixed the updated website so that 5.17.0 is actually
> > > > > > considered a 'current' release, meaning it actually gets listed
> > > > > > properly on the main download page, and has the correct download
> > > > > > links etc added. It is generally good to look at the site update
> > > > > > before publishing it (using scripted 'jekyll serve'), and certainly before announcing.
> > > > > >
> > > > > > To the 'checking before publish' point, the change to delete the
> > > > > > src/maven/apidocs/ folder and replace it with a symlink to
> > > > > > src/maven/5.17.0 is causes an error from the Jekyll test server
> > > > > > (as
> > > > > > below) since it ends up watching the target folder twice,
> > > > > > directly and then again via the symlink.
> > > > > >
> > > > > > I didnt change this back, but personally I think it makes sense
> > > > > > to skip the symlink and just use the apidocs folder. It would
> > > > > > avoid such an error, and also means the diff for adding each
> > > > > > release would only need to show difference in the javadoc files
> > > > > > rather than containing literally the entire content of the
> > > > > > javadoc, as the commit adding
> > > > > > 5.17.0 does (in addition to complete content of removing the
> > > > > > prior apidocs content, and for some reason 5.15.8, even though a
> > > > > > 5.15.9 folder remains).
> > > > > >
> > > > > >
> > > > > > Server address: http://127.0.0.1:4000
> > > > > > Server running... press ctrl-c to stop.
> > > > > > ** 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/master/README.md
> > > > > > LiveReload: Browser connected
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Mon, 14 Mar 2022 at 13:26, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> > > > > > >
> > > > > > > Hi everyone,
> > > > > > >
> > > > > > > this vote passed with the following result:
> > > > > > >
> > > > > > > +1 (binding): Chris Shannon, Tim Bish, JB Onofré, Clebert
> > > > > > > +Suconic
> > > > > > > +1 (non binding): Robbie Gemmell, WBD, Matt Pavlovich
> > > > > > >
> > > > > > > I'm promoting the artifacts on Maven Central and dist.apache.org.
> > > > > > >
> > > > > > > Then, I will prepare two PRs updates for the website:
> > > > > > > 1. announcement (download links, javadoc update, etc) 2. quick
> > > > > > > "update guide" listing major changes between ActiveMQ 5.16.x
> > > > > > > and 5.17.x (JDK, Spring, ...) and introducing target roadmap
> > > > > > > for ActiveMQ 5.18.x
> > > > > > >
> > > > > > > Once the website is up to date, I will send the announcement email.
> > > > > > >
> > > > > > > These 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é
> > > > > > > <jb...@nanthrax.net>
> > > > > > > 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, activemq-jms-pool artifacts.
> > > > > > > >
> > > > > > > > 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 runtime
> > > > > > > > - remove of activemq-camel component (replaced by
> > > > > > > > camel-activemq and camel-jms components)
> > > > > > > > - remove leveldb
> > > > > > > > - tons of fixes and dependency updates
> > > > > > > >
> > > > > > > > Please take a look on the Release Notes for details:
> > > > > > > >
> > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> > > > > > > > ctId=12311210&version=12346476
> > > > > > > >
> > > > > > > > Maven Staging Repository:
> > > > > > > > https://repository.apache.org/content/repositories/orgapache
> > > > > > > > activemq-1248/
> > > > > > > >
> > > > > > > > Dist Staging Repository:
> > > > > > > > https://dist.apache.org/repos/dist/dev/activemq/activemq/5.1
> > > > > > > > 7.0/
> > > > > > > >
> > > > > > > > Git tag: activemq-5.17.0
> > > > > > > >
> > > > > > > > Please vote to approve this release:
> > > > > > > > [ ] +1 Approve the release
> > > > > > > > [ ] -1 Don't approve the release (please provide specific
> > > > > > > > comments)
> > > > > > > >
> > > > > > > > This vote will be open for at least 72 hours.
> > > > > > > >
> > > > > > > > Thanks !
> > > > > > > > Regards
> > > > > > > > JB
> > > > > > > >
Re: Re: [RESULT][VOTE] Apache ActiveMQ 5.17.0 release (take #2)
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,
You are using a custom activemq.xml right ?
If you take a look on the activemq.xml provided with ActiveMQ 5.17.x,
you can see that fabric8 insight log has been removed simply because
it supports only log4j 1.x, not log4j 2.x.
So you have to remove the fabric8-insight-log bean from activemq.xml
or ask fabric8 an update to log4j2.
Regards
JB
On Thu, Mar 17, 2022 at 1:58 PM Shank, Charles R <SH...@nationwide.com> wrote:
>
> Good day
>
> I am trying to install the version 5.17.0 and when I try to start my broker I am receiving this message
>
> ERROR: java.lang.RuntimeException: Failed to execute start task. Reason: org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [io.fabric8.insight.log.log4j.Log4jLogQuery] for bean with name 'logQuery' defined in class path resource [activemq.xml]; nested exception is java.lang.ClassNotFoundException: io.fabric8.insight.log.log4j.Log4jLogQuery
> java.lang.RuntimeException: Failed to execute start task. Reason: org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [io.fabric8.insight.log.log4j.Log4jLogQuery] for bean with name 'logQuery' defined in class path resource [activemq.xml]; nested exception is java.lang.ClassNotFoundException: io.fabric8.insight.log.log4j.Log4jLogQuery
>
> any suggestions on how to resolve?
>
> Chuck Shank
> Consultant, Technology Engineer
> Middleware Technology
> W 614-249-6672
> shankc1@nationwide.com
>
>
>
> -----Original Message-----
> From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> Sent: Tuesday, March 15, 2022 9:48 AM
> To: dev@activemq.apache.org
> Subject: [EXTERNAL] Re: [RESULT][VOTE] Apache ActiveMQ 5.17.0 release (take #2)
>
> Nationwide Information Security Warning: This is an EXTERNAL email. Use CAUTION before clicking on links, opening attachments, or responding. (Sender: dev-return-73178-SHANKC1=nationwide.com@activemq.apache.org)
>
> ------------------------------------------------------------------------------
>
>
> OK, ack for next releases. Thanks.
>
> Regards
> JB
>
> On Tue, Mar 15, 2022 at 2:29 PM Robbie Gemmell <ro...@gmail.com> wrote:
> >
> > I think as all the useful info is on the download page that makes the
> > most sense, its where people looking to download should always go, to
> > get the latest release. If they happen 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é <jb...@nanthrax.net> wrote:
> > >
> > > Hi again ;)
> > >
> > > As the announcement is specifically for 5.17.0, I think it's more
> > > "natural" to link to the specific release page.
> > >
> > > However, "overall" download could work as well as it drives users to
> > > the same page.
> > >
> > > Either way is fine with me ;)
> > >
> > > Regards
> > > JB
> > >
> > > On Tue, Mar 15, 2022 at 12:51 PM Robbie Gemmell
> > > <ro...@gmail.com> wrote:
> > > >
> > > > Separately, I'd like to suggest the 5.x announcement mails link to
> > > > the 'download page' rather than the 'release page'.
> > > >
> > > > So, use https://activemq.apache.org/components/classic/download/
> > > > rather than e.g
> > > > https://activemq.apache.org/activemq-5017000-release
> > > >
> > > > It's nicer/more succinct, yet has most of the same info, and links
> > > > to the release page if needed...but nicely means when people
> > > > follow older links as they quite often tend to do, they actually
> > > > get directed to the latest 'current' release(s) first, which is
> > > > what they should really be using. If they really really want older
> > > > releases then those pages are also linked to from there.
> > > >
> > > > On Tue, 15 Mar 2022 at 11:39, Robbie Gemmell <ro...@gmail.com> wrote:
> > > > >
> > > > > I have fixed the updated website so that 5.17.0 is actually
> > > > > considered a 'current' release, meaning it actually gets listed
> > > > > properly on the main download page, and has the correct download
> > > > > links etc added. It is generally good to look at the site update
> > > > > before publishing it (using scripted 'jekyll serve'), and certainly before announcing.
> > > > >
> > > > > To the 'checking before publish' point, the change to delete the
> > > > > src/maven/apidocs/ folder and replace it with a symlink to
> > > > > src/maven/5.17.0 is causes an error from the Jekyll test server
> > > > > (as
> > > > > below) since it ends up watching the target folder twice,
> > > > > directly and then again via the symlink.
> > > > >
> > > > > I didnt change this back, but personally I think it makes sense
> > > > > to skip the symlink and just use the apidocs folder. It would
> > > > > avoid such an error, and also means the diff for adding each
> > > > > release would only need to show difference in the javadoc files
> > > > > rather than containing literally the entire content of the
> > > > > javadoc, as the commit adding
> > > > > 5.17.0 does (in addition to complete content of removing the
> > > > > prior apidocs content, and for some reason 5.15.8, even though a
> > > > > 5.15.9 folder remains).
> > > > >
> > > > >
> > > > > Server address: http://127.0.0.1:4000
> > > > > Server running... press ctrl-c to stop.
> > > > > ** 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/master/README.md
> > > > > LiveReload: Browser connected
> > > > >
> > > > >
> > > > >
> > > > > On Mon, 14 Mar 2022 at 13:26, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> > > > > >
> > > > > > Hi everyone,
> > > > > >
> > > > > > this vote passed with the following result:
> > > > > >
> > > > > > +1 (binding): Chris Shannon, Tim Bish, JB Onofré, Clebert
> > > > > > +Suconic
> > > > > > +1 (non binding): Robbie Gemmell, WBD, Matt Pavlovich
> > > > > >
> > > > > > I'm promoting the artifacts on Maven Central and dist.apache.org.
> > > > > >
> > > > > > Then, I will prepare two PRs updates for the website:
> > > > > > 1. announcement (download links, javadoc update, etc) 2. quick
> > > > > > "update guide" listing major changes between ActiveMQ 5.16.x
> > > > > > and 5.17.x (JDK, Spring, ...) and introducing target roadmap
> > > > > > for ActiveMQ 5.18.x
> > > > > >
> > > > > > Once the website is up to date, I will send the announcement email.
> > > > > >
> > > > > > These 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é
> > > > > > <jb...@nanthrax.net>
> > > > > > 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, activemq-jms-pool artifacts.
> > > > > > >
> > > > > > > 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 runtime
> > > > > > > - remove of activemq-camel component (replaced by
> > > > > > > camel-activemq and camel-jms components)
> > > > > > > - remove leveldb
> > > > > > > - tons of fixes and dependency updates
> > > > > > >
> > > > > > > Please take a look on the Release Notes for details:
> > > > > > >
> > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> > > > > > > ctId=12311210&version=12346476
> > > > > > >
> > > > > > > Maven Staging Repository:
> > > > > > > https://repository.apache.org/content/repositories/orgapache
> > > > > > > activemq-1248/
> > > > > > >
> > > > > > > Dist Staging Repository:
> > > > > > > https://dist.apache.org/repos/dist/dev/activemq/activemq/5.1
> > > > > > > 7.0/
> > > > > > >
> > > > > > > Git tag: activemq-5.17.0
> > > > > > >
> > > > > > > Please vote to approve this release:
> > > > > > > [ ] +1 Approve the release
> > > > > > > [ ] -1 Don't approve the release (please provide specific
> > > > > > > comments)
> > > > > > >
> > > > > > > This vote will be open for at least 72 hours.
> > > > > > >
> > > > > > > Thanks !
> > > > > > > Regards
> > > > > > > JB
> > > > > > >
Re: Re: [RESULT][VOTE] Apache ActiveMQ 5.17.0 release (take #2)
Posted by Robbie Gemmell <ro...@gmail.com>.
You should use the users list for such questions, generally starting a
new thread and describing stuff like what changes if any you made to
the config.
I'm not familiar with these bits but there was a 'insight-log4j'
dependency that was removed in 5.17.0 as part of the changes to use
Log4J 2, I would assume that will be related.
On Thu, 17 Mar 2022 at 12:58, Shank, Charles R <SH...@nationwide.com> wrote:
>
> Good day
>
> I am trying to install the version 5.17.0 and when I try to start my broker I am receiving this message
>
> ERROR: java.lang.RuntimeException: Failed to execute start task. Reason: org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [io.fabric8.insight.log.log4j.Log4jLogQuery] for bean with name 'logQuery' defined in class path resource [activemq.xml]; nested exception is java.lang.ClassNotFoundException: io.fabric8.insight.log.log4j.Log4jLogQuery
> java.lang.RuntimeException: Failed to execute start task. Reason: org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [io.fabric8.insight.log.log4j.Log4jLogQuery] for bean with name 'logQuery' defined in class path resource [activemq.xml]; nested exception is java.lang.ClassNotFoundException: io.fabric8.insight.log.log4j.Log4jLogQuery
>
> any suggestions on how to resolve?
>
> Chuck Shank
> Consultant, Technology Engineer
> Middleware Technology
> W 614-249-6672
> shankc1@nationwide.com
>
>
>
> -----Original Message-----
> From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> Sent: Tuesday, March 15, 2022 9:48 AM
> To: dev@activemq.apache.org
> Subject: [EXTERNAL] Re: [RESULT][VOTE] Apache ActiveMQ 5.17.0 release (take #2)
>
> Nationwide Information Security Warning: This is an EXTERNAL email. Use CAUTION before clicking on links, opening attachments, or responding. (Sender: dev-return-73178-SHANKC1=nationwide.com@activemq.apache.org)
>
> ------------------------------------------------------------------------------
>
>
> OK, ack for next releases. Thanks.
>
> Regards
> JB
>
> On Tue, Mar 15, 2022 at 2:29 PM Robbie Gemmell <ro...@gmail.com> wrote:
> >
> > I think as all the useful info is on the download page that makes the
> > most sense, its where people looking to download should always go, to
> > get the latest release. If they happen 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é <jb...@nanthrax.net> wrote:
> > >
> > > Hi again ;)
> > >
> > > As the announcement is specifically for 5.17.0, I think it's more
> > > "natural" to link to the specific release page.
> > >
> > > However, "overall" download could work as well as it drives users to
> > > the same page.
> > >
> > > Either way is fine with me ;)
> > >
> > > Regards
> > > JB
> > >
> > > On Tue, Mar 15, 2022 at 12:51 PM Robbie Gemmell
> > > <ro...@gmail.com> wrote:
> > > >
> > > > Separately, I'd like to suggest the 5.x announcement mails link to
> > > > the 'download page' rather than the 'release page'.
> > > >
> > > > So, use https://activemq.apache.org/components/classic/download/
> > > > rather than e.g
> > > > https://activemq.apache.org/activemq-5017000-release
> > > >
> > > > It's nicer/more succinct, yet has most of the same info, and links
> > > > to the release page if needed...but nicely means when people
> > > > follow older links as they quite often tend to do, they actually
> > > > get directed to the latest 'current' release(s) first, which is
> > > > what they should really be using. If they really really want older
> > > > releases then those pages are also linked to from there.
> > > >
> > > > On Tue, 15 Mar 2022 at 11:39, Robbie Gemmell <ro...@gmail.com> wrote:
> > > > >
> > > > > I have fixed the updated website so that 5.17.0 is actually
> > > > > considered a 'current' release, meaning it actually gets listed
> > > > > properly on the main download page, and has the correct download
> > > > > links etc added. It is generally good to look at the site update
> > > > > before publishing it (using scripted 'jekyll serve'), and certainly before announcing.
> > > > >
> > > > > To the 'checking before publish' point, the change to delete the
> > > > > src/maven/apidocs/ folder and replace it with a symlink to
> > > > > src/maven/5.17.0 is causes an error from the Jekyll test server
> > > > > (as
> > > > > below) since it ends up watching the target folder twice,
> > > > > directly and then again via the symlink.
> > > > >
> > > > > I didnt change this back, but personally I think it makes sense
> > > > > to skip the symlink and just use the apidocs folder. It would
> > > > > avoid such an error, and also means the diff for adding each
> > > > > release would only need to show difference in the javadoc files
> > > > > rather than containing literally the entire content of the
> > > > > javadoc, as the commit adding
> > > > > 5.17.0 does (in addition to complete content of removing the
> > > > > prior apidocs content, and for some reason 5.15.8, even though a
> > > > > 5.15.9 folder remains).
> > > > >
> > > > >
> > > > > Server address: http://127.0.0.1:4000
> > > > > Server running... press ctrl-c to stop.
> > > > > ** 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/master/README.md
> > > > > LiveReload: Browser connected
> > > > >
> > > > >
> > > > >
> > > > > On Mon, 14 Mar 2022 at 13:26, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> > > > > >
> > > > > > Hi everyone,
> > > > > >
> > > > > > this vote passed with the following result:
> > > > > >
> > > > > > +1 (binding): Chris Shannon, Tim Bish, JB Onofré, Clebert
> > > > > > +Suconic
> > > > > > +1 (non binding): Robbie Gemmell, WBD, Matt Pavlovich
> > > > > >
> > > > > > I'm promoting the artifacts on Maven Central and dist.apache.org.
> > > > > >
> > > > > > Then, I will prepare two PRs updates for the website:
> > > > > > 1. announcement (download links, javadoc update, etc) 2. quick
> > > > > > "update guide" listing major changes between ActiveMQ 5.16.x
> > > > > > and 5.17.x (JDK, Spring, ...) and introducing target roadmap
> > > > > > for ActiveMQ 5.18.x
> > > > > >
> > > > > > Once the website is up to date, I will send the announcement email.
> > > > > >
> > > > > > These 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é
> > > > > > <jb...@nanthrax.net>
> > > > > > 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, activemq-jms-pool artifacts.
> > > > > > >
> > > > > > > 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 runtime
> > > > > > > - remove of activemq-camel component (replaced by
> > > > > > > camel-activemq and camel-jms components)
> > > > > > > - remove leveldb
> > > > > > > - tons of fixes and dependency updates
> > > > > > >
> > > > > > > Please take a look on the Release Notes for details:
> > > > > > >
> > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> > > > > > > ctId=12311210&version=12346476
> > > > > > >
> > > > > > > Maven Staging Repository:
> > > > > > > https://repository.apache.org/content/repositories/orgapache
> > > > > > > activemq-1248/
> > > > > > >
> > > > > > > Dist Staging Repository:
> > > > > > > https://dist.apache.org/repos/dist/dev/activemq/activemq/5.1
> > > > > > > 7.0/
> > > > > > >
> > > > > > > Git tag: activemq-5.17.0
> > > > > > >
> > > > > > > Please vote to approve this release:
> > > > > > > [ ] +1 Approve the release
> > > > > > > [ ] -1 Don't approve the release (please provide specific
> > > > > > > comments)
> > > > > > >
> > > > > > > This vote will be open for at least 72 hours.
> > > > > > >
> > > > > > > Thanks !
> > > > > > > Regards
> > > > > > > JB
> > > > > > >
RE: Re: [RESULT][VOTE] Apache ActiveMQ 5.17.0 release (take #2)
Posted by "Shank, Charles R" <SH...@nationwide.com>.
Good day
I am trying to install the version 5.17.0 and when I try to start my broker I am receiving this message
ERROR: java.lang.RuntimeException: Failed to execute start task. Reason: org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [io.fabric8.insight.log.log4j.Log4jLogQuery] for bean with name 'logQuery' defined in class path resource [activemq.xml]; nested exception is java.lang.ClassNotFoundException: io.fabric8.insight.log.log4j.Log4jLogQuery
java.lang.RuntimeException: Failed to execute start task. Reason: org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [io.fabric8.insight.log.log4j.Log4jLogQuery] for bean with name 'logQuery' defined in class path resource [activemq.xml]; nested exception is java.lang.ClassNotFoundException: io.fabric8.insight.log.log4j.Log4jLogQuery
any suggestions on how to resolve?
Chuck Shank
Consultant, Technology Engineer
Middleware Technology
W 614-249-6672
shankc1@nationwide.com
-----Original Message-----
From: Jean-Baptiste Onofré <jb...@nanthrax.net>
Sent: Tuesday, March 15, 2022 9:48 AM
To: dev@activemq.apache.org
Subject: [EXTERNAL] Re: [RESULT][VOTE] Apache ActiveMQ 5.17.0 release (take #2)
Nationwide Information Security Warning: This is an EXTERNAL email. Use CAUTION before clicking on links, opening attachments, or responding. (Sender: dev-return-73178-SHANKC1=nationwide.com@activemq.apache.org)
------------------------------------------------------------------------------
OK, ack for next releases. Thanks.
Regards
JB
On Tue, Mar 15, 2022 at 2:29 PM Robbie Gemmell <ro...@gmail.com> wrote:
>
> I think as all the useful info is on the download page that makes the
> most sense, its where people looking to download should always go, to
> get the latest release. If they happen 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é <jb...@nanthrax.net> wrote:
> >
> > Hi again ;)
> >
> > As the announcement is specifically for 5.17.0, I think it's more
> > "natural" to link to the specific release page.
> >
> > However, "overall" download could work as well as it drives users to
> > the same page.
> >
> > Either way is fine with me ;)
> >
> > Regards
> > JB
> >
> > On Tue, Mar 15, 2022 at 12:51 PM Robbie Gemmell
> > <ro...@gmail.com> wrote:
> > >
> > > Separately, I'd like to suggest the 5.x announcement mails link to
> > > the 'download page' rather than the 'release page'.
> > >
> > > So, use https://activemq.apache.org/components/classic/download/
> > > rather than e.g
> > > https://activemq.apache.org/activemq-5017000-release
> > >
> > > It's nicer/more succinct, yet has most of the same info, and links
> > > to the release page if needed...but nicely means when people
> > > follow older links as they quite often tend to do, they actually
> > > get directed to the latest 'current' release(s) first, which is
> > > what they should really be using. If they really really want older
> > > releases then those pages are also linked to from there.
> > >
> > > On Tue, 15 Mar 2022 at 11:39, Robbie Gemmell <ro...@gmail.com> wrote:
> > > >
> > > > I have fixed the updated website so that 5.17.0 is actually
> > > > considered a 'current' release, meaning it actually gets listed
> > > > properly on the main download page, and has the correct download
> > > > links etc added. It is generally good to look at the site update
> > > > before publishing it (using scripted 'jekyll serve'), and certainly before announcing.
> > > >
> > > > To the 'checking before publish' point, the change to delete the
> > > > src/maven/apidocs/ folder and replace it with a symlink to
> > > > src/maven/5.17.0 is causes an error from the Jekyll test server
> > > > (as
> > > > below) since it ends up watching the target folder twice,
> > > > directly and then again via the symlink.
> > > >
> > > > I didnt change this back, but personally I think it makes sense
> > > > to skip the symlink and just use the apidocs folder. It would
> > > > avoid such an error, and also means the diff for adding each
> > > > release would only need to show difference in the javadoc files
> > > > rather than containing literally the entire content of the
> > > > javadoc, as the commit adding
> > > > 5.17.0 does (in addition to complete content of removing the
> > > > prior apidocs content, and for some reason 5.15.8, even though a
> > > > 5.15.9 folder remains).
> > > >
> > > >
> > > > Server address: http://127.0.0.1:4000
> > > > Server running... press ctrl-c to stop.
> > > > ** 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/master/README.md
> > > > LiveReload: Browser connected
> > > >
> > > >
> > > >
> > > > On Mon, 14 Mar 2022 at 13:26, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> > > > >
> > > > > Hi everyone,
> > > > >
> > > > > this vote passed with the following result:
> > > > >
> > > > > +1 (binding): Chris Shannon, Tim Bish, JB Onofré, Clebert
> > > > > +Suconic
> > > > > +1 (non binding): Robbie Gemmell, WBD, Matt Pavlovich
> > > > >
> > > > > I'm promoting the artifacts on Maven Central and dist.apache.org.
> > > > >
> > > > > Then, I will prepare two PRs updates for the website:
> > > > > 1. announcement (download links, javadoc update, etc) 2. quick
> > > > > "update guide" listing major changes between ActiveMQ 5.16.x
> > > > > and 5.17.x (JDK, Spring, ...) and introducing target roadmap
> > > > > for ActiveMQ 5.18.x
> > > > >
> > > > > Once the website is up to date, I will send the announcement email.
> > > > >
> > > > > These 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é
> > > > > <jb...@nanthrax.net>
> > > > > 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, activemq-jms-pool artifacts.
> > > > > >
> > > > > > 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 runtime
> > > > > > - remove of activemq-camel component (replaced by
> > > > > > camel-activemq and camel-jms components)
> > > > > > - remove leveldb
> > > > > > - tons of fixes and dependency updates
> > > > > >
> > > > > > Please take a look on the Release Notes for details:
> > > > > >
> > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> > > > > > ctId=12311210&version=12346476
> > > > > >
> > > > > > Maven Staging Repository:
> > > > > > https://repository.apache.org/content/repositories/orgapache
> > > > > > activemq-1248/
> > > > > >
> > > > > > Dist Staging Repository:
> > > > > > https://dist.apache.org/repos/dist/dev/activemq/activemq/5.1
> > > > > > 7.0/
> > > > > >
> > > > > > Git tag: activemq-5.17.0
> > > > > >
> > > > > > Please vote to approve this release:
> > > > > > [ ] +1 Approve the release
> > > > > > [ ] -1 Don't approve the release (please provide specific
> > > > > > comments)
> > > > > >
> > > > > > This vote will be open for at least 72 hours.
> > > > > >
> > > > > > Thanks !
> > > > > > Regards
> > > > > > JB
> > > > > >
Re: [RESULT][VOTE] Apache ActiveMQ 5.17.0 release (take #2)
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
OK, ack for next releases. Thanks.
Regards
JB
On Tue, Mar 15, 2022 at 2:29 PM Robbie Gemmell <ro...@gmail.com> wrote:
>
> I think as all the useful info is on the download page that makes the
> most sense, its where people looking to download should always go, to
> get the latest release. If they happen 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é <jb...@nanthrax.net> wrote:
> >
> > Hi again ;)
> >
> > As the announcement is specifically for 5.17.0, I think it's more
> > "natural" to link to the specific release page.
> >
> > However, "overall" download could work as well as it drives users to
> > the same page.
> >
> > Either way is fine with me ;)
> >
> > Regards
> > JB
> >
> > On Tue, Mar 15, 2022 at 12:51 PM Robbie Gemmell
> > <ro...@gmail.com> wrote:
> > >
> > > Separately, I'd like to suggest the 5.x announcement mails link to the
> > > 'download page' rather than the 'release page'.
> > >
> > > So, use https://activemq.apache.org/components/classic/download/
> > > rather than e.g https://activemq.apache.org/activemq-5017000-release
> > >
> > > It's nicer/more succinct, yet has most of the same info, and links to
> > > the release page if needed...but nicely means when people follow older
> > > links as they quite often tend to do, they actually get directed to
> > > the latest 'current' release(s) first, which is what they should
> > > really be using. If they really really want older releases then those
> > > pages are also linked to from there.
> > >
> > > On Tue, 15 Mar 2022 at 11:39, Robbie Gemmell <ro...@gmail.com> wrote:
> > > >
> > > > I have fixed the updated website so that 5.17.0 is actually considered
> > > > a 'current' release, meaning it actually gets listed properly on the
> > > > main download page, and has the correct download links etc added. It
> > > > is generally good to look at the site update before publishing it
> > > > (using scripted 'jekyll serve'), and certainly before announcing.
> > > >
> > > > To the 'checking before publish' point, the change to delete the
> > > > src/maven/apidocs/ folder and replace it with a symlink to
> > > > src/maven/5.17.0 is causes an error from the Jekyll test server (as
> > > > below) since it ends up watching the target folder twice, directly and
> > > > then again via the symlink.
> > > >
> > > > I didnt change this back, but personally I think it makes sense to
> > > > skip the symlink and just use the apidocs folder. It would avoid such
> > > > an error, and also means the diff for adding each release would only
> > > > need to show difference in the javadoc files rather than containing
> > > > literally the entire content of the javadoc, as the commit adding
> > > > 5.17.0 does (in addition to complete content of removing the prior
> > > > apidocs content, and for some reason 5.15.8, even though a 5.15.9
> > > > folder remains).
> > > >
> > > >
> > > > Server address: http://127.0.0.1:4000
> > > > Server running... press ctrl-c to stop.
> > > > ** 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/master/README.md
> > > > LiveReload: Browser connected
> > > >
> > > >
> > > >
> > > > On Mon, 14 Mar 2022 at 13:26, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> > > > >
> > > > > Hi everyone,
> > > > >
> > > > > this vote passed with the following result:
> > > > >
> > > > > +1 (binding): Chris Shannon, Tim Bish, JB Onofré, Clebert Suconic
> > > > > +1 (non binding): Robbie Gemmell, WBD, Matt Pavlovich
> > > > >
> > > > > I'm promoting the artifacts on Maven Central and dist.apache.org.
> > > > >
> > > > > Then, I will prepare two PRs updates for the website:
> > > > > 1. announcement (download links, javadoc update, etc)
> > > > > 2. quick "update guide" listing major changes between ActiveMQ 5.16.x and
> > > > > 5.17.x (JDK, Spring, ...) and introducing target roadmap for ActiveMQ 5.18.x
> > > > >
> > > > > Once the website is up to date, I will send the announcement email.
> > > > >
> > > > > These 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é <jb...@nanthrax.net>
> > > > > 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, activemq-jms-pool artifacts.
> > > > > >
> > > > > > 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 runtime
> > > > > > - remove of activemq-camel component (replaced by camel-activemq and
> > > > > > camel-jms components)
> > > > > > - remove leveldb
> > > > > > - tons of fixes and dependency updates
> > > > > >
> > > > > > Please take a look on the Release Notes for details:
> > > > > >
> > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12346476
> > > > > >
> > > > > > Maven Staging Repository:
> > > > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1248/
> > > > > >
> > > > > > Dist Staging Repository:
> > > > > > https://dist.apache.org/repos/dist/dev/activemq/activemq/5.17.0/
> > > > > >
> > > > > > Git tag: activemq-5.17.0
> > > > > >
> > > > > > Please vote to approve this release:
> > > > > > [ ] +1 Approve the release
> > > > > > [ ] -1 Don't approve the release (please provide specific comments)
> > > > > >
> > > > > > This vote will be open for at least 72 hours.
> > > > > >
> > > > > > Thanks !
> > > > > > Regards
> > > > > > JB
> > > > > >
Re: [RESULT][VOTE] Apache ActiveMQ 5.17.0 release (take #2)
Posted by Robbie Gemmell <ro...@gmail.com>.
I think as all the useful info is on the download page that makes the
most sense, its where people looking to download should always go, to
get the latest release. If they happen 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é <jb...@nanthrax.net> wrote:
>
> Hi again ;)
>
> As the announcement is specifically for 5.17.0, I think it's more
> "natural" to link to the specific release page.
>
> However, "overall" download could work as well as it drives users to
> the same page.
>
> Either way is fine with me ;)
>
> Regards
> JB
>
> On Tue, Mar 15, 2022 at 12:51 PM Robbie Gemmell
> <ro...@gmail.com> wrote:
> >
> > Separately, I'd like to suggest the 5.x announcement mails link to the
> > 'download page' rather than the 'release page'.
> >
> > So, use https://activemq.apache.org/components/classic/download/
> > rather than e.g https://activemq.apache.org/activemq-5017000-release
> >
> > It's nicer/more succinct, yet has most of the same info, and links to
> > the release page if needed...but nicely means when people follow older
> > links as they quite often tend to do, they actually get directed to
> > the latest 'current' release(s) first, which is what they should
> > really be using. If they really really want older releases then those
> > pages are also linked to from there.
> >
> > On Tue, 15 Mar 2022 at 11:39, Robbie Gemmell <ro...@gmail.com> wrote:
> > >
> > > I have fixed the updated website so that 5.17.0 is actually considered
> > > a 'current' release, meaning it actually gets listed properly on the
> > > main download page, and has the correct download links etc added. It
> > > is generally good to look at the site update before publishing it
> > > (using scripted 'jekyll serve'), and certainly before announcing.
> > >
> > > To the 'checking before publish' point, the change to delete the
> > > src/maven/apidocs/ folder and replace it with a symlink to
> > > src/maven/5.17.0 is causes an error from the Jekyll test server (as
> > > below) since it ends up watching the target folder twice, directly and
> > > then again via the symlink.
> > >
> > > I didnt change this back, but personally I think it makes sense to
> > > skip the symlink and just use the apidocs folder. It would avoid such
> > > an error, and also means the diff for adding each release would only
> > > need to show difference in the javadoc files rather than containing
> > > literally the entire content of the javadoc, as the commit adding
> > > 5.17.0 does (in addition to complete content of removing the prior
> > > apidocs content, and for some reason 5.15.8, even though a 5.15.9
> > > folder remains).
> > >
> > >
> > > Server address: http://127.0.0.1:4000
> > > Server running... press ctrl-c to stop.
> > > ** 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/master/README.md
> > > LiveReload: Browser connected
> > >
> > >
> > >
> > > On Mon, 14 Mar 2022 at 13:26, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> > > >
> > > > Hi everyone,
> > > >
> > > > this vote passed with the following result:
> > > >
> > > > +1 (binding): Chris Shannon, Tim Bish, JB Onofré, Clebert Suconic
> > > > +1 (non binding): Robbie Gemmell, WBD, Matt Pavlovich
> > > >
> > > > I'm promoting the artifacts on Maven Central and dist.apache.org.
> > > >
> > > > Then, I will prepare two PRs updates for the website:
> > > > 1. announcement (download links, javadoc update, etc)
> > > > 2. quick "update guide" listing major changes between ActiveMQ 5.16.x and
> > > > 5.17.x (JDK, Spring, ...) and introducing target roadmap for ActiveMQ 5.18.x
> > > >
> > > > Once the website is up to date, I will send the announcement email.
> > > >
> > > > These 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é <jb...@nanthrax.net>
> > > > 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, activemq-jms-pool artifacts.
> > > > >
> > > > > 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 runtime
> > > > > - remove of activemq-camel component (replaced by camel-activemq and
> > > > > camel-jms components)
> > > > > - remove leveldb
> > > > > - tons of fixes and dependency updates
> > > > >
> > > > > Please take a look on the Release Notes for details:
> > > > >
> > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12346476
> > > > >
> > > > > Maven Staging Repository:
> > > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1248/
> > > > >
> > > > > Dist Staging Repository:
> > > > > https://dist.apache.org/repos/dist/dev/activemq/activemq/5.17.0/
> > > > >
> > > > > Git tag: activemq-5.17.0
> > > > >
> > > > > Please vote to approve this release:
> > > > > [ ] +1 Approve the release
> > > > > [ ] -1 Don't approve the release (please provide specific comments)
> > > > >
> > > > > This vote will be open for at least 72 hours.
> > > > >
> > > > > Thanks !
> > > > > Regards
> > > > > JB
> > > > >
Re: [RESULT][VOTE] Apache ActiveMQ 5.17.0 release (take #2)
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi again ;)
As the announcement is specifically for 5.17.0, I think it's more
"natural" to link to the specific release page.
However, "overall" download could work as well as it drives users to
the same page.
Either way is fine with me ;)
Regards
JB
On Tue, Mar 15, 2022 at 12:51 PM Robbie Gemmell
<ro...@gmail.com> wrote:
>
> Separately, I'd like to suggest the 5.x announcement mails link to the
> 'download page' rather than the 'release page'.
>
> So, use https://activemq.apache.org/components/classic/download/
> rather than e.g https://activemq.apache.org/activemq-5017000-release
>
> It's nicer/more succinct, yet has most of the same info, and links to
> the release page if needed...but nicely means when people follow older
> links as they quite often tend to do, they actually get directed to
> the latest 'current' release(s) first, which is what they should
> really be using. If they really really want older releases then those
> pages are also linked to from there.
>
> On Tue, 15 Mar 2022 at 11:39, Robbie Gemmell <ro...@gmail.com> wrote:
> >
> > I have fixed the updated website so that 5.17.0 is actually considered
> > a 'current' release, meaning it actually gets listed properly on the
> > main download page, and has the correct download links etc added. It
> > is generally good to look at the site update before publishing it
> > (using scripted 'jekyll serve'), and certainly before announcing.
> >
> > To the 'checking before publish' point, the change to delete the
> > src/maven/apidocs/ folder and replace it with a symlink to
> > src/maven/5.17.0 is causes an error from the Jekyll test server (as
> > below) since it ends up watching the target folder twice, directly and
> > then again via the symlink.
> >
> > I didnt change this back, but personally I think it makes sense to
> > skip the symlink and just use the apidocs folder. It would avoid such
> > an error, and also means the diff for adding each release would only
> > need to show difference in the javadoc files rather than containing
> > literally the entire content of the javadoc, as the commit adding
> > 5.17.0 does (in addition to complete content of removing the prior
> > apidocs content, and for some reason 5.15.8, even though a 5.15.9
> > folder remains).
> >
> >
> > Server address: http://127.0.0.1:4000
> > Server running... press ctrl-c to stop.
> > ** 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/master/README.md
> > LiveReload: Browser connected
> >
> >
> >
> > On Mon, 14 Mar 2022 at 13:26, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> > >
> > > Hi everyone,
> > >
> > > this vote passed with the following result:
> > >
> > > +1 (binding): Chris Shannon, Tim Bish, JB Onofré, Clebert Suconic
> > > +1 (non binding): Robbie Gemmell, WBD, Matt Pavlovich
> > >
> > > I'm promoting the artifacts on Maven Central and dist.apache.org.
> > >
> > > Then, I will prepare two PRs updates for the website:
> > > 1. announcement (download links, javadoc update, etc)
> > > 2. quick "update guide" listing major changes between ActiveMQ 5.16.x and
> > > 5.17.x (JDK, Spring, ...) and introducing target roadmap for ActiveMQ 5.18.x
> > >
> > > Once the website is up to date, I will send the announcement email.
> > >
> > > These 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é <jb...@nanthrax.net>
> > > 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, activemq-jms-pool artifacts.
> > > >
> > > > 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 runtime
> > > > - remove of activemq-camel component (replaced by camel-activemq and
> > > > camel-jms components)
> > > > - remove leveldb
> > > > - tons of fixes and dependency updates
> > > >
> > > > Please take a look on the Release Notes for details:
> > > >
> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12346476
> > > >
> > > > Maven Staging Repository:
> > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1248/
> > > >
> > > > Dist Staging Repository:
> > > > https://dist.apache.org/repos/dist/dev/activemq/activemq/5.17.0/
> > > >
> > > > Git tag: activemq-5.17.0
> > > >
> > > > Please vote to approve this release:
> > > > [ ] +1 Approve the release
> > > > [ ] -1 Don't approve the release (please provide specific comments)
> > > >
> > > > This vote will be open for at least 72 hours.
> > > >
> > > > Thanks !
> > > > Regards
> > > > JB
> > > >
Re: [RESULT][VOTE] Apache ActiveMQ 5.17.0 release (take #2)
Posted by Robbie Gemmell <ro...@gmail.com>.
Separately, I'd like to suggest the 5.x announcement mails link to the
'download page' rather than the 'release page'.
So, use https://activemq.apache.org/components/classic/download/
rather than e.g https://activemq.apache.org/activemq-5017000-release
It's nicer/more succinct, yet has most of the same info, and links to
the release page if needed...but nicely means when people follow older
links as they quite often tend to do, they actually get directed to
the latest 'current' release(s) first, which is what they should
really be using. If they really really want older releases then those
pages are also linked to from there.
On Tue, 15 Mar 2022 at 11:39, Robbie Gemmell <ro...@gmail.com> wrote:
>
> I have fixed the updated website so that 5.17.0 is actually considered
> a 'current' release, meaning it actually gets listed properly on the
> main download page, and has the correct download links etc added. It
> is generally good to look at the site update before publishing it
> (using scripted 'jekyll serve'), and certainly before announcing.
>
> To the 'checking before publish' point, the change to delete the
> src/maven/apidocs/ folder and replace it with a symlink to
> src/maven/5.17.0 is causes an error from the Jekyll test server (as
> below) since it ends up watching the target folder twice, directly and
> then again via the symlink.
>
> I didnt change this back, but personally I think it makes sense to
> skip the symlink and just use the apidocs folder. It would avoid such
> an error, and also means the diff for adding each release would only
> need to show difference in the javadoc files rather than containing
> literally the entire content of the javadoc, as the commit adding
> 5.17.0 does (in addition to complete content of removing the prior
> apidocs content, and for some reason 5.15.8, even though a 5.15.9
> folder remains).
>
>
> Server address: http://127.0.0.1:4000
> Server running... press ctrl-c to stop.
> ** 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/master/README.md
> LiveReload: Browser connected
>
>
>
> On Mon, 14 Mar 2022 at 13:26, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> >
> > Hi everyone,
> >
> > this vote passed with the following result:
> >
> > +1 (binding): Chris Shannon, Tim Bish, JB Onofré, Clebert Suconic
> > +1 (non binding): Robbie Gemmell, WBD, Matt Pavlovich
> >
> > I'm promoting the artifacts on Maven Central and dist.apache.org.
> >
> > Then, I will prepare two PRs updates for the website:
> > 1. announcement (download links, javadoc update, etc)
> > 2. quick "update guide" listing major changes between ActiveMQ 5.16.x and
> > 5.17.x (JDK, Spring, ...) and introducing target roadmap for ActiveMQ 5.18.x
> >
> > Once the website is up to date, I will send the announcement email.
> >
> > These 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é <jb...@nanthrax.net>
> > 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, activemq-jms-pool artifacts.
> > >
> > > 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 runtime
> > > - remove of activemq-camel component (replaced by camel-activemq and
> > > camel-jms components)
> > > - remove leveldb
> > > - tons of fixes and dependency updates
> > >
> > > Please take a look on the Release Notes for details:
> > >
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12346476
> > >
> > > Maven Staging Repository:
> > > https://repository.apache.org/content/repositories/orgapacheactivemq-1248/
> > >
> > > Dist Staging Repository:
> > > https://dist.apache.org/repos/dist/dev/activemq/activemq/5.17.0/
> > >
> > > Git tag: activemq-5.17.0
> > >
> > > Please vote to approve this release:
> > > [ ] +1 Approve the release
> > > [ ] -1 Don't approve the release (please provide specific comments)
> > >
> > > This vote will be open for at least 72 hours.
> > >
> > > Thanks !
> > > Regards
> > > JB
> > >
Re: [RESULT][VOTE] Apache ActiveMQ 5.17.0 release (take #2)
Posted by Robbie Gemmell <ro...@gmail.com>.
I have fixed the updated website so that 5.17.0 is actually considered
a 'current' release, meaning it actually gets listed properly on the
main download page, and has the correct download links etc added. It
is generally good to look at the site update before publishing it
(using scripted 'jekyll serve'), and certainly before announcing.
To the 'checking before publish' point, the change to delete the
src/maven/apidocs/ folder and replace it with a symlink to
src/maven/5.17.0 is causes an error from the Jekyll test server (as
below) since it ends up watching the target folder twice, directly and
then again via the symlink.
I didnt change this back, but personally I think it makes sense to
skip the symlink and just use the apidocs folder. It would avoid such
an error, and also means the diff for adding each release would only
need to show difference in the javadoc files rather than containing
literally the entire content of the javadoc, as the commit adding
5.17.0 does (in addition to complete content of removing the prior
apidocs content, and for some reason 5.15.8, even though a 5.15.9
folder remains).
Server address: http://127.0.0.1:4000
Server running... press ctrl-c to stop.
** 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/master/README.md
LiveReload: Browser connected
On Mon, 14 Mar 2022 at 13:26, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> Hi everyone,
>
> this vote passed with the following result:
>
> +1 (binding): Chris Shannon, Tim Bish, JB Onofré, Clebert Suconic
> +1 (non binding): Robbie Gemmell, WBD, Matt Pavlovich
>
> I'm promoting the artifacts on Maven Central and dist.apache.org.
>
> Then, I will prepare two PRs updates for the website:
> 1. announcement (download links, javadoc update, etc)
> 2. quick "update guide" listing major changes between ActiveMQ 5.16.x and
> 5.17.x (JDK, Spring, ...) and introducing target roadmap for ActiveMQ 5.18.x
>
> Once the website is up to date, I will send the announcement email.
>
> These 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é <jb...@nanthrax.net>
> 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, activemq-jms-pool artifacts.
> >
> > 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 runtime
> > - remove of activemq-camel component (replaced by camel-activemq and
> > camel-jms components)
> > - remove leveldb
> > - tons of fixes and dependency updates
> >
> > Please take a look on the Release Notes for details:
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12346476
> >
> > Maven Staging Repository:
> > https://repository.apache.org/content/repositories/orgapacheactivemq-1248/
> >
> > Dist Staging Repository:
> > https://dist.apache.org/repos/dist/dev/activemq/activemq/5.17.0/
> >
> > Git tag: activemq-5.17.0
> >
> > Please vote to approve this release:
> > [ ] +1 Approve the release
> > [ ] -1 Don't approve the release (please provide specific comments)
> >
> > This vote will be open for at least 72 hours.
> >
> > Thanks !
> > Regards
> > JB
> >