activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Bertram <>
Subject Re: [DISCUSS] ActiveMQ Artemis 2.x stream
Date Thu, 09 Feb 2017 17:08:47 GMT
Can you elaborate on that, Matt?  What exactly do you mean by "plugin support"?  What user-facing
APIs would necessarily break?


----- Original Message -----
From: "Matt Pavlovich" <>
Sent: Thursday, February 9, 2017 11:03:31 AM
Subject: Re: [DISCUSS] ActiveMQ Artemis 2.x stream


I think an important API breakage issue is plugin support.


On 2/9/17 6:18 AM, Martyn Taylor wrote:
> All,
> As discussed in a previous thread [1] Artemis master has had a major bump
> (due to major model refactor).
> The great news is that the new model is more flexible and lends itself well
> to 5.x features like Virtual Topics as well as being consistent across all
> protocols.  The not so good news is that this work required API breakages,
> hence the major version bump.).  This refactor work (mostly around the
> addressing scheme [2]) is now completed.
> The code base is now in a stable state, and as such, I'd like to start
> thinking about doing a release off of master as an Apache Artemis 2.0.0 to
> get the new changes into the hands of users.
> I'd like to open discussion around this topic, does anyone have any
> suggestions, or can think of anything that is needed before we go ahead
> with a major release? This is the perfect time to do anything that could
> break APIs, drop deprecated methods support, break data format etc...
> Cheers
> Martyn
> [1]
> [2]

View raw message