----- Original Message -----
From: "Leo Simons" <[EMAIL PROTECTED]>
> yep. It's been a TODO for ages. ie:
:-(
> the tools are used for running the container tests IIRC. A workaround is
> to comment out the dependency on tools in the container project.xml file
> (as above), build it and install it into your local repo. Disable the
> tests. IOW,
Wow!
I made the Container depends on fortress-tools in the ibiblio. Not better
that your solution, though.
Anyway, Container compilations works fine, but tools fails miserably with
avalon:custom-compile:
[echo] Compiling to D:\temp\fortress\tools/target/classes
[javac] Compiling 5 source files to
D:\temp\fortress\tools\target\classes
D:\temp\fortress\tools\src\java\org\apache\avalon\fortress\tools\FortressBea
n.java:71: cannot resolve symbol
symbol : class AvalonLogger
location: package impl
import org.apache.commons.logging.impl.AvalonLogger;
^
D:\temp\fortress\tools\src\java\org\apache\avalon\fortress\tools\FortressBea
n.java:123: cannot resolve symbol
symbol : variable AvalonLogger
location: class org.apache.avalon.fortress.tools.FortressBean
AvalonLogger.setDefaultLogger(cm.getLogger());
^
2 errors
BUILD FAILED
Seems that the current commons-logging implementation is different from what
Fortress-Tools expected. Any clues?
regards,
hammett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
