Return-Path: Delivered-To: apmail-incubator-harmony-dev-archive@www.apache.org Received: (qmail 9582 invoked from network); 5 Jul 2006 11:03:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 5 Jul 2006 11:03:57 -0000 Received: (qmail 25581 invoked by uid 500); 5 Jul 2006 11:03:53 -0000 Delivered-To: apmail-incubator-harmony-dev-archive@incubator.apache.org Received: (qmail 25544 invoked by uid 500); 5 Jul 2006 11:03:53 -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 25533 invoked by uid 99); 5 Jul 2006 11:03:53 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Jul 2006 04:03:53 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of a.y.chernyshev@gmail.com designates 64.233.162.205 as permitted sender) Received: from [64.233.162.205] (HELO nz-out-0102.google.com) (64.233.162.205) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Jul 2006 04:03:52 -0700 Received: by nz-out-0102.google.com with SMTP id q3so1172640nzb for ; Wed, 05 Jul 2006 04:03:32 -0700 (PDT) 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=uurfHTvsKED/tIjnX+XjwfdvHBzco3NDWiiG/8GyXRHVg0erSVBX2JDVNgI2KnVvOLclJBJpL7KUHIkbuq+L2OfpXJCWzY3Q5YkYXboG37Ru1/kEXUIKo35BsPEbEybTz7QheGX2Lua+kZeAOVEcPaHkc93XbHqje6KGW8rG3+w= Received: by 10.65.218.8 with SMTP id v8mr5112538qbq; Wed, 05 Jul 2006 04:03:31 -0700 (PDT) Received: by 10.65.73.19 with HTTP; Wed, 5 Jul 2006 04:03:31 -0700 (PDT) Message-ID: <6928c5160607050403n36c42cd7vab37d8ae72245cba@mail.gmail.com> Date: Wed, 5 Jul 2006 15:03:31 +0400 From: "Andrey Chernyshev" To: harmony-dev@incubator.apache.org Subject: Re: [drlvm] Removing classlib-related tasks from VM build (was Doing the minimum to support Java 5 classfiles) In-Reply-To: <44AB9674.5030706@Intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <44AB58AF.2080007@Intel.com> <200607050817.k658HGCw019131@d06av02.portsmouth.uk.ibm.com> <44AB9674.5030706@Intel.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 7/5/06, Salikh Zakirov wrote: > Mark Hindess wrote: > > Salikh Zakirov wrote: > >> Using the fixed classlib snapshot will remove one factor > >> of uncertainty, and will make the DRLVM behaviour more reproducible. > > > > -1 > > > > Doing this will hide issues that appear when changes to classlib breaks > > drlvm. At this stage in the project, I'd rather have such issues be as > > visible as possible. Such breakages should be relatively easy to fix > > and any drlvm developer should be capable of rolling back classlib svn > > until things are fixed if they get impatient. > > > > I don't see how it significantly affects reproducibility since it is > > trivial to check/record the versions of classlib and drlvm svn when an > > error occurs? > > I agree that recording revision numbers of both classlib and drlvm will be > sufficient to reproduce the problem. > > The hard part is finding the "good" ones when the latest revisions > do not work, in a case when someone wants to work on something different > than fixing the latest breakages. > > I think that the reasonable compromise is to have both capabilities in the > build system (build with classlib snapshot or with latest checkout), and > leave it up to contributors to decide which way to use. One more idea - we have a web page with the classlib snapshots over here: http://people.apache.org/dist/incubator/harmony/snapshots/ with an option of downloading the latest classlib snapshot, or a snapshot at a fixed date. By default, drlvm build could use just the latest one. This will allow to catch the possible classlib/drlvm integration issues at the frequency of creating build snapshots. On the other hand, in case the latest classlib appears to be incompatible with vm, people can easily change the link and use any of previous snapshots. How does that sound? Thanks, Andrey. > > --------------------------------------------------------------------- > Terms of use : http://incubator.apache.org/harmony/mailing.html > To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org > For additional commands, e-mail: harmony-dev-help@incubator.apache.org > > -- Andrey Chernyshev Intel Middleware Products Division --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org For additional commands, e-mail: harmony-dev-help@incubator.apache.org