Thanks Paul! Yes it is desirable to do so...I look forward to using it.
> -----Original Message----- > From: Paul Kinnucan [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 23, 2003 12:58 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Problem report reconsidered > > > > ----- Original Message ----- > > From: "Charles Sutton" <[EMAIL PROTECTED]>m > > To: <[EMAIL PROTECTED]> > > Sent: Tuesday, September 16, 2003 10:16 PM > > Subject: Previous implement-interface problem report > > > > > > > > > > Yesterday I filed a problem report on the implement-interface > > > wizard being able to fully-qualify an interface name but not > > > being able to locate it in the classpath. I am now able to give > > > a minimal (if convoluted) test case. > > > > > > However, I'm not sure if this is a bug, or just > configuration error. > > > The basic issue was that my jde-global-classpath had a > relative path > > > "./class" in it, but it was specified in my .emacs file > rather than > > > in my prj.el. > > Hi Charles, > > I'm reconsidering my decision to treat this problem as a configuration > error. It may be desirable to interpret a relative path as a value > of a variable (e.g., jde-global-classpath) set in a .emacs > file as relative to the closest project file from the current > directory > if no project file in the current directory tree sets the variable. > > Paul >
