harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Hindess (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HARMONY-789) logging.properties is missing in VM build
Date Fri, 07 Jul 2006 14:17:30 GMT
     [ http://issues.apache.org/jira/browse/HARMONY-789?page=all ]
     
Mark Hindess resolved HARMONY-789:
----------------------------------

    Resolution: Fixed

Applied in r419895.  Please check it is as expected.


> logging.properties is missing in VM build
> -----------------------------------------
>
>          Key: HARMONY-789
>          URL: http://issues.apache.org/jira/browse/HARMONY-789
>      Project: Harmony
>         Type: Bug

>   Components: VM
>  Environment: Windows XP
>     Reporter: Anton Luht
>     Assignee: Mark Hindess
>     Priority: Minor

>
> I've built VM and  classlib revision 419539
> Trying to run a simple test with logging:
> import java.util.logging.Level;
> import java.util.logging.Logger;
> public class Test {
>   public static void main(String[] args) {
>     Logger log = Logger.getAnonymousLogger();
>     log.setLevel(Level.INFO);
>     log.info("hello world");
>   }
> }
> I've got the error:
> prompt> <vm distr root>\build\win_ia32_msvc_debug\deploy\jre\bin\ij.exe Test
> java.io.FileNotFoundException
>         at org.apache.harmony.luni.platform.OSFileSystem.open(OSFileSystem.java:
> 223)
>         at java.io.FileInputStream.<init>(FileInputStream.java:66)
>         at java.io.FileInputStream.<init>(FileInputStream.java:110)
>         at java.util.logging.LogManager.readConfigurationImpl(LogManager.java:45
> 0)
>         at java.util.logging.LogManager.<clinit>(LogManager.java:186)
>         at java.util.logging.Logger.getLoggerWithRes(Logger.java:362)
>         at java.util.logging.Logger.getLogger(Logger.java:389)
>         at java.util.logging.Logger.<clinit>(Logger.java:99)
>         at Test.main(Test.java:6)
> The problem was that logging.properties file was not copied from classlib. The following
patch to VM build solves the problem:
> Index: build.xml
> ===================================================================
> --- build.xml   (revision 419539)
> +++ build.xml   (working copy)
> @@ -445,6 +445,12 @@
>              </fileset>
>          </copy>
> +        <copy todir="${build.deploy.dir}/lib">
> +            <fileset dir="${external.dep.CLASSLIB}/deploy/jdk/jre/lib">
> +                <include name="logging.properties"/>
> +            </fileset>
> +        </copy>
> +
>      </target>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message