Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: neutral (asf.osuosl.org: 217.158.94.220 is neither permitted nor
 denied by domain of t.p.ellison@gmail.com)
Message-ID: <440EE651.2050609@gmail.com>
Date: Wed, 08 Mar 2006 14:12:33 +0000
From: Tim Ellison <t.p.ellison@gmail.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: harmony-dev <harmony-dev@incubator.apache.org>
Subject: [classlib] modular builds
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I've started to lay down some build scripts within each module for
people who use the command line (as opposed to Eclipse) for development.

These 'module builds' assume that you have a working Harmony JRE in the
deploy/jre directory, and the associated VM overlaid.  Steps for this
'bootstrapping' build should be familiar, and are described on the
website[1].

Once you have the initial Harmony JRE built you can work in a single
module and compile (using the Harmony JRE & Eclipse compiler) and test
changes to just that module.

So, for example, if I want to work in NIO, I can 'cd' into modules/nio
and hack on the source code and tests in there, compile the NIO code by
typing 'ant' in modules/nio/make, and test by typing 'ant test' in that
same dir.

NB: The compile step replaces the nio.jar in the deploy/jre/lib/boot
directory (so if you really screw up you'll have to revert and run the
global build again!)

[1]
http://incubator.apache.org/harmony/subcomponents/classlibrary/build_classlib.html

Regards,
Tim

p.s.  it is still a work in progress

-- 

Tim Ellison (t.p.ellison@gmail.com)
IBM Java technology centre, UK.