On Wed, May 14, 2008 at 3:31 PM, Damian Krzeminski <[EMAIL PROTECTED]> wrote: > I am working on integrating real SIP stack with sipXconfig. > > I would like to package jain-sip as 3rd party dependency so that it can > be used by all interested projects without checking the jars into > respective lib directories. > > I was thinking I will try to build java package compliant RPM from it. > Initially I would build it as a part of our dependency build, but if it > turns out OK I could submit it to the javapackage (it should not be very > difficult since it does not have many dependencies). > > Is the version we sipx using an official jain-sip release (does it > correspond to something that is tagged as such in CVS repo)?
I think version being used in some of the sipx projects is dated. As I am the official in charge of JSIP releases :-) we can call it "official" at any time. The official release tends to move each time there is a bug so tagging is a good idea. > > When I build jain-sip I end up with 4 jars: > > jain-sip-api-1.2.jar > jain-sip-ri-1.2.jar > nist-sdp-1.0.jar > sip-sdp-1.2.jar oh I should rename the last and call it jain-sip-sdp-1.2.jar > > However sipxbridge is using only one: > > jain-sip-sdp-1.2.jar Naturally :-) I prefer a single jar for everything. We never use sip without sdp and we use only one implementation of the standard so putting everything in one jar is sensible. > > preflight is using: > > jain-sip-api-1.2.jar > jain-sip-ri-1.2.92.jar > > > sipxpark is using > > jain-sip-api-1.2.jar > jain-sip-ri-1.2.92.jar > sip-sdp-1.0.jar > > And it looks like despite of the same names those files are actually > different. > > What is the version and set of jars we should standardize on? I would like to pick a time ( now -- assuming we agree ) and tag the repository. As of now JSIP is pretty stable and has all the features I need. Incidentally, as I built sipxbridge, I have also added a few small extensions to jain-sip which were motivated by my needs. We should, as a matter of discipline, try to not use the implementation objects. I have extension interfaces for all the extensions I added. The extensions are all called things like SipProviderExt, SipStackExt etc. We (I) will do a quick sweep through the jsip projects of sipx and pick up all users of implementation objects. They authors of such code will be fined :-) and I will incorporate those changes into the specification if needed. We should only be using the specification and the extension interfaces to build stuff. Ranga > D. > > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
