Re: master branch compilation errors shown in Eclipse

An error shows that the class *ExprLexer* cannot be resolved, The .java file for that class is generated and found in *drill-logical* project (module ?) int it's *target/generated-sources/antlr3/* folder, which I configured, through Eclipse, to be a source folder and then *ALL* compilation errors

Re: master branch compilation errors shown in Eclipse

The TSV file is ruined by the stacktraces in the maven exceptions, I deleted those and attached another one excluding them. Thanks, Gelbana On Wed, Aug 2, 2017 at 8:17 PM, Muhammad Gelbana wrote: > I attached a TSV file showing the errors I have in Eclipse. I believe its >

Re: master branch compilation errors shown in Eclipse

I attached a TSV file showing the errors I have in Eclipse. I believe its something that has to do with code generation because many errors are: - Compilation errors due to mismatching signatures for overridden methods while the *@Override* annotation is applied - Missing fields\methods

Re: master branch compilation errors shown in Eclipse

Please pass along the detailed error: here or in the JIRA you filed earlier. That way, we can try to figure out what’s happening. Thanks, - Paul On Aug 2, 2017, at 6:45 AM, Muhammad Gelbana > wrote: I pulled the latest code from the master

master branch compilation errors shown in Eclipse

I pulled the latest code from the master branch just today. Ran *mvn clean install -DskipTests* which finished successfully, updated all projects but the update filed due to a *NullPointerException* while updating the *vector* project. So I ran the update again but excluded the *vector* project