On Thu, 2008-06-05 at 12:10 -0400, Jeff Gehlbach wrote:
> On Jun 5, 2008, at 6:46 AM, Alex Bennee wrote:
> > org.springframework.beans.factory.BeanCreationException: Error
> > creating bean with name 'daemon' defined in class path resource
> > [META-INF/opennms/applicationContext-jettyServer.xml]: Invocation of
> > init method failed; nested exception is java.lang.Error: This
> > version of SLF4J requires log4j version 1.2.12 or later. See also
> > http://www.slf4j.org/codes.html#log4j_version
>
> This looks as if you haven't updated your top-level pom.xml to specify
> log4j version 1.2.15. Verify that pom.xml in the top-level source
> directory is up to date against Subversion. If it is, you should see
> something like this in it:
>
> <dependency>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.2.15</version>
Yes, that was all correct.
> ...
>
> The version is key here. I think we jumped straight from 1.2.9 to
> 1.2.15, not sure when off hand, you could track that down yourself
> using svn log.
FWIW I'm running from a git-svn tree although I can build debs from it
that work so I think it's pretty complete. The pom update was:
commit 328677e2864c706fe07da7ac90a481fe36074a16
Author: brozow <[EMAIL PROTECTED]>
Date: Fri May 16 20:54:10 2008 +0000
Merged revisions 9125-9128 via svnmerge from
https://opennms.svn.sourceforge.net/svnroot/opennms/opennms/branches/1.6-testing
So it's quite likely I could of had stale jar's lying around. I've been
switching back and forth between 1.59.2 and 1.6 while trying to work out
what worked. I assume the 1.6 branch is a sensible one to base a release
product on, this is aiming to be the next stable?
> If your POM is up to date but you're still having problems, try doing
> a ./build.sh clean and cleaning out any old log4j JARs from the
> installed lib directory.
I did some digging after the email and managed to get it further after
dropping odk and going for java6 (which is odd as the debs work, just
not the "local" run, however I did some cleans). I then into a problem
where it wouldn't run on my desktop but the same code would run on the
VM I had created.
For some reason the dhcpd service was failing to bind. After applying:
--- a/opennms-daemon/src/main/filtered/etc/service-configuration.xml
+++ b/opennms-daemon/src/main/filtered/etc/service-configuration.xml
@@ -106,6 +106,8 @@ maintained
<invoke at="stop" pass="0" method="stop"/>
</service>
-->
+<!-- dhcpd seems to break for some reason
+
<service>
<name>OpenNMS:Name=Dhcpd</name>
<class-name>org.opennms.netmgt.dhcpd.jmx.Dhcpd</class-name>
@@ -113,6 +115,7 @@ maintained
<invoke at="status" pass="0" method="status"/>
<invoke at="stop" pass="0" method="stop"/>
</service>
+-->
I'm a little unclear what the dhcpd service is for? The wiki mentions
things about relaying requests but I have to admit I didn't follow. I
don't think I need the functionality anyway AFAICT.
I managed to get a local build which ran and I've made my first working
changes to the jetty web-pages after a crash course on JSP and how it
works :-)
I'll clone the working VM later and put openjdk on it and check the
problems I was seeing before weren't an aberration caused by the java I
was using.
At some point I'm sure this will all start to gel and I can stop asking
newbie Java questions on the list :-)
--
Alex Bennee, Software Engineer
We question most of the mantras around here periodically, in case you
hadn't noticed. :-) -- Larry Wall in <[EMAIL PROTECTED]>
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-devel mailing list
To *unsubscribe* or change your subscription options, see the bottom of this
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel
