Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (athena.apache.org: domain of t.p.ellison@gmail.com
 designates 66.249.92.170 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding;
        b=oVEzTEy6dLs3I+J467Jp31F4cNiQ8+vfnnPNZxhvfG2F3amWb5vX2V439Su4VgObPWT1QcwFTesOKZDcT7VxGoJWE8bVgxSbi6qevZC8h9O7GCaItTwneRZD8FoYijnAMQMJsidL0qAerbus9bmsChZKpir1WOrq7wqllfEIaq4=
Message-ID: <47EBBB90.1070106@gmail.com>
Date: Thu, 27 Mar 2008 15:21:52 +0000
From: Tim Ellison <t.p.ellison@gmail.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: dev@harmony.apache.org
Subject: Re: Changing default federated build target Was: [jira] Commented:
 (HARMONY-5521) [build] fix incremental federated build
References: <c30d70960803270805n78f72169v119f8ffb1874f2d0@mail.gmail.com>
	 <47EBB91F.2040405@gmail.com>
 <c30d70960803270816t60467ed8ve819e946cbc13562@mail.gmail.com>
In-Reply-To: <c30d70960803270816t60467ed8ve819e946cbc13562@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Alexei Fedotov wrote:
> Tim, I renamed "build-all" to "build" to follow this pattern. It was
> Geir who addded "clean" target long time ago. Do you want "rebuild"
> target to be added?

That would suit me (the target names I have become used to using) and 
would be consistent.  Thanks.

Tim


> On Thu, Mar 27, 2008 at 6:11 PM, Tim Ellison <t.p.ellison@gmail.com> wrote:
>> FWIW the names used in the classlib level build script are:
>>
>>  build - default target, does an incremental build
>>  clean - as you would expect
>>  rebuild - clean followed by build
>>  ...
>>
>>  Maybe it would be good to be consistent with the names here.
>>
>>  Regards,
>>  Tim
>>
>>
>>
>>
>>  Alexei Fedotov wrote:
>>  > Tim wrote in HARMONY-5521:
>>  >>  Why not make the incremental build the default?  This is more likely the one people will be using daily.
>>  >
>>  > We should ask people who are in charge of snapshot creation since they
>>  > probably use a default target for their script now. It might be good
>>  > to rename the "default" target into "all" or something because it
>>  > would not be conventional to call it "default" any longer. This is
>>  > done via incremental_build_1.patch [2]. Stepan, Alexey, what do you
>>  > about Tim's suggestion and the patch?
>>  >
>>  > The following step would be to do something about class library
>>  > natives which are rebuilt each time.
>>  >
>>  > [1] https://issues.apache.org/jira/browse/HARMONY-5521
>>  > [2] https://issues.apache.org/jira/secure/attachment/12378724/incremental_build_1.patch
>>  >
>>  > On Thu, Mar 27, 2008 at 5:29 PM, Tim Ellison (JIRA) <jira@apache.org> wrote:
>>  >>
>>  >>     [ https://issues.apache.org/jira/browse/HARMONY-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582662#action_12582662 ]
>>  >>
>>  >>  Tim Ellison commented on HARMONY-5521:
>>  >>  --------------------------------------
>>  >>
>>  >>  Why not make the incremental build the default?  This is more likely the one people will be using daily.
>>  >>
>>  >>
>>  >>  > [build] fix incremental federated build
>>  >>  > ---------------------------------------
>>  >>  >
>>  >>  >                 Key: HARMONY-5521
>>  >>  >                 URL: https://issues.apache.org/jira/browse/HARMONY-5521
>>  >>  >             Project: Harmony
>>  >>  >          Issue Type: Improvement
>>  >>  >          Components: build - test - ci
>>  >>  >            Reporter: Alexei Fedotov
>>  >>  >            Assignee: Pavel Pervov
>>  >>  >         Attachments: incremental_build.patch
>>  >>  >
>>  >>  >
>>  >>  > This is a patch which enables incremental Harmony build via conventional federated build option "build". Testing changes.
>>  >>
>>  >>  --
>>  >>  This message is automatically generated by JIRA.
>>  >>  -
>>  >>  You can reply to this email to add a comment to the issue online.
>>  >>
>>  >>
>>  >
>>  >
>>  >
>>
> 
> 
>