Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 15426 invoked from network); 26 Dec 2006 19:34:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Dec 2006 19:34:53 -0000 Received: (qmail 40185 invoked by uid 500); 26 Dec 2006 19:34:58 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 39931 invoked by uid 500); 26 Dec 2006 19:34:57 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 39920 invoked by uid 99); 26 Dec 2006 19:34:57 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Dec 2006 11:34:57 -0800 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: error (herse.apache.org: local policy) Received: from [216.86.168.178] (HELO mxout-03.mxes.net) (216.86.168.178) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Dec 2006 11:34:47 -0800 Received: from [192.168.1.104] (unknown [67.86.14.213]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id E24C951927 for ; Tue, 26 Dec 2006 14:34:04 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <3D8E84095C6A524A985B787423094E40912592@mssmsx411> References: <3D8E84095C6A524A985B787423094E40912592@mssmsx411> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <37690B3B-583C-4859-AEA9-26BCC6D5FE58@pobox.com> Content-Transfer-Encoding: 7bit From: "Geir Magnusson Jr." Subject: Re: Issue with Yoko: org.omg.CORBA.INITIALIZE Date: Tue, 26 Dec 2006 14:34:06 -0500 To: dev@harmony.apache.org X-Mailer: Apple Mail (2.752.3) X-Virus-Checked: Checked by ClamAV on apache.org Aren't we going to visit this same problem again at next snapshot? Why not have bootclasspath.42=yoko/yoko-core.jar Do we think it's that important to denote the version of the resource via directory name? geir On Dec 24, 2006, at 5:26 PM, Zakharov, Vasily M wrote: > > > Thanks Tim! That resolved the problem. Without a single JIRA. :) > > Vasily > > > -----Original Message----- > From: Tim Ellison [mailto:t.p.ellison@gmail.com] > Sent: Sunday, December 24, 2006 11:37 PM > To: dev@harmony.apache.org > Subject: Re: Issue with Yoko: org.omg.CORBA.INITIALIZE > > Fixed in r490069. > > Thanks, > Tim > > > Zakharov, Vasily M wrote: >> Tim, >> >> 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! >> >> Vasily >> >> >> -----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 >> in >>> yoko.jar file. In Yoko they are located in core directory and > compiled >> into >>> a separated jar file (you may download it from >>> >> > http://people.apache.org/maven-snapshot-repository/org/apache/yoko/ > yoko- >> core/), >>> 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 :-) >> and >>> 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. >> >> Thanks >> Tim >>