gump failing on components

from:

http://brutus.apache.org/gump/public/smartfrog/smartfrog-components/gump_work/build_smartfrog_smartfrog-components.html

Looks like changes to log4j have broken us:

compile:
  [sf-javac] Compiling 2 source files to 
/home/gump/workspaces2/public/workspace/smartfrog/components/sfcoreloggers/build/classes
  [sf-javac] 
/home/gump/workspaces2/public/workspace/smartfrog/components/sfcoreloggers/src/org/smartfrog/sfcore/logging/logger/LogToLog4JImpl.java:184: 
configure(java.lang.String) in org.apache.log4j.xml.DOMConfigurator 
cannot be applied to (java.net.URL)
  [sf-javac] 
org.apache.log4j.xml.DOMConfigurator.configure((java.net.
  [sf-javac]                                                       ^
  [sf-javac] 
/home/gump/workspaces2/public/workspace/smartfrog/components/sfcoreloggers/src/org/smartfrog/sfcore/logging/logger/LogToLog4JImpl.java:215: 
cannot resolve symbol
  [sf-javac] symbol  : method configureAndWatch (java.lang.String,long)
  [sf-javac] location: class org.apache.log4j.xml.DOMConfigurator
  [sf-javac] 
org.apache.log4j.xml.DOMConfigurator.configureAndWatch((String) 
configuratorURL, configureAndWatchDelay);
  [sf-javac]                                                           ^
  [sf-javac] 
/home/gump/workspaces2/public/workspace/smartfrog/components/sfcoreloggers/src/org/smartfrog/sfcore/logging/logger/LogToLog4JImpl.java:229: 
cannot resolve symbol
  [sf-javac] symbol  : method configureAndWatch (java.lang.String,long)
  [sf-javac] location: class org.apache.log4j.PropertyConfigurator
  [sf-javac] 
org.apache.log4j.PropertyConfigurator.configureAndWatch((String) 
configuratorURL, configureAndWatchDelay);
  [sf-javac]                                                            ^
  [sf-javac] 3 errors
  [sf-javac] 3 warnings

On an unrelated note, see all those warning messages from rmic about 
verification failure? That only appears on Gump, and makes me wonder 
about whether the magic gump does with classpaths is breaking RMIC. If 
we set verify=false then verification is turned off, but we also need to 
worry about those build files that just tell <rmi> to work out for 
itself which classes are remotable. Maybe we need to list them all 
explicitly.


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt