>>>>> "Paul" == Paul Kinnucan <[EMAIL PROTECTED]> writes:
Paul> Phillip Lord writes: >> >>>>> "Kai" == Kai Gro�johann <[EMAIL PROTECTED]> writes: >> Kai> I have some lengthy class path statements for compilation in Kai> build.xml, and I thought it would be cool if JDEE could make Kai> use of that for C-c C-v C-z and friends. Then I wouldn't have Kai> to update the paths in two places. -- Two cafe au lait please, Kai> but without milk. >> >> >> This is something that I would also love to have. And as well as >> class path, I'd like to add to the javadoc locations, specify a >> main class, and so on. >> >> I have not come up with a good solution yet, although there are a >> couple of possibilities. Paul> I use David Ponce's JMaker facility for make. It generates a Paul> multilevel set of makefiles for the current project, i.e., a Paul> makefile for each package that is invoked by a toplevel Paul> makefile. JMaker uses JDEE variables, e.g., Paul> jde-global-classpath, jde-compiler, etc., to generate the Paul> paths for the compiler and the classpath. JMaker really Paul> works. The generated makefiles build the project without any Paul> hand tuning and its a snap to regenerate the makefiles when Paul> you add classes or packages to a package. Paul> Perhaps somebody could provides a similar JDEE "plugin" for Paul> Ant. It would be possible, but wouldn't work for me. The build I am using is developed for many different people, most of whom do not use JDE. The communication really has to go the other way. I guess that a simple solution would be to split `jde-project-file-name' conceptually into two, which would be `load-file-name' and `save-file-name'. Then I could set the classpath up as "@CLASSPATH@", and have ant rebuild prj.el as appropriate. Writing a specific ant task with this in mind, which could be distributed with JDE, would isolate users from changes in the way JDE uses variables. Phil
