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 <[email protected]> wrote:
Does anyone have instructions how to setup Eclipse for Calcite development?
I would like to document that for CALCITE-2172
<https://issues.apache.org/jira/browse/CALCITE-2172> while I am at it.
