camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <christian.muel...@gmail.com>
Subject Re: updating the jSMPP dependency
Date Tue, 06 Jan 2015 21:01:18 GMT
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

Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member

https://www.linkedin.com/pub/christian-mueller/11/551/642

On Tue, Jan 6, 2015 at 5:18 PM, Daniel Pocock <daniel@pocock.pro> wrote:

>
> I've been creating a 2.2.0 release of jSMPP with various bug fixes that
> had been left in github pull requests
>
> What is the procedure to use this in Camel?
>
> I notice the camel-smpp/pom.xml uses an OSGi-bundle build of jSMPP:
>
>         <dependency>
>             <groupId>org.apache.servicemix.bundles</groupId>
>             <artifactId>org.apache.servicemix.bundles.jsmpp</artifactId>
>             <version>${jsmpp-version}</version>
>         </dependency>
>
> and it appears to have been created about 4 years ago by Jean-Baptiste:
>
>
> http://svn.apache.org/viewvc/servicemix/smx4/bundles/tags/org.apache.servicemix.bundles.jsmpp-2.1.0_2/
>
>
> and published under a different group ID:
>
>
> http://mvnrepository.com/artifact/org.apache.servicemix.bundles/org.apache.servicemix.bundles.jsmpp/2.1.0_2
>
> Should the bundle stuff be merged into the proper jSMPP JAR or is it
> necessary to continue building a separate JAR like that for OSGi?
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message