Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates
 209.85.216.49 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=jVMBgqH0DWiwjAbPNVmQu0JASvwn+k6/cDY4i6lSqfXtGuvz4siKuGi23YOSDR8yTt
         7BnyhkpozjiYoyRNUDQFqPrEM4G26PstDiRe+24wutcTwDE4BvVI2QhYdWaNRePzebeJ
         fzf7z0SCWAe7thwqIM5myi6052rdWeplUYwVk=
MIME-Version: 1.0
In-Reply-To: <201009231117.o8NBHGPa030236@d06av04.portsmouth.uk.ibm.com>
References: <201009231117.o8NBHGPa030236@d06av04.portsmouth.uk.ibm.com>
Date: Thu, 23 Sep 2010 12:58:49 +0100
Message-ID: <AANLkTik=rScQQgo7c88XRLshYsnxPr=a8V=VpEMeXU0H@mail.gmail.com>
Subject: Re: [build] Ensuring consistent build environment for releases
From: sebb <sebbaz@gmail.com>
To: dev@harmony.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 23 September 2010 12:17, Mark Hindess <mark.hindess@googlemail.com> wrot=
e:
>
> I've been looking at:
>
> =A0https://issues.apache.org/jira/browse/HARMONY-6535
>
> and wondering about build processes particularly for releases.
>
> Some of you might have noticed (as I checked in my scripts recently[0]),
> that I try quite hard to ensure that the linux builds are built with a
> known environment. =A0In particular, these scripts do:
>
> =A0cat /tmp/build/*/common_resources/depends/jars/ecj_*/ecj-*.jar \
> =A0 =A0 =A0>/usr/share/ant/lib/ecj-harmony.jar
>
> to ensure that the version of ecj used during the build is the one
> defined by the harmony dependency downloads.
>
> I don't really have an equivalent clean process for windows and it looks
> like the version of ecj.jar on my windows build machine was a little
> older than the 3.5.1 that I used on Linux. =A0So this accounts for the
> differences described in the above JIRA.
>
> Obviously I've fixed my machine now and will try to make sure I check
> this before building release binaries in future. =A0However, I'd prefer a
> more robust solution.
>
> I'd be tempted to add a build time check to look at the ecj jar version
> that is available but there doesn't seem to be enough information in the
> ecj.jar manifests to do this.
>
> Anyone got any bright ideas?

I must be missing something here.

Can you not give the ecj jar a version-specific path name, and use
that in the classpath?

> Regards,
> =A0Mark.
>
> [0] https://svn.apache.org/repos/asf/harmony/standard/tools/release
>
>