I'm using WSAD, which is an IBM product built on the Eclipse platform; my
experience may not be relevant and may not be the best solution, but for
what it's worth:
I started by importing my existing Xalan directory as a new project.
(file/new/project/java project, uncheck "use default" and specify the
java/src directory as the project contents, call the project "xalan").
I then opened properties on that project and flipped to the Java Build Path
section. You can set the output directory on any of those four pages; I
used xalan/wsad-build (that is, create a directory called
java/src/wsad-build and output into that).
This is also where you set classpaths. I have xml-commons and xml-xerces
previously set up as projects, so I can check those as dependencies.
(Setting them up is the same process I'm describing here for Xalan, of
course -- consider this a recursive description.) On the Libraries page, I
used Add External JARs to bring in all the jarfiles needed for stuff the
Xerces and Commons projects don't supply. On the last page, I didn't Export
anything other than Xalan itself.
Rather than deal with changing the properties on the Process class every
time I want to alter the command line arguments (or system properties), I
rattled off a short driver class in the default package and launch the
processor through that. The advantage is that I can keep several tests
around and comment in and out which one I want to run, and I can use a bit
of string processing so I don't have to retype directory paths quite so
much when I switch testcases. It's a kluge, but I find it useful.
______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"The world changed profoundly and unpredictably the day Tim Berners Lee
got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
