[
https://issues.apache.org/jira/browse/CAMEL-8215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268959#comment-14268959
]
Daniel Pocock edited comment on CAMEL-8215 at 1/8/15 8:26 AM:
--------------------------------------------------------------
I've changed the title of this issue to refer explicitly to v2.1.1. We can
track v2.2.x as a separate JIRA issue.
I feel that this change, using 2.1.1, should be backported to Camel 2.14 and
2.13.
The jSMPP 2.1.x branch will only be used for minor bug fixes, security fixes,
etc. There won't be any API breaking changes in the 2.1.x branch.
The jSMPP 2.2.x release should probably not be backported to Camel 2.14 or
earlier and maybe it won't even be ready for 2.15.
was (Author: daniel.pocock):
I've changed the title of this issue to refer explicitly to v2.1.1. We can
track v2.2.x as a separate JIRA issue.
I feel that this change, using 2.1.1, should be backported to Camel 2.14 and
2.13.
The jSMPP 2.1.x branch will only be used for minor bug fixes, security fixes,
etc. There won't be any API breaking changes in the 2.1.x branch.
The jSMPP 2.2.x release should not be backported to Camel 2.14 or earlier and
maybe it won't even be ready for 2.15.
> camel-smpp - use jsmpp version 2.1.1 / new groupId
> --------------------------------------------------
>
> Key: CAMEL-8215
> URL: https://issues.apache.org/jira/browse/CAMEL-8215
> Project: Camel
> Issue Type: Bug
> Components: camel-smpp
> Environment: n/a
> Reporter: Daniel Pocock
> Assignee: Willem Jiang
>
> A new jSMPP version is available
> It is released under a new groupId org.jsmpp
> Some of the ServiceMix enhancements are included and it is also released as a
> bundle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
