>Thanks for pointing out the existence of this variable, Klaus. Perhaps >the JDE should set this variable to the value of jde-db-source-directories >at the beginning of a compilation and when running the build command. >This would avoid a user having to maintain both variables. Yes, this would be nice! Klaus - Paul > >-----Urspr�ngliche Nachricht----- >Von: Chuck Irvine [mailto:[EMAIL PROTECTED]] >Gesendet am: Freitag, 22. September 2000 21:07 >An: [EMAIL PROTECTED] >Cc: [EMAIL PROTECTED] >Betreff: RE: compile next-error can't find path (directory) to file >w/error > >Paul, > >I think you misunderstood my problem. Actually, I am using the +E option >with Jikes and it wasn't Jikes that I was having a problem with. My >problem is with javac compilations. Next-error doesn't seem to have >problems finding/parsing the next error, but with determining the path >(directory) to the source. > >Thought I should clarify so people won't think my problem got solved. >Thanks! > >Chuck > >-----Original Message----- >From: paulk [mailto:[EMAIL PROTECTED]] >Sent: Friday, September 22, 2000 1:38 PM >To: Irvine, Chuck R. >Cc: paulk; jde >Subject: Re: compile next-error can't find path (directory) to file >w/error > > >At 01:18 PM 9/22/00 -0500, you wrote: >>I'm suspecting that my problem might have nothing to do with JDE, but, >>out of the blue, I'm experiencing this maddening problem. Perhaps >>someone can point me in the right direction. When I compile a java file >>and start trying to step through the compile errors, emacs keeps asking >>me for the path to the file. Interestingly, if I compile with Jikes, I >>don't have the problem. I do notice that the Jikes error message >>contains the complete path to the file, and the javac error does not, >>but I'm not sure that this is relevant since the I only recently >started >>having this problem. Your help is GREATLY appreciated. Excerpt from >>compile buffer attached. > >You have to specify the +E compiler command line argument when >compiling >with jikes. The +E option is documented in the Jikes documentation. The >+E >option causes Jikes to generate Emacs-compatible error messages. > >- Paul > > >>Chuck Irvine >>Sprint >> >>Javac compile >>-------------- >> >>cd c:/Chuck/cvshome/cmserver/server/com/sprint/cm/attrfrwk/ >>javac -classpath >>".;c:/chuck/cmcvshome/cmserver/classes;c:/chuck/cvshome/cmserver/lib/bs >h >>-1.0.jar;c:/chuck/cvshome/cmserver/lib/junit3.2/junit.jar" -sourcepath >>".;c:/chuck/cvshome/cmserver/server;c:/chuck/cvshome/cmserver/common" >-d >>c:/chuck/cm/classes -g ElementConstraintEvaluatorBf.java >>ElementConstraintEvaluatorBf.java:17: class >>com.sprint.cm.attrfrwk.ElementConstraintEvaluatorBf must be declared >>abstract. It does not define boolean isSvcPort(java.lang.Object) from >>interface com.sprint.cm.attrfrwk.ConstraintEvaluatorBf. >>public class ElementConstraintEvaluatorBf >> >> >>Jikes compile >>-------------- >> >>jikes -d c:/Chuck/cvshome/cmserver/classes -g +E -classpath >>"c:/Chuck/cvshome/cmserver/common;c:/Chuck/cvshome/cmserver/idl;c:/Chuc >k >>/cvshome/cmserver/server;c:/Chuck/cvshome/cmserver/lib/xmlparserv2.jar; >c >>:/Chuck/cvshome/cmserver/lib/vbjorb.jar;c:/Chuck/cvshome/cmserver/lib/v >b >>japp.jar;c:/Chuck/cvshome/cmserver/lib/bsh-1.0.jar;c:/Chuck/cvshome/cms >e >>rver/lib/classes12.zip;c:/Chuck/cvshome/cmserver/lib/CosNotification.ja >r >>;c:/Chuck/cvshome/cmserver/lib/junit.jar;Q:/tools/weblogic/classes;Q:/t >o >>ols/weblogic/lib/weblogicaux.jar;c:/programs/jdk1.2.2/jre/lib/i18n.jar; >c >>:/programs/jdk1.2.2/jre/lib/rt.jar;c:/programs/jdk1.2.2/lib/dt.jar;c:/p >r >>ograms/jdk1.2.2/lib/tools.jar" ElementConstraintEvaluatorBf.java >>c:/Chuck/cvshome/cmserver/server/com/sprint/cm/attrfrwk/ElementConstrai >n >>tEvaluatorBf.java:17:14:17:14: Error: The abstract method "boolean >>isSvcPort(java.lang.Object domainObject);", inherited from type >>"com/sprint/cm/attrfrwk/ConstraintEvaluatorBf", is not implemented in >>the non-abstract class >>"com/sprint/cm/attrfrwk/ElementConstraintEvaluatorBf". > > >
