[
https://issues.apache.org/jira/browse/CALCITE-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15029191#comment-15029191
]
Alexander Reshetov edited comment on CALCITE-994 at 11/26/15 7:10 PM:
----------------------------------------------------------------------
As Josh proposed in mailing list, I'm posting all related text here in site
component.
Copies from mailing list.
{noformat}
Hello,
I tried to import Calcite project into Eclipse and faced some issues.
In newly created workspace I select File - Import - Maven - Existing
Maven Projects
Point "Root Directory" to git cloned dir. Press "Finish".
After this steps I got erros:
- fmpp-maven-plugin:1.0:generate (1 errors)
Description: No marketplace entries found to handle
fmpp-maven-plugin:1.0:generate in Eclipse. Please see Help for more
information.
\- Execution generate-fmpp-sources, in /calcite-core/pom.xml
Description: No marketplace entries found to handle Execution
generate-fmpp-sources, in /calcite-core/pom.xml in Eclipse. Please
see Help for more information.
- javacc-maven-plugin:2.4:javacc (2 errors)
Description: No marketplace entries found to handle
javacc-maven-plugin:2.4:javacc in Eclipse. Please see Help for more
information.
\- Execution javacc, in /calcite-core/pom.xml
Description: No marketplace entries found to handle Execution
javacc, in /calcite-core/pom.xml in Eclipse. Please see Help for more
information.
\- Execution javacc, in /calcite-piglet/pom.xml
Description: No marketplace entries found to handle Execution
javacc, in /calcite-piglet/pom.xml in Eclipse. Please see Help for
more information.
After some googling it pointed out that while Eclipse uses incremental
compilation,
his m2eclipse plugin should have information from maven plugins about
lifecycle management.
See [1] for more details regarding this behaviour.
I also found similar issue (already closed) in Apache Drill. See Jira
ticket [2] and pull request
for it [3].
I modified pom.xml in calcite-core and calcite-piglet modules, which
caused this issue and
it was fixed for me. See git diffs [4] and [5].
There is also errors from checkstyle checks, but probably it's just my
setup. Didn't investigate yet.
[1] - http://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html
[2] - https://issues.apache.org/jira/browse/DRILL-445
[3] -
https://github.com/apache/drill/commit/1e25c0d287b8ca55d7ae3242b638659c68d115da
[4] - http://pastebin.com/VsV4RcG2
[5] - http://pastebin.com/Dhf9VJrS
{noformat}
{noformat}
Checked out probably better solution. At least from project point of view.
While such behaviour Eclipse-specific, it may be better to manage
lifecycle mapping
directly in Eclipse without blowing up project's POMs.
This feature is available from Eclipse 4.2 as described in
https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html
part "Eclipse 4.2 Adds Default Mapping".
Note: while this feature is experimental, it have some issues. At least for me
this setting is same across workspaces, while it should be unique for
each workspace or even project.
To solve early mentioned issue with project import you need to add next config
in specified lifecycle-mapping-metadata.xml
<?xml version="1.0" encoding="UTF-8"?>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>com.googlecode.fmpp-maven-plugin</groupId>
<artifactId>fmpp-maven-plugin</artifactId>
<versionRange>[1.0,)</versionRange>
<goals>
<goal>generate</goal>
</goals>
</pluginExecutionFilter>
<action>
<execute>
<runOnIncremental>false</runOnIncremental>
<runOnConfiguration>true</runOnConfiguration>
</execute>
</action>
</pluginExecution>
<pluginExecution>
<pluginExecutionFilter>
<groupId>org.codehaus.mojo</groupId>
<artifactId>javacc-maven-plugin</artifactId>
<versionRange>[2.4,)</versionRange>
<goals>
<goal>javacc</goal>
</goals>
</pluginExecutionFilter>
<action>
<execute>
<runOnIncremental>false</runOnIncremental>
<runOnConfiguration>true</runOnConfiguration>
</execute>
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata>
{noformat}
was (Author: areshetov):
Copies from mailing list.
{noformat}
Hello,
I tried to import Calcite project into Eclipse and faced some issues.
In newly created workspace I select File - Import - Maven - Existing
Maven Projects
Point "Root Directory" to git cloned dir. Press "Finish".
After this steps I got erros:
- fmpp-maven-plugin:1.0:generate (1 errors)
Description: No marketplace entries found to handle
fmpp-maven-plugin:1.0:generate in Eclipse. Please see Help for more
information.
\- Execution generate-fmpp-sources, in /calcite-core/pom.xml
Description: No marketplace entries found to handle Execution
generate-fmpp-sources, in /calcite-core/pom.xml in Eclipse. Please
see Help for more information.
- javacc-maven-plugin:2.4:javacc (2 errors)
Description: No marketplace entries found to handle
javacc-maven-plugin:2.4:javacc in Eclipse. Please see Help for more
information.
\- Execution javacc, in /calcite-core/pom.xml
Description: No marketplace entries found to handle Execution
javacc, in /calcite-core/pom.xml in Eclipse. Please see Help for more
information.
\- Execution javacc, in /calcite-piglet/pom.xml
Description: No marketplace entries found to handle Execution
javacc, in /calcite-piglet/pom.xml in Eclipse. Please see Help for
more information.
After some googling it pointed out that while Eclipse uses incremental
compilation,
his m2eclipse plugin should have information from maven plugins about
lifecycle management.
See [1] for more details regarding this behaviour.
I also found similar issue (already closed) in Apache Drill. See Jira
ticket [2] and pull request
for it [3].
I modified pom.xml in calcite-core and calcite-piglet modules, which
caused this issue and
it was fixed for me. See git diffs [4] and [5].
There is also errors from checkstyle checks, but probably it's just my
setup. Didn't investigate yet.
[1] - http://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html
[2] - https://issues.apache.org/jira/browse/DRILL-445
[3] -
https://github.com/apache/drill/commit/1e25c0d287b8ca55d7ae3242b638659c68d115da
[4] - http://pastebin.com/VsV4RcG2
[5] - http://pastebin.com/Dhf9VJrS
{noformat}
{noformat}
Checked out probably better solution. At least from project point of view.
While such behaviour Eclipse-specific, it may be better to manage
lifecycle mapping
directly in Eclipse without blowing up project's POMs.
This feature is available from Eclipse 4.2 as described in
https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html
part "Eclipse 4.2 Adds Default Mapping".
Note: while this feature is experimental, it have some issues. At least for me
this setting is same across workspaces, while it should be unique for
each workspace or even project.
To solve early mentioned issue with project import you need to add next config
in specified lifecycle-mapping-metadata.xml
<?xml version="1.0" encoding="UTF-8"?>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>com.googlecode.fmpp-maven-plugin</groupId>
<artifactId>fmpp-maven-plugin</artifactId>
<versionRange>[1.0,)</versionRange>
<goals>
<goal>generate</goal>
</goals>
</pluginExecutionFilter>
<action>
<execute>
<runOnIncremental>false</runOnIncremental>
<runOnConfiguration>true</runOnConfiguration>
</execute>
</action>
</pluginExecution>
<pluginExecution>
<pluginExecutionFilter>
<groupId>org.codehaus.mojo</groupId>
<artifactId>javacc-maven-plugin</artifactId>
<versionRange>[2.4,)</versionRange>
<goals>
<goal>javacc</goal>
</goals>
</pluginExecutionFilter>
<action>
<execute>
<runOnIncremental>false</runOnIncremental>
<runOnConfiguration>true</runOnConfiguration>
</execute>
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata>
{noformat}
> Calcite development under Eclipse IDE
> -------------------------------------
>
> Key: CALCITE-994
> URL: https://issues.apache.org/jira/browse/CALCITE-994
> Project: Calcite
> Issue Type: Improvement
> Components: site
> Reporter: Alexander Reshetov
> Assignee: Julian Hyde
> Priority: Minor
> Attachments: lifecycle-mapping-metadata.xml
>
>
> After "git clone" project could not be imported in Eclipse as existing Maven
> project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
