Ding Lei writes: > Hello, > First of all, I'd like to say that I enjoy using JDE & ECB very much, > Thank you Paul & Berndl! > > My question is how to add the path to both jde-global-classpath & jde- > source-path whenever a new ECB Source Path is added. And, they might > under be different subdirectories, for ex, "PROJECT_PATH/src" & > "PROJECT_PATH/build", which I hope it will be prompted upon creation. >
Anything is possible because we're talking about software. The problem is deciding exactly what you want to happen. For example, the ECB does not support the concept of projects where every project has its own source path and classpath while the JDEE does support such a concept. So the question becomes: what do you want to update when you update ecb-source-path: the project-specific value of jde-global-classpath and jde-source-path or the global value, i.e., the value stored in the .emacs file, and how do you indicate which if you want support for both. The question also is whether the updating should be done by ECB or by language-specific applications, such as the JDEE. My own preference would be that ECB provide support for ecb-source-path--hook functions that it would call each time a user changes ecb-source-path. Then ECB-aware applications, such as the JDEE (could become), could add a hook function to update their own class- and source-path variables to reflect changes to the ecb-source-path. Paul > And is it possible to associate a build.xml with a ECB source path ? > i.e. Upon adding of new Ecb source path, it would prompt for a build.xml > for that ECB source path & write it to somewhere, so that jde-ant-build > will use that build.xml by default. > Again anything is possible. I don't use Ant and I didn't write nor do I maintain the JDEE's interface to Ant. So I defer to anyone who is still interested in maintaining and enhancing the JDEE's Ant interface to decide how to implement what you suggest. Paul > Thank you! > > > Cheers, > Ding Lei
