[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ozone 0.4-dev5



On Wed, 22 Mar 2000, you wrote:
> >
> >*** ozone version 0.4-dev5 available ***
> >
> >It includes the new ClassLoader that depends on JDK1.2. You can just use
> the
> >ClassManager.java from the 0.4-dev4 distribution to make it work with
> JDK1.1.
> 
> 
> I had to make some changes to get ozone0.4.5 working with jdk1.1.8.
> The first thing was very strange:
> in Makefile.env the .jar's and class-directories from ozone are added to the
> CLASSPATH.
> All Makefiles read Makefile.env, thus while making "make" all
> jars get added to the CLASSPATH several times. There seems to be
> a limit on the length of environment variables (at least on FreeBSD).
Fixed.

> and I changed $(JAVAC) to javac. ( in ozone/INSTALL you say the default is
> javac)
I'll try to change it to javac before each release.

> 
> the second change:
> my javac said:
>        javac -g AbstractTest.java CollectionTest.java DiskHashTest.java
> MapTest.java SetTest.java Test.java
>        SetTest.java:29: Reference to equals is ambiguous. It is defined in
> boolean equals(java.lang.Object)
>        and boolean equals(java.lang.Object).
>        if (!set.equals (set2) && set.count()>0)
> 
> equals is defined in java.lang.Object (all objects inherit from it)
> org.ozone.DxLib.DxCompatible
> I commented equals() int DxCompatible. And it compiled without error. (The
> same problem
> could be with clone())
Don't try to compile the DxLib tests.

> 
> third change:
>  I took the old ClassManager.java because I am using jdk1.1.8 ,
>   but some other Objects need the new flushCache(),
> I glanced at the could and added an empty function (is this save?)
>     public void flushCache() throws Exception {
>     }
Next release will have 1.1 compliant ClassLoader again until Ted comes up with
a real working solution for jdk1.2.

> 
> fourth change:
>       the openxml.jar was not included. I took the one from 0.4.4
Should compile and run without. Did I miss something? Where is it needed?

> 
> while compiling opp produced the following warnings
> very often (unable to open ...):
> 
> javac -g util/BLOBContainer.java util/BLOBContainerImpl.java
> util/BLOBInputStream.java util/BLOBOutputStream.java util/BLOBPage.java
> util/BLOBPageImpl.java
> cd util; opp org.ozoneDB.util.BLOBContainerImpl
> org.ozoneDB.util.BLOBPageImpl
> org.ozoneDB.util.BLOBContainerImpl:
>    update methods:
>       (processing BLOBContainer.java...)
> BLOBContainerImpl.ocd:0: warning: Unable to open descriptor file.
>       init ("int")
>       write ("int|[B|int|int")
> compiler: javac
> 
> I had no time to see what was wrong with this.
It's just a warning... I deleted this message to avoid confusion.


Falko
-- 
______________________________________________________________________
Falko Braeutigam                         mailto:falko@softwarebuero.de
softwarebuero m&b (SMB)                    http://www.softwarebuero.de