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 were gone.

Shouldn't that be configured in maven somewhere ?



Thanks,
Gelbana

On Wed, Aug 2, 2017 at 8:22 PM, Muhammad Gelbana <m.gelb...@gmail.com>
wrote:

> 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 <m.gelb...@gmail.com>
> wrote:
>
>> 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 such as the missing *INSTANCE* field in
>>    *org.apache.calcite.rel.metadata.DefaultRelMetadataProvider* (Shown
>>    in the screenshot)
>>
>>
>> Thanks,
>> Gelbana
>>
>> On Wed, Aug 2, 2017 at 6:16 PM, Paul Rogers <prog...@mapr.com> wrote:
>>
>>> 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 <m.gelb...@gmail.com
>>> <mailto:m.gelb...@gmail.com>> wrote:
>>>
>>> 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
>>> this time.
>>>
>>> Now I'm left with the errors shown in the attached image.
>>>
>>> I'm used to developing a Drill plugin in Eclipse but using the 1.9
>>> branch with only errors only related to maven like lifecycles errors. And
>>> that didn't cause any issue for me.
>>>
>>> I was hoping to create a simple PR but this is blocking me. Would
>>> someone please help me get through this ?
>>>
>>> ​Thanks,
>>> Gelbana
>>>
>>>
>>
>

Reply via email to