[
https://issues.apache.org/jira/browse/FLUME-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13651044#comment-13651044
]
Thiruvalluvan M. G. commented on FLUME-2009:
--------------------------------------------
bq. I think you should get rid of the open-ended version spec [1.2,) as it
occasionally screws things up by bringing in snapshots or non-working code
Thanks for looking at it.
It does not introduce a dependency. It is in the <pluginManagement> and is in
the configuration for the plugin me2. That is, it is not the version range for
the plugin itself; The consumer of the version range is not Maven but rather
me2. What it says is something like this: "If you use paranamer plugin version
1.7 or above (the actual version is specified in the plugins section againt
paranamer plugin) m2e should ignore the plugin when importing this project into
Eclipse".
In fact, m2e plugin encourages use of version ranges instead of version for its
argument; there is no "version" parameter, there is only "versionRange"
parameter.
As I mentioned earlier, the entire change of this patch is a no-op everywhere
outside Eclipse.
> Flume project throws error when imported into Eclipse IDE (Juno)
> ----------------------------------------------------------------
>
> Key: FLUME-2009
> URL: https://issues.apache.org/jira/browse/FLUME-2009
> Project: Flume
> Issue Type: Improvement
> Components: Build
> Affects Versions: v1.3.1
> Reporter: Thiruvalluvan M. G.
> Assignee: Thiruvalluvan M. G.
> Attachments: FLUME-2009.patch
>
>
> It happens because Eclipse's M2E (maven integration) does not know what to do
> when certain plugins are executed. The forthcoming patch fixes the problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
