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.
I use David Ponce's JMaker facility for make. It generates a multilevel set of makefiles for the current project, i.e., a makefile for each package that is invoked by a toplevel makefile. JMaker uses JDEE variables, e.g., jde-global-classpath, jde-compiler, etc., to generate the paths for the compiler and the classpath. JMaker really works. The generated makefiles build the project without any hand tuning and its a snap to regenerate the makefiles when you add classes or packages to a package. Perhaps somebody could provides a similar JDEE "plugin" for Ant. Paul > > You could use a "replace" task in ant, and fill in your classpath as > "@CLASSPATH@" or some such. The only difficulty with this is that JDE > by default saves to prj.el. To get this to work you would need to get > it so save to prj.src.el (or whatever) and load from a prj.el > generated by ant. > > The other possibility is this ant task here... > > http://i3sp-build.sourceforge.net/javadoc/com/i3sp/ant/JdeProject.html > > > I've not tried this yet. The documentation suggests that it creates a > prj.el, which would be no good for me, as I would want it to update an > existing prj.el. It would also be sensitive to changes in the > underlying types of the various entities in the prj.el. > > Let me know if you can think of a better alternative! > > Phil
