harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zakharov, Vasily M" <vasily.m.zakha...@intel.com>
Subject RE: Issue with Yoko: org.omg.CORBA.INITIALIZE
Date Sun, 24 Dec 2006 01:27:53 GMT

Thanks alot for the quick change! But there's a small problem with the
configuration - bootclasspath.properties file you've just fixed expects
yoko-core.jar to be in lib/boot/yoko_M1-20061027 directory, while in
fact it resides in lib/boot/yoko_M2-20061115 directory. Could you please
fix that somehow? Thanks!

I've tried to correct that manually in the ready build, it resolves the
initial problem.

Thank you!


-----Original Message-----
From: Tim Ellison [mailto:t.p.ellison@gmail.com] 
Sent: Sunday, December 24, 2006 1:11 AM
To: dev@harmony.apache.org
Subject: Re: Issue with Yoko: org.omg.CORBA.INITIALIZE

Mikhail Markov wrote:
> Vasily,
> I've investigated the problem a bit and found that
> org.omg.CORBA.ORB.init();
> call fails because there are no org.apache.yoko.orb.* classes at all
> yoko.jar file. In Yoko they are located in core directory and compiled
> a separated jar file (you may download it from
> which is not downloaded during Harmony building.
> So, the solution for this problem is simple: just download
> yoko-core.jarfrom the url above, put it to the jdk/jre/lib/boot and
> modify
> bootclasspath.properties, but there is another important question:
> Do we download yoko jars only for compilation purposes?
> I suppose we want to have working CORBA implemenation in Harmony :-)
> without yoko-core.jar, i think Yoko will not work.
> So, i suggest modifying the building process to download yoko-core.jar
> along
> with other yoko jars and put it to boot directory.
> What do you thinks?

Agreed -- I've fixed the dependencies in repository revision r489931.


View raw message