On Dec 8, 2008, at 3:02 PM, Damian Krzeminski wrote: > 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. >> >> -Mardy >> > > This probably went a bit too far. I understand (although I do not > agree > with it) that you wanted to remove the need to package our own RPMs > (jain-sip, dnsjava etc.) but I do not think that sipXconfig should > be using > our own versions of Ant or Log4j which are nicely packaged and > available on > all the platforms that we need them for. >
Relying on platform supplied Ant and Log4j appears on the surface to be benign. But in reality these packages have very extensive dependency chains which translates to a total of 29 required RPM's (on CentOS 5). Given that, I chose instead to bring back the three required jar files, one of which was already supplied by sipXcommons. > The one error that I see now is: > > /home/cruisecontrol/work/projects/ecs/main/sipXconfig/neoconf/ > build.xml:255: > org.apache.commons.logging.LogConfigurationException: > org.apache.commons.logging.LogConfigurationException: No suitable Log > constructor [Ljava.lang.Class;@cfec48 for > org.apache.commons.logging.impl.Log4JLogger (Caused by > java.lang.NoClassDefFoundError: org/apache/log4j/Priority) (Caused by > org.apache.commons.logging.LogConfigurationException: No suitable Log > constructor [Ljava.lang.Class;@cfec48 for > org.apache.commons.logging.impl.Log4JLogger (Caused by > java.lang.NoClassDefFoundError: org/apache/log4j/Priority)) > > > If I remember correctly this one is triggered by adding log4j as a > build-time dependency (it should be run-time dependency only) - I > think > Kevin fixed it recently. Yes, the problem is with the pre-compilation of the jasper reports. What has thrown me is that I have not been able to reproduce the problem. I will try moving log4j out of the build-time dependency list and into the run-time dependency list. -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
