[
https://issues.apache.org/jira/browse/FLUME-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232947#comment-13232947
]
Arvind Prabhakar commented on FLUME-1032:
-----------------------------------------
Thanks again. The only issue with the 1.1.0 patch is that the following
dependency added to top level pom should be version 1.1.0-incubating instead of
1.2.0-incubating-SNAPSHOT:
{noformat}
@@ -656,6 +644,12 @@
<version>1.1.0-incubating</version>
</dependency>
+ <dependency>
+ <groupId>org.apache.flume.flume-ng-clients</groupId>
+ <artifactId>flume-ng-log4jappender</artifactId>
+ <version>1.2.0-incubating-SNAPSHOT</version>
+ </dependency>
+
{noformat}
> Fix / clean up Flume NG build
> -----------------------------
>
> Key: FLUME-1032
> URL: https://issues.apache.org/jira/browse/FLUME-1032
> Project: Flume
> Issue Type: Improvement
> Reporter: Mike Percy
> Assignee: Mike Percy
> Attachments: FLUME-1032-8-branch-1.1.0.patch, FLUME-1032-8.patch
>
>
> There are problems with the current Flume NG maven build setup:
> 1. Maven build against Hadoop 0.23 is misconfigured:
> - Referenced Hadoop artifact does not exist in central repo (build fails
> due to this)
> - commons-logging gets pulled in, which causes slf4j errors at Flume
> runtime due to multiple logger implementations (commons & log4j)
> 2. Several artifacts are missing from the -dist archive:
> - SDK jar
> - Legacy sources
> - log4j appender client
> Patch forthcoming to address these issues.
--
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
