A hierarchy of project variables is what I really want. How they are stored
in the project files is not my real concern. As developers we need to
remember to phrase our problem without biasing the implementation.
Currently I am involved in Java Servlet and Applet development where the
servlets and applets are in different subtrees of the development
environment. We have a package hierarchy that looks like:
com.domainpharma
Raven - the current project
classes - Common classes
applets - The applets
servlets - The servlets
I would like to have project settings at each of these nodes such that
setting a value in com.domainpharma would propagate down the tree unless
overriden by a particular node. Servlets and Applets have different
compilation options. Thus they need those settings to be specified on the
lowest level. We are considering using some testing tools that would
require a change in the compilation statement. It would be very handy to
turn that on and off at the com.domainpharma level instead of having to do
it in every one of the subtrees.
Someone else mentioned switching between javac and the jikes compiler. I
have both Java 1.1.8 and Java 1.2 on my machine and try not to have them
mentioned in my path because of the problems that can introduce. It would
be nice to be able to switch compilers easily.
The other reason that I initially mentioned only storing modified settings
has to do with upgrades to JDE. You could handle that issue with a version
number in the project file and perhaps a upgrade command in JDE.
Erik Husby
Domain Pharma Corp
Suite 110 Vox: 781-778-3834
10 Maguire Rd Fax: 781-778-3800
Lexington, MA 02421 Email: [EMAIL PROTECTED]
