You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flume.apache.org by "E. Sammer (Resolved) (JIRA)" <ji...@apache.org> on 2012/02/23 07:57:48 UTC

[jira] [Resolved] (FLUME-972) Missing dep when attempting to prepare flume dir for import into Eclipse

     [ https://issues.apache.org/jira/browse/FLUME-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

E. Sammer resolved FLUME-972.
-----------------------------

    Resolution: Invalid
      Assignee: E. Sammer

This is because not all plugins support referencing the reactor. Maven can be pretty broken that way. The site plugin suffers from the same problem (which is why I never completed the site build with javadoc from all of the components). There's no good solution to this other than to not use the eclipse maven plugin and, instead, use m2eclipse.

Closing as invalid.
                
> Missing dep when attempting to prepare flume dir for import into Eclipse
> ------------------------------------------------------------------------
>
>                 Key: FLUME-972
>                 URL: https://issues.apache.org/jira/browse/FLUME-972
>             Project: Flume
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: v1.0.0
>         Environment: RHEL 6.2 64-bit
>            Reporter: Will McQueen
>            Assignee: E. Sammer
>             Fix For: v1.1.0
>
>
> Issue: Cannot run 'mvn eclipse:eclipse' to prepare flumeng checkout for import into eclipse
> Steps:
> 1. Use fresh checkout of flume-728 branch
> 2. mvn package
> 3. mvn eclipse:add-maven-repo -Declipse.workspace=/home/will/workspace-flumeng
> 4. mvn eclipse:eclipse
> ...results in:
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-remote-resources-plugin:1.1:process (default) on project flume-hdfs-sink: Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing:
> [ERROR] 1) org.apache.flume:flume-ng-core:jar:1.1.0-incubating-SNAPSHOT

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira