calcite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edmon Begoli <>
Subject Re: Setting up Calcite development with Eclipse
Date Thu, 08 Feb 2018 17:23:08 GMT
I am on Maven 3.5 and Eclipse Oxygen .2

I did mvn eclipse:eclipse.

Then "open existing project -> open" Chose the specialized imports and
selected "Maven -> import maven project" and selected root directory name,
chose the Maven source.

At the attempt of import, I got:

No marketplace entries found to handle fmpp-maven-plugin:1.0:generate in
Eclipse.  Please see Help for more information.
No marketplace entries found to handle javacc-maven-plugin:2.4:javacc in
Eclipse.  Please see Help for more information.
No marketplace entries found to handle maven-clean-plugin:3.0.0:clean in
Eclipse.  Please see Help for more information.

By looking around, it looks like I would need to switch to external, and
not embedded Maven.

Did not try that yet.

Any suggestions?

NOTE: I am doing this for the purpose of documenting the repeatable setup
steps for contributing developers using different, popular IDEs.

On Thu, Feb 8, 2018 at 10:57 AM, Josh Elser <> wrote:

> I've chased these down a few times on Avatica and other projects.
> In general, you shouldn't have to invoke the eclipse:eclipse mojo directly
> to import to modern versions of Eclipse. You should just be able to import
> it as a Maven project. If that fails, it's something we can/should fix in
> Calcite itself.
> Can you share what you're seeing, Edmon?
> On 2/8/18 1:20 AM, Malcolm Taylor wrote:
>> This worked for me:
>> 1) fork the calcite repository on github
>> 2) clone your fork
>> 3) mvn -version
>> (make sure you have Maven 3.5.2, if not then upgrade)
>> 4) mvn eclipse:eclipse
>> 5) start eclipse, Import existing projects into workspace
>> On 8 February 2018 at 02:20, Edmon Begoli <> wrote:
>> Does anyone have instructions how to setup Eclipse for Calcite
>>> development?
>>> I would like to document that for  CALCITE-2172
>>> <> while I am at it.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message