>>
>> More, we would also need the changes for CAMEL-6116. If possible, please
>> ensure these changes to be in 2.11.0 .
>>
>> Thanks,
>> Anurag.
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/camel-smpp-optional-param-issue-tp5728376p5728673.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>
--
; value
> of which should be OptionalParam(jsmpp object) .
>
> More, we would also need the changes for CAMEL-6116. If possible, please
> ensure these changes to be in 2.11.0 .
>
> Thanks,
> Anurag.
>
>
>
>
>
> --
> View this message in context:
changes to be in 2.11.0 .
Thanks,
Anurag.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-smpp-optional-param-issue-tp5728376p5728673.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ikely to get
accepted and included in the code faster.
And we prefer to have unit tests go with patches to test new
functionality / changes etc.
http://camel.apache.org/contributing.html
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/came
to this
> project and need to plan ahead.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/camel-smpp-optional-param-issue-tp5728376p5728591.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
@Christian is there an ETA to this. How long are your release cycles
typically ? We unfortunately have a reasonably aggressive timeline to this
project and need to plan ahead.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-smpp-optional-param-issue-tp5728376p5728591
gt;
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/camel-smpp-optional-param-issue-tp5728376.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
t.
Thanks,
Anurag.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-smpp-optional-param-issue-tp5728376.html
Sent from the Camel - Users mailing list archive at Nabble.com.
