It has been a long time since this came up but it looks like I already made the point on the PR that the protobuf code almost never changes. The last release was done in 2010 so it hasn't been updated in 16 years.
So my main question is what exactly are you expecting to change that we would need to be releasing every version or prototyping? I certainly expect that we might need to make some changes soon if we are making updates for shared subscriptions or if we want to modernize it, but I would think we'd update the version once and then it probably wouldn't change for another 16 years. I'm not necessarily against it per se but I'm just struggling to see why we need to do this and what you expect will be changing frequently enough to justify the move vs keeping it separate and only releasing it when infrequent updates happen. Chris On Tue, Mar 24, 2026 at 10:21 AM Matt Pavlovich <[email protected]> wrote: > The activemq-protobuf project was split out from the main line project a > while ago and I don’t think it serves the project having it split out. > > 1. It is more work to maintain an independent module that is rarely used > by any other project (JDK alignment, Maven modules, release, vote, issues, > etc) > see: > https://mvnrepository.com/artifact/org.apache.activemq.protobuf/activemq-protobuf/1.1 > > Note: The next release would automatically signal an upgrade to any > consumer of this jar by the version number being higher than the current > > 2. Having this hosted will allow us to more quickly experiment and modify > the broker for any datastore changes that need to be made— changes to > activemq-protobuf and other activemq-* modules may need to be merged > together for feature changes vs ‘guessing’ if a design works in > activemq-protobuf, releasing and then changing the main broker modules. > > PR discussion here: > https://github.com/apache/activemq/pull/1209 > > Thanks, > Matt Pavlovich
