Anyway, I'm still not successful. The extras companion does not want
to compile either. I attached the output. Is it possible that the
junit package is missing?! I can't really believe that, as I guess
that it is used by the other packages' tests, too.
This is bizarre. On the command line, 'mvn clean package' works a
treat. Inside Eclipse, I get magically the same error you have.
I've just committed an import change to the affected class that fixes
the issue for me in Eclipse, but doesn't really explain why it's
working on the command line (I'm using the Maven Eclipse plugin, so it
should be the same..). At any rate, the Assert import that was being
used previously is odd. Try with an 'svn update;mvn install' on the
extras and see if it works now.
After this error, I was adventurous enough to try to build Chainsaw
even without it. Surprisingly, it seems to compile, but afterwards,
the tests
- testKnownReceivers(org.apache.log4j.chainsaw.receivers.
ReceiversHelperTest) and
-
testLogPanelPreferenceModelSerialization(org.apache.log4j.chainsaw.
LogPanelPreferenceModelTest)
fail.
Umm, how exactly did you build/test this? Can you attach the full
'mvn package' output for the Chainsaw project ?
As I'd like to add new receivers, the first error seems to render
the system totally useless for me...
Any ideas?
So, you'd like to be able to add a new Receiver class via the Plugins?
Or are you thinking of contributing a more general Receiver that could
be used by others? At the moment, Chainsaw has it's own hard-coded
registry of 'potential' Receivers that are known, and checks which
ones can be loaded. Ideally we would replace that with the standard
JAR service provider stuff so any custom Receivers could be placed in
the Plugin directory and be dynamically discovered (sounding a lot
like OSGI isn't it. Really starting to think about Chainsaw 3 now.)
cheers,
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
