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 alexei.fedotov@gmail.com
 designates 72.14.214.238 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=SxI9fiGJr+U5eOshGzG7STt99ni8SVFrw4hbZo+HZt3MrMBGvEsH3c4hhPIdqd1MLwDx4Q65yZ/yoVaIYs6eMOvQ4ErJavoVBFy0MJNcCIGuObdsbBCnlUyjnxgaibX4DnjRYYCUGYI6EFNE9m7hJtZdOrqQ8qOLNFF0FyLpGko=
Message-ID: <c30d70960802170300q5b5249a9of47cbb8ba7c03d73@mail.gmail.com>
Date: Sun, 17 Feb 2008 14:00:20 +0300
From: "Alexei Fedotov" <alexei.fedotov@gmail.com>
To: dev@harmony.apache.org
Subject: Re: [build] ant utility target to copy working_vm to working_classlib
In-Reply-To: <c3755b3a0802170224x65cbd1f4n2cad41fd3c86d9c9@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <3b3f27c60802161258k7155e16ah30912357e8071cb5@mail.gmail.com>
	 <c30d70960802170116n5f18b58bq162c58d2344d8350@mail.gmail.com>
	 <c3755b3a0802170224x65cbd1f4n2cad41fd3c86d9c9@mail.gmail.com>

Alexey
You are correct about incremental build issue of the federated build.

The fix of the issue is not very difficult: see HARMONY-5521 for the
patch. BTW, the build file with Nathan's unified hyphens looks much
more readable. Thanks, Nathan!

[1] http://issues.apache.org/jira/browse/HARMONY-5521


On Feb 17, 2008 1:24 PM, Alexey Petrenko <alexey.a.petrenko@gmail.com> wrote:
> Current federated build is not suited for every day work. Because it
> makes only clean builds and this takes lots of time.
>
> So we should keep possibility to build class library, vm and selected
> class library module alone.
>
> SY, Alexey
>
> 2008/2/17, Alexei Fedotov <alexei.fedotov@gmail.com>:
>
> > Nathan, all,
> > Copying class library artifacts to the working_vm/ directory is a
> > legacy of two component system, isn't it? Now, when we have several
> > (three, and will have more) upper level components, it looks
> > reasonable to collect the build artifacts at the same upper level. Why
> > should not we assemble the build in the target/ dir? May be one should
> > add several target directories for different build configurations. I
> > believe that the artifact location should not affect class library
> > development, we just need to move deploy directories to a common
> > place.
> >
> > What do you think?
> >
> > On Feb 16, 2008 11:58 PM, Nathan Beyer <ndbeyer@apache.org> wrote:
> > > I was thinking that we could use a utility target in the top-level
> > > build script that copied the HDK artifacts from the working_vm to the
> > > working_classlib, but I'm still catching up with the new DRLVM build.
> > > Would copying the 'working_vm/deploy' to the 'working_classlib/deploy'
> > > be sufficient?
> > >
> > > The use for this would be to facilitate class library development, so
> > > I want to be able to run the top-level build, copy the HDK artifacts,
> > > then move into 'working_classlib' and be able to do cleans, rebuilds
> > > and tests.
> > >
> > > -Nathan
> > >
> >
> >
> >
> > --
> > With best regards,
> > Alexei
> >
>


-- 
With best regards,
Alexei