+1 (binding)
* Checked parent version in pom.xml files using `grep -LPrz --include
pom.xml "(.|\n)*2.26.0<\/version>(.|\n)*<\/parent>" ./`
* Ran binary broker instance on Fedora 36 using OpenJDK 11
* Checked the web console using `Google Chrome`
* Checked producing, browsing and consuming
I think that's fair.
+1
Justin
On Thu, Sep 22, 2022 at 2:58 PM Clebert Suconic
wrote:
> I am following up with an item that will be part of the document
> upload on the release notes:
>
> https://github.com/apache/activemq-artemis/pull/4229
>
>
>
> Rest as I said it's a maven dependency.
As I said on the Voting Thread. Rest is an independent maven
component. Users have to consume it from maven on their own Rest
application.
So, they can still keep doing it from a previous release until they
decide to not use it any more:
https://github.com/apache/activemq-artemis/pull/4229
I am following up with an item that will be part of the document
upload on the release notes:
https://github.com/apache/activemq-artemis/pull/4229
Rest as I said it's a maven dependency. There's no point in keeping it
as it can be accessed from a previous maven repository.
@Justin Bertram If
and it turns out activeMQ Artemis Rest is not part of the
distribution... (I don't think it's ever been).
it's a component that you consume from maven and you have to create
your own war with your dependency.
in these terms the current REST would work as is as long as you use it
from a previous
The ActiveMQ Artemis Rest module itself is being pretty much
abandonware and no one wants to fix it...
To fix it we would need to bring a few versions up to date.. and make
some improvements on the module.
People can still use the Rest from any previous download of artemis.
Just bring the WAR
I may be a bit ignorant here (not a java dev), but how changing the logging
framework may justify and imply removing the whole functional module?
On Thu, Sep 22, 2022 at 8:55 PM Clebert Suconic
wrote:
> We can put a release notes on how to bring the rest from a previous
> version and still
We can put a release notes on how to bring the rest from a previous
version and still install in the current release... noticing this
won't be supported in future releases.
And if you prefer to keep the module, just update the module and bring
it back please. This release should progress I
>> Although I don't
think anybody wants to invest the resources to bring all the dependencies
up-to-date. <<
until someone does that, I think it should be out.
this is pretty much abandonware.
On Thu, Sep 22, 2022 at 2:04 PM Justin Bertram wrote:
>
> I've been meaning to get to this for
if you want to keep that Rest, please fix it (update jboss-rest) and
then move it back.
Especially we are removing jboss-logging, and that rest implementation
is strongly dependent on jboss-logging.
On Thu, Sep 22, 2022 at 2:07 PM Justin Bertram wrote:
>
> -1 (binding)
>
> I just responded on
-1 (binding)
I just responded on the [DISCUSS] thread about removing the REST interface.
As far as I can tell the REST interface is perfectly functional. I think we
should deprecate it and update the documentation with an explanation before
removing it completely.
Justin
On Wed, Sep 21, 2022
I've been meaning to get to this for awhile. Better late than never, right?
Generally speaking, I agree that REST is not a great fit for messaging.
Whenever folks ask about it on the mailing lists, Slack, Stack Overflow,
etc. I strongly encourage them for two main reasons:
- The STOMP protocol
On Wed, 21 Sept 2022 at 21:24, Clebert Suconic
wrote:
>
> I would like to propose an Apache ActiveMQ Artemis 2.26.0 release.
>
>
> We removed ActiveMQ Artemis Rest, (which was already non functional)
> as part of this release.
> And other improvements and bug fixes.
>
>
> The release notes can be
+1
On Wed, 21 Sept 2022 at 21:24, Clebert Suconic
wrote:
>
> I would like to propose an Apache ActiveMQ Artemis 2.26.0 release.
>
>
> We removed ActiveMQ Artemis Rest, (which was already non functional)
> as part of this release.
> And other improvements and bug fixes.
>
>
> The release notes
14 matches
Mail list logo
