On Sun, Oct 2, 2011 at 2:17 AM, George Niculae <[email protected]> wrote: > On Sat, Oct 1, 2011 at 3:10 PM, Douglas Hubler <[email protected]> wrote: >> 1.) I moved some non-essential packages to "app" category. To build them >> run >> >> make app >> >> To list what they are, use run "make" and you should see the list >> >> 2.) Few days back, I created sipxconfig-web.jar and now some projects >> like sipXopenfire are were attempting to find classes from neoconf in >> the web jar. Only sane fix was to rename sipxconfig.jar to >> sipxconfig-neoconf.jar and that's a little harder to track down the >> fixes. I did a fresh build of sipx and looks ok, but i may have >> missed something. >> > > Thanks for heads up, this is working very good. There are 2 minor > issues I noticed: > - cmcprov.war build from sipXcounterpath is not correctly generated - > it is created as a directory rather than an archive. Also, the > cmcprov.war is referenced in sipXconfig-jetty.xml , so if you don't > run make app sipXconfig will fail to load it and complain in logs (not > sure if this is a real problem though as it is supposed to be fixed > after make app) > - I installed without app categories and only polycoms were shown in > phones page, then after running make app all phones supported were > displayed - which is good. However, gateways are not picked up even > after make app - there are only Acme, unmanaged and SIP trunk >
One more thing, make app fails at sipXcustomCallerId with aclocal: configure.ac:5: file `config/general.m4' does not exist autoreconf: aclocal failed with exit status: 1 make[1]: *** [sipXcustomCallerId.autoreconf] Error 1 make[1]: Leaving directory `/home/george/release-4.6/BUILD' make: *** [app] Error 2 George _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
