[
https://issues.apache.org/jira/browse/UIMA-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494382
]
Marshall Schor commented on UIMA-397:
-------------------------------------
I can verify it now passes the tests. But I don't understand the intricacies
of logging to say if this is a good test or not - I'll leave that to others :-)
> JSR47Logger_implTest failing with Sun Java 6
> --------------------------------------------
>
> Key: UIMA-397
> URL: https://issues.apache.org/jira/browse/UIMA-397
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Affects Versions: 2.1
> Environment: Java 6 or 6_01
> Reporter: Marshall Schor
> Assigned To: Marshall Schor
> Priority: Minor
> Fix For: 2.2
>
>
> If you run the maven install using these java versions, then the default
> logger created has this property, as evidenced from this print statement you
> can insert in the code:
> System.out.println("defaultLogLevel: " + defaultLogLevel);
> System.out.println("rootLogger is set to log messages: " +
> ( rootLogger.isLoggable(Level.ALL) ? "ALL, " : "NotALL, ") +
> ( rootLogger.isLoggable(Level.FINEST) ? "FINEST, " : "NotFINEST,
> ") +
> ( rootLogger.isLoggable(Level.FINER) ? "FINER, " : "NotFINER, ")
> +
> ( rootLogger.isLoggable(Level.FINE) ? "FINE, " : "NotFINE, ") +
> ( rootLogger.isLoggable(Level.CONFIG) ? "CONFIG, " : "NotCONFIG,
> ") +
> ( rootLogger.isLoggable(Level.INFO) ? "INFO, " : "NotINFO, ") +
> ( rootLogger.isLoggable(Level.WARNING) ? "WARNING, " :
> "NotWARNING, ") +
> ( rootLogger.isLoggable(Level.SEVERE) ? "SEVERE, " : "NotSEVERE,
> ") +
> ( rootLogger.isLoggable(Level.OFF) ? "OFF, " : "NotOFF, "));
> Message produced is:
> rootLogger is set to log messages: NotALL, NotFINEST, NotFINER, FINE, CONFIG,
> INFO, WARNING, SEVERE, OFF,
> For IBM Java 5 message produced is:
> rootLogger is set to log messages: NotALL, NotFINEST, NotFINER, NotFINE,
> NotCONFIG, INFO, WARNING, SEVERE, OFF,
> WARNING It is somewhat hard to run maven with a particular level. The
> mvn.bat file (on windows) says to set %JAVA_HOME% to control this but that
> doesn't work. You can tell by setting a very siimple PATH pointing only to
> the mvn bin dir. The testcases will then fail with a message saying it
> couldn't find java (because it's not using %JAVA_HOME%). I worked around
> this by putting in the maven bin dir a java.bat file which had just the line:
> %JAVA_HOME%\bin\java.exe %1 %2 %3 %4 %5 %6 %7 %8 %9
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
