I've been looking at running hackyInstaller through eclipse, i.e. running
Control.main() as a Java Application. There are some problems with getting
the right System.properties. For example, I'm not quite sure how
installerResources gets set or how it is used. It is probably really worth
sitting down for a couple of hours (if it even takes that long) to figure
out how to do it. Then you can run hackyInstaller for these GUI UI
debugging without even the Ant based build.
Austin, Hongbing is probably the best person to help you figure this out.
thanks, aaron
At 09:17 PM 10/12/2005, Philip Johnson wrote:
--On Wednesday, October 12, 2005 6:32 PM -1000 Aaron Kagawa
<[EMAIL PROTECTED]> wrote:
And maybe the GUI creation process won't be as painful when the new
build system is in.
Whoa, using even quickStart to do your kind of GUI UI debugging is way too
much overhead!
For this kind of iterative development, you should create an ant target
(in hackyInstaller/local.build.xml) that just recompiles the sources and
then invokes <java> with the appropriate classpath and main class to start
with. Two or three seconds max should be all you should need wait for the
window.
As Aaron says, of course run the test suite before committing your
changes, but if you're just doing button placement there's no sense in
redeploying the server or anything.
Cheers,
Philip
