[
https://issues.apache.org/jira/browse/CALCITE-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15029560#comment-15029560
]
Alexander Reshetov commented on CALCITE-994:
--------------------------------------------
Usually content from this file placed directly in pom.xml (main pom.xml, or
related sub-modules').
While it affects M2Eclipse only and does not changes behaviour of plain maven
it's safe to do in a such way. But I really don't like to blow up project's
pom.xml without absolute necessary.
I think it could be placed in m2e folder in root of repo. Or even be available
for download just from site. Thus it will not make mess in repository for those
who use other development environment and at the same time would be available
right after git clone.
Maybe something like "contrib" folder could be too. But it could be confusing a
little bit, while usually this is place for some kind of extensions/plugins.
And yet another one alternative:
For javacc-maven-plugin could be created feature request to support M2E if they
ok with it.
But fmpp-maven-plugin seems like dead project.. But sure we can try to reach
author.
So I think mentioning about problem on site and included XML content may be
enough.
> 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)
