On Dec 8, 2008, at 1:36 PM, Kevin Thorley wrote: > > On Mon, 2008-12-08 at 13:16 -0500, Marden Marshall wrote: >> sipXconfig now utilizes sipXcommons to resolve common third-party JAR >> files as other sipX java services do. For developers, this means >> that >> it is now necessary to first build and install the sipXcommons >> component before building and/or testing sipXconfig. For Eclipse >> users, in addition to setting the "SIPX_CONFIG" classpath variable to >> the location of the sipXconfig source directory, it is now necessary >> to define "SIPX_COMMONS" to the location of the sipXcommons source >> directory. >> > > sipXconfig previously dealt with jars in two different ways. True > third-party jars that are used as-is were checked into the sipxconfig > lib dir and referenced from both the ant scripts and from Eclipse > classpath file. Jars that were custom-built for sipXconfig, such as > jain-sip and more recently sipx-jasperreports-deps are referenced > via a > CHECK_JAR macro in the config/java.m4 file. Do the new changes that > you > are referring to take into account both of these types of > dependencies? >
Yes. sipx-jasperreports-deps is still located via autoconf. Jain- sip, on the other hand, is supplied by sipXcommons. You can see quickly which packages are being supplied by sipXcommons by querying the "lib.properties" file. -Mardy _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
