On Thu, Aug 28, 2008 at 7:37 AM, Marden Marshall <[EMAIL PROTECTED]> wrote: > > On Aug 27, 2008, at 10:56 AM, M. Ranganathan wrote: > >> Hi, >> >> I am trying to update the version of jain-sip in sipXcommons and >> observe that I need to update versions in all the config.properties.in >> in all build directories where the file is referenced. It would have >> been easier to create a symbolic link for the jar file and hence avoid >> this. Any reason why we cannot do that? >> >> Ranga >> >> -- M. Ranganathan >> _______________________________________________ > > A common config.properties.in is not used as different projects can have the > option of calling out jar files which are either not supplied by sipxcommons > or are at a different version than the ones supplied by sipxcommons. > > One solution to the problem which you bring up is for sipxcommons to include > unversioned jar files which are merely links to the actual versioned jar > files. For example: > > jain-sip-sdp.jar -> jain-sip-sdp-1.2.79.jar > > Then if a project only cares about using the latest version of jain-sip-sdp > supplied by sipxcommons, it's config.properties.in can would just specify > "jain-sip-sdp.jar". Moving forward, changes related to updates of that jar > file would be contained to the sipxcommons project. > > -Mardy >
I agree that this would be a viable solution. Ranga > > > -- 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
