On 07/01/15 16:47, Daniel Pocock wrote:
> On 07/01/15 10:18, Daniel Pocock wrote:
>> On 07/01/15 03:19, Willem Jiang wrote:
>>> I just send a PR by applying the patch of creating OSGi bundle for jSMPP.
>>> Now Camel can consume the new jSMPP bundle from the Official release :)
>>
>> I've just rel
On 07/01/15 10:18, Daniel Pocock wrote:
> On 07/01/15 03:19, Willem Jiang wrote:
>> I just send a PR by applying the patch of creating OSGi bundle for jSMPP.
>> Now Camel can consume the new jSMPP bundle from the Official release :)
>
> I've just released jSMPP 2.2.1 with that change, please let me
On 07/01/15 03:19, Willem Jiang wrote:
> I just send a PR by applying the patch of creating OSGi bundle for jSMPP.
> Now Camel can consume the new jSMPP bundle from the Official release :)
I've just released jSMPP 2.2.1 with that change, please let me know if
it looks correct, it has been release
I just send a PR by applying the patch of creating OSGi bundle for jSMPP.
Now Camel can consume the new jSMPP bundle from the Official release :)
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: will
On 06/01/15 22:01, Christian Müller wrote:
> It would be good, if you could release JSMPP as an OSGI bundle. It's only a
> few more lines in the pom.xml file...
Could you possibly propose a pull request for it or refer me to an
example of how to do this in a way that is satisfactory for Camel?
It would be good, if you could release JSMPP as an OSGI bundle. It's only a
few more lines in the pom.xml file...
I'm wondering whether you should use a different Maven group id to
differentiate for the original JSMPP library.
Best,
Christian
-
Software Integration Specialist
A
