On Thu, Mar 08, 2007 at 12:02:50PM -0600, Bob Black wrote:
> Does anyone have a logging.properties file that works with jamvm
> (+ classpath)?
jamvm uses classpath's java.util.logging. I don't think it would require
any special content.
Here is an example:
== logging.properties ========================================================
handlers = java.util.logging.ConsoleHandler
.level = WARNING
==============================================================================
Maybe that bug was solved in another package (classpath?) or in a new
upload.
Otherwise, I either can't reproduce this bug or don't understand the
problem described in this bug: Is it that jamvm doesn't work, or just that
the java.util.logging package cannot be configured?
By default, GNU classpath looks in /usr/lib for the logging.properties
file (/usr/lib is the default value for gnu.classpath.home.url).
The logging.properties can also be specified with the
java.util.logging.config.file property:
java -Djava.util.logging.config.file=<path to logging.properties> ..
When there is no system wide logging.properties file, GNU classpath uses
default values (only >= INFO messages are displayed on console).
This default looks good to me, and also it seems sane to require users (or
applications) to set java.util.logging.config.file if they want special
logging properties.
At one time, I've been able to have a strange behavior (the VM silently
quit, no Exception) with a given logging.properties file. But I can't
reproduce it currently (and I can't remember what was in this
logging.properties).
> Any ideas? Has anyone gotten jamvm working with an app that uses
> java.util.logging?
Yes, with the following app:
== Test.java =================================================================
import java.util.logging.*;
public class Test{
private static Logger logger = Logger.getLogger("Test");
public static void main(String argv[]){
logger.fine("FINE log");
logger.log(Level.WARNING,"WARNING log");
logger.info("INFO log");
logger.log(Level.SEVERE,"SEVERE log");
}
}
==============================================================================
I compiled it with javac from jikes-sablevm (1.13-1.1).
I run it with jamvm (1.4.4-2); classpath (0.92-4). (I tried both running
it from a JAR and a .class file.)
3 persons could reproduce it (with real applications, not just this test).
So there could be an issue elsewhere.
Michel, Matthew, Bob, can you confirm that this bug still exists?
Can you try the above example? And if it works, can you also provide an
application which fails?
Your classpath's version could also be interesting.
Kind Regards,
--
Nekral
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
