Return-Path: Delivered-To: apmail-incubator-harmony-dev-archive@www.apache.org Received: (qmail 92313 invoked from network); 13 Nov 2006 21:31:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Nov 2006 21:31:02 -0000 Received: (qmail 57768 invoked by uid 500); 13 Nov 2006 21:31:10 -0000 Delivered-To: apmail-incubator-harmony-dev-archive@incubator.apache.org Received: (qmail 57450 invoked by uid 500); 13 Nov 2006 21:31:09 -0000 Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: harmony-dev@incubator.apache.org Delivered-To: mailing list harmony-dev@incubator.apache.org Received: (qmail 57441 invoked by uid 99); 13 Nov 2006 21:31:09 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Nov 2006 13:31:09 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of ilya.neverov@gmail.com designates 66.249.82.238 as permitted sender) Received: from [66.249.82.238] (HELO wx-out-0506.google.com) (66.249.82.238) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Nov 2006 13:30:56 -0800 Received: by wx-out-0506.google.com with SMTP id h29so1415209wxd for ; Mon, 13 Nov 2006 13:30:35 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jrIbcd5ueIL3AlaCNx3kF+2WQqZqAByAVoFYM3iMYMz9+eBsg59EXNoFvuYnG8LLIeiRjcMvkmygNAtacknja3rP6uWmaqpcK/rEcYSi+d6Nps194l5nd1Hfww6j6p810Y8PuK0zpcBB9SrKbvHoJI2FPAa/Yr2TzA+GWV/KGvg= Received: by 10.90.105.19 with SMTP id d19mr136931agc.1163453435253; Mon, 13 Nov 2006 13:30:35 -0800 (PST) Received: by 10.90.96.5 with HTTP; Mon, 13 Nov 2006 13:30:30 -0800 (PST) Message-ID: <4ed33be10611131330m1320a5dfwfd5d004b35f282a8@mail.gmail.com> Date: Tue, 14 Nov 2006 03:30:30 +0600 From: "Ilya Neverov" To: harmony-dev@incubator.apache.org, geir@pobox.com Subject: Re: [general] creation of "jdktools" In-Reply-To: <4557B1C6.1000806@pobox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <452129AB.6040407@pobox.com> <452174E1.8040907@pobox.com> <4522B3C0.7070109@gmail.com> <4522BE88.4070307@pobox.com> <4ed33be10610191051x5afe1324x3ba0af79f7fc2c73@mail.gmail.com> <4ed33be10610300955o2a5f52a3x8b2a53c1bbe8eca8@mail.gmail.com> <45468D12.5080004@pobox.com> <4ed33be10611110819s21030462x84f3a9ac142362f9@mail.gmail.com> <4557B1C6.1000806@pobox.com> X-Virus-Checked: Checked by ClamAV on apache.org Nathan, thank you for creation of the trunk/working_jdktools. Geir, Please look at comment and scripts attached to the HARMONY-2180. I tried to make them trivial so that reviewing doesn't take much time. Proposed build system has two levels of enrties: - working_jdktools/build.xml which can be used for processing all or selected modules. To be used in federated build; - working_jdktools/modules/$M/build.xml used for processing the $M module. These module-level build.xml files can be used while working with single module. The working_jdktools/make/ dir contains definitions imported by modules' build.xml files so few simple buildfiles are required in each module directory. I'm going to complete the HARMONY-2180 sub-task in few days to provide final script set. Thank you -Ilya On 11/13/06, Geir Magnusson Jr. wrote: > Can you please give us an idea of what you have right now? There's no > way we can participate with you if we don't have an idea of current > status... > > geir > > > Ilya Neverov wrote: > > On 10/31/06, Geir Magnusson Jr. wrote: > > [skip] > >> > Assumptions which look reasonable for jdktool's build subsystem: > >> > > >> > 1) it works in presence of built classlib (as HDK binaries or as a > >> > result of classlib phase of overall build); > >> > >> yes - think of the same trick we do w/ DRLVM to "reach over" to find it. > >> I'd imagine the federated build to then have : > >> > >> trunk/ > >> working_classlib/ > >> working_vm/ > >> working_jdktools/ > >> > > > > Commiters, > > > > Could you please create empty directory "trunk/working_jdktools". > > > > I need it to check building jdktools as part of the federated build. > > Without having the "working_jdktools/" in the repository the moving > > sources and patching buiild files would require additional manual > > steps. > > > > Thank you. > > -Ilya > > >