[ 
https://issues.apache.org/jira/browse/OPENWIRE-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17794406#comment-17794406
 ] 

Matt Pavlovich edited comment on OPENWIRE-71 at 12/7/23 7:41 PM:
-----------------------------------------------------------------

Right, I was suggesting _starting_ the semantic versioning at 12.0.0, because 
we'd have to bump major when going to openwire v13 anyway:

OpenWire v12 support
{noformat}
jakarta-jms-3.1.0
activemq-openwire-12.0.0 
{noformat}

OpenWire v13 support
{noformat}
jakarta-jms-3.1.0
activemq-openwire-13.0.0 
{noformat}

vs.

OpenWire v12 support
{noformat}
jakarta-jms-3.1.0
activemq-openwire-1.0.0 
{noformat}

OpenWire v13 support
{noformat}
jakarta-jms-3.1.0
activemq-openwire-2.0.0 
{noformat}

All good, nothing I'm die-hard about. Just thought it made for nice alignment.


was (Author: mattrpav):
Right, I was suggesting starting the semantic versioning at 12.0.0, because 
we'd have to bump major when going to openwire v13 anyway:

OpenWire v12 support
{noformat}
jakarta-jms-3.1.0
activemq-openwire-12.0.0 
{noformat}

OpenWire v13 support
{noformat}
jakarta-jms-3.1.0
activemq-openwire-13.0.0 
{noformat}

vs.

OpenWire v12 support
{noformat}
jakarta-jms-3.1.0
activemq-openwire-1.0.0 
{noformat}

OpenWire v13 support
{noformat}
jakarta-jms-3.1.0
activemq-openwire-2.0.0 
{noformat}

All good, nothing I'm die-hard about. Just thought it made for nice alignment.

> Align OpenWire project major version to protocol major version (12.0.0)
> -----------------------------------------------------------------------
>
>                 Key: OPENWIRE-71
>                 URL: https://issues.apache.org/jira/browse/OPENWIRE-71
>             Project: ActiveMQ OpenWire
>          Issue Type: Improvement
>            Reporter: Matt Pavlovich
>            Assignee: Matt Pavlovich
>            Priority: Major
>
> OpenWire v12 should be served by activemq-openwire-12.0.0.jar



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to