The Apache Jenkins build system has built Camel.2.14.x.notest (build #80)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.2.14.x.notest/80/
to view the results.
GitHub user lamperi opened a pull request:
https://github.com/apache/camel/pull/371
CAMEL-8217: Fix typeHints option for camel-xmljson
Fixed camel-core model to set the option on the data format. Changed the
behaviour of YES and WITH_PREFIX to reflect documentation and naming.
Y
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
GitHub user dpocock opened a pull request:
https://github.com/apache/camel/pull/370
camel-smpp: CAMEL-8215: update to org.jsmpp / jsmpp v2.1.1
This uses 2.1.1 instead of jumping up to 2.2.0
You can merge this pull request into a Git repository by running:
$ git pull https://git
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
GitHub user dpocock opened a pull request:
https://github.com/apache/camel/pull/369
Begin conversion to jsmpp v2.2.1
This is for CAMEL-8215 - it builds but some unit tests fail
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dpoco
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
