harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexei Fedotov" <alexei.fedo...@gmail.com>
Subject Re: [build] ant utility target to copy working_vm to working_classlib
Date Sun, 17 Feb 2008 09:16:37 GMT
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

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,

View raw message