Hi Damian, Comments below.
On Fri, May 16, 2008 at 1:11 PM, Damian Krzeminski <[EMAIL PROTECTED]> wrote: > M. Ranganathan wrote: >> On Wed, May 14, 2008 at 3:31 PM, Damian Krzeminski >> <[EMAIL PROTECTED]> wrote: > [...] >>> >>> 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. >> > > For now I ended up creating a tarball and putting it here (thanks Scott!): > > http://sipxecs.sipfoundry.org/temp/sipXecs/jain-sip-1.2.tar.gz Can we make a tag and then tarball it with the name of that tag? > > I'll gladly switch to whatever is considered an official release. At this point there is no such thing. Only the API ( java.sip* ) have an official release. The RI is a changing thing. It changes each time a bug is fixed. I have a volunteer who is adding a "release number" file to that repository. This will be updated on each "offical" build and build artifacts will be uploaded to the mvn2 repository on java.net. An svn repository is the way to go. Where shall we put it ( here or java.net ? ). If we > are to have any hope of this RPM being accepted by jpackage and/or > Fedora there has to be a source-only tarball available for download > without any click-through (see: http://jpackage.org/jpprequest.php). > > I did not find anything like that on https://jain-sip.dev.java.net, > please let me know if I missed something. http://download.java.net/communications/jain-sip/nightly/ has snapshots but I see a src.tar.gz does not exist. I can add that. > >> >>> 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. >> > > I suspect sipXconfig might end up not using SDP jar. And I think it's as > easy to use one jar as many jars, but it's up to you. The problem with multiple jars is that common classes are repeated ( unless we want to create yet another jar with just a few class files in it ). As such sdp is pretty small so lugging it in a jain-sip-sdp.jar it is not too bad > > For now the RPM will install the following: > > [EMAIL PROTECTED] lib]$ ls -l /usr/share/java/jain-sip > total 1.2M > jain-sip-api-1.2.jar > jain-sip-api.jar -> jain-sip-api-1.2.jar > jain-sip-ri-1.2.jar > jain-sip-ri.jar -> jain-sip-ri-1.2.jar > sip-sdp-1.2.jar > sip-sdp.jar -> sip-sdp-1.2.jar > > And javadoc is installed by jain-sip-javadoc here: > > /usr/share/javadoc/jain-sip-1.2/ri (copied from javadoc) > /usr/share/javadoc/jain-sip-1.2/jain (copied from javadoc-jain) > > If you'd rather see it packaged in a different way, please let me know. > > You can build this RPM by running: > > make jain-sip > > In sipXecs/lib directory. > I did not add it to any distro dependency yet (I want to make sure > sipXconfig can use it first). Feedback from RPM gurus also highly > apreciated. > > [...] >>> >>> 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. >> > > I am obviously OK with now ;-) I am threatening to tag it then.... :-) Will clean up any minor issues on that issue list on jSIP, tag it and post to the list when it is tagged. > > [...] > > I'll be posting more info on how to actually use sip-jain when it's > packaged. > > As a reminder, the goal is not to have various jars checked in into lib > directories of sipXecs repo. sipXbridge has a bunch of jars that other components use. There is nothing specific about jain-sip > jar. Other java libraries that are commonly available in packages > version will get similar treatment. > 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
