Import generation problems
For the longest time, I've only barely used the features of JDE. I'm now looking at it a little closer. I'm using version 2.3.2, in Xemacs/Cygwin. I set up a prj.el file, and I set the jde-global-classpath there, so I could get import generation (jde-import-find-and-import) working. I find that this works much of the time, but fails to find some classes, but I'm not sure why. In fact, it almost seems like it doesn't find any classes that would have been reached by my setting of jde-global-classpath. It finds classes in the JDK, but none in my related projects or jar files. Here is my prj.el contents: - (setq jde-global-classpath (quote (common/cmcmbeans/build/cmcmbeans.jar common/serviceregistry/build/esbserviceregistry.jar CMC/common/cmcgui/build/cmcgui.jar lib/weblogic.jar ))) - These jar files all exist, relative to the directory the prj.el file is in.
Import generation problems
Karr, David writes: For the longest time, I've only barely used the features of JDE. I'm now looking at it a little closer. I'm using version 2.3.2, in Xemacs/Cygwin. I set up a prj.el file, and I set the jde-global-classpath there, so I could get import generation (jde-import-find-and-import) working. I find that this works much of the time, but fails to find some classes, but I'm not sure why. In fact, it almost seems like it doesn't find any classes that would have been reached by my setting of jde-global-classpath. It finds classes in the JDK, but none in my related projects or jar files. Here is my prj.el contents: - (setq jde-global-classpath (quote (common/cmcmbeans/build/cmcmbeans.jar common/serviceregistry/build/esbserviceregistry.jar CMC/common/cmcgui/build/cmcgui.jar lib/weblogic.jar ))) - These jar files all exist, relative to the directory the prj.el file is in. You should update to the latest version of the JDEE that is several years old. A lot of water has flowed under the bridge since then. You should also read the section on project-relative paths in the JDEE user's guide. The reason the JDEE cannot find that classes in your projects is that you have incorrectly specified the paths. To specify a path relative to the project file directory, you must use the period (.) character, e.g., ./common/cmcmbeans/build/cmcmbeans.jar Paul
RE: Import generation problems
That worked, thanks. I believe I read that section, but I missed the point about the dot prefix. I guess I'll proceed with upgrading. -Original Message- From: Paul Kinnucan [mailto:[EMAIL PROTECTED] Sent: Friday, November 12, 2004 9:10 AM To: Karr, David Cc: [EMAIL PROTECTED] Subject: Import generation problems Karr, David writes: For the longest time, I've only barely used the features of JDE. I'm now looking at it a little closer. I'm using version 2.3.2, in Xemacs/Cygwin. I set up a prj.el file, and I set the jde-global-classpath there, so I could get import generation (jde-import-find-and-import) working. I find that this works much of the time, but fails to find some classes, but I'm not sure why. In fact, it almost seems like it doesn't find any classes that would have been reached by my setting of jde-global-classpath. It finds classes in the JDK, but none in my related projects or jar files. Here is my prj.el contents: - (setq jde-global-classpath (quote (common/cmcmbeans/build/cmcmbeans.jar common/serviceregistry/build/esbserviceregistry.jar CMC/common/cmcgui/build/cmcgui.jar lib/weblogic.jar ))) - These jar files all exist, relative to the directory the prj.el file is in. You should update to the latest version of the JDEE that is several years old. A lot of water has flowed under the bridge since then. You should also read the section on project-relative paths in the JDEE user's guide. The reason the JDEE cannot find that classes in your projects is that you have incorrectly specified the paths. To specify a path relative to the project file directory, you must use the period (.) character, e.g., ./common/cmcmbeans/build/cmcmbeans.jar Paul
