Update: With the no tests parameter for each one, I can build both the
extras companion and Chainsaw itself, but a Chainsaw run attempt later
on just gives me:
Exception in thread main java.lang.Error: Unresolved compilation problems:
LogManager cannot be resolved
Author: psmith
Date: Thu Jun 26 15:27:04 2008
New Revision: 672042
URL: http://svn.apache.org/viewvc?rev=672042view=rev
Log:
Replace Assert import with standard package. Really not sure why this is not
required
on the maven command line, but Eclipse refuses to find it for some reason.
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
Paul Smith wrote:
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
https://issues.apache.org/bugzilla/show_bug.cgi?id=45274
Jacob Kjome [EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
https://issues.apache.org/bugzilla/show_bug.cgi?id=45274
--- Comment #2 from Ralph Goers [EMAIL PROTECTED] 2008-06-26 21:26:22 PST ---
writing to a file from two JVMs is indeed supported by Java. The problem is
that in order to do so the file must be locked while the writes are taking
place.
[
https://issues.apache.org/jira/browse/LOG4J2-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12608651#action_12608651
]
Ralph Goers commented on LOG4J2-4:
--
File locking should be a configurable option to allow
