You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Mike Percy (Created) (JIRA)" <ji...@apache.org> on 2012/03/15 21:18:39 UTC
[jira] [Created] (FLUME-1032) Fix / clean up Flume NG build
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
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
[jira] [Updated] (FLUME-1032) Fix / clean up Flume NG build
Posted by "Mike Percy (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Percy updated FLUME-1032:
------------------------------
Attachment: (was: FLUME-1032-8.patch)
> 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-9-branch-1.1.0.patch, FLUME-1032-9.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
[jira] [Updated] (FLUME-1032) Fix / clean up Flume NG build
Posted by "Mike Percy (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Percy updated FLUME-1032:
------------------------------
Attachment: FLUME-1032-8-branch-1.1.0.patch
> 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
[jira] [Commented] (FLUME-1032) Fix / clean up Flume NG build
Posted by "Arvind Prabhakar (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (FLUME-1032) Fix / clean up Flume NG build
Posted by "Mike Percy (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Percy updated FLUME-1032:
------------------------------
Attachment: (was: FLUME-1032-8-branch-1.1.0.patch)
> 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.patch, FLUME-1032-9-branch-1.1.0.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
[jira] [Updated] (FLUME-1032) Fix / clean up Flume NG build
Posted by "Mike Percy (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Percy updated FLUME-1032:
------------------------------
Attachment: FLUME-1032-8-branch-1.1.0.diff
I applied the other one to a copy of the branch, which applied with some fuzziness warnings but no errors, and then did a diff between the affected files on the trunk and the branch, and all differences were unrelated stuff having to do with artifact version numbers.
This one should apply cleanly to the branch with no warnings.
> 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
[jira] [Updated] (FLUME-1032) Fix / clean up Flume NG build
Posted by "Mike Percy (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Percy updated FLUME-1032:
------------------------------
Attachment: FLUME-1032-8.patch
> 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.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
[jira] [Commented] (FLUME-1032) Fix / clean up Flume NG build
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233056#comment-13233056 ]
Hudson commented on FLUME-1032:
-------------------------------
Integrated in flume-trunk #133 (See [https://builds.apache.org/job/flume-trunk/133/])
FLUME-1032. Fix Flume NG build.
(Mike Percy via Arvind Prabhakar) (Revision 1302711)
Result = SUCCESS
arvind : http://svn.apache.org/viewvc/?view=rev&rev=1302711
Files :
* /incubator/flume/trunk/flume-ng-clients/flume-ng-log4jappender/pom.xml
* /incubator/flume/trunk/flume-ng-dist/pom.xml
* /incubator/flume/trunk/flume-ng-dist/src/main/assembly/dist.xml
* /incubator/flume/trunk/flume-ng-dist/src/main/assembly/src.xml
* /incubator/flume/trunk/flume-ng-sinks/flume-hdfs-sink/pom.xml
* /incubator/flume/trunk/pom.xml
> 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
> Fix For: v1.1.0, v1.2.0
>
> Attachments: FLUME-1032-9-branch-1.1.0.patch, FLUME-1032-9.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
[jira] [Commented] (FLUME-1032) Fix / clean up Flume NG build
Posted by "Mike Percy (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230523#comment-13230523 ]
Mike Percy commented on FLUME-1032:
-----------------------------------
Forgot to mention one more problem with Hadoop 0.23: hadoop-hdfs JAR was not included. Not that hard to miss since Filesystem is included in hadoop-core but DistributedFileSystem is only included in hadoop-hdfs.
> 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
>
> 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
[jira] [Updated] (FLUME-1032) Fix / clean up Flume NG build
Posted by "Mike Percy (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Percy updated FLUME-1032:
------------------------------
Attachment: FLUME-1032-9.patch
Updated trunk patch which was applying with fuzz after some commits
> 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-9-branch-1.1.0.patch, FLUME-1032-9.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
[jira] [Updated] (FLUME-1032) Fix / clean up Flume NG build
Posted by "Mike Percy (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Percy updated FLUME-1032:
------------------------------
Attachment: FLUME-1032-9-branch-1.1.0.patch
Thanks for the catch Arvind. Here's a new patch for the 1.1.0 branch.
I ran a full mvn clean package with unit tests against the branch and it looks good to me.
> 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.patch, FLUME-1032-9-branch-1.1.0.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
[jira] [Updated] (FLUME-1032) Fix / clean up Flume NG build
Posted by "Arvind Prabhakar (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arvind Prabhakar updated FLUME-1032:
------------------------------------
Resolution: Fixed
Fix Version/s: v1.2.0
v1.1.0
Status: Resolved (was: Patch Available)
Patch committed to trunk and 1.1.0 branch. Thanks Mike!
> 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
> Fix For: v1.1.0, v1.2.0
>
> Attachments: FLUME-1032-9-branch-1.1.0.patch, FLUME-1032-9.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
[jira] [Commented] (FLUME-1032) Fix / clean up Flume NG build
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230589#comment-13230589 ]
jiraposter@reviews.apache.org commented on FLUME-1032:
------------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4368/
-----------------------------------------------------------
Review request for Flume.
Summary
-------
Fixing various build issues:
1. Maven build against Hadoop 0.23 is misconfigured:
- Referenced Hadoop artifact (0.23-SNAPSHOT) does not exist in central repo (build fails due to this)
- slf4j-jcl gets pulled in, which breaks logging at runtime due to the inclusion of slf4j-log4j12 as well
- downstream dependencies which should be transitively included are explicitly referenced only for hadoop-0.23 (commons-logging and commons-configuration)
- hadoop-hdfs jar is missing
(I think much of this was broken-build stuff in the SNAPSHOT which was fixed for release)
2. Several artifacts are missing from the -dist archive:
- SDK jar
- Legacy sources
- log4j appender client
This addresses bug FLUME-1032.
https://issues.apache.org/jira/browse/FLUME-1032
Diffs
-----
flume-ng-clients/flume-ng-log4jappender/pom.xml d1c443d
flume-ng-dist/pom.xml f7e0dd9
flume-ng-dist/src/main/assembly/dist.xml afe7a44
flume-ng-dist/src/main/assembly/src.xml 21278dc
flume-ng-sinks/flume-hdfs-sink/pom.xml 76d69a3
pom.xml cf10727
Diff: https://reviews.apache.org/r/4368/diff
Testing
-------
Tested 3 profiles: default (hadoop-0.20.205), -Dhadoop.profile=100 (hadoop-1.0.0), -Dhadoop.profile=23 (hadoop-0.23)
Thanks,
Mike
> 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
>
> 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
[jira] [Commented] (FLUME-1032) Fix / clean up Flume NG build
Posted by "Arvind Prabhakar (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232894#comment-13232894 ]
Arvind Prabhakar commented on FLUME-1032:
-----------------------------------------
Thanks for the patch Mike. Can you also generate a patch for branch-1.1.0 as well? Thanks!
> 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.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
[jira] [Updated] (FLUME-1032) Fix / clean up Flume NG build
Posted by "Mike Percy (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Percy updated FLUME-1032:
------------------------------
Attachment: (was: FLUME-1032-8-branch-1.1.0.diff)
> 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
[jira] [Commented] (FLUME-1032) Fix / clean up Flume NG build
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232888#comment-13232888 ]
jiraposter@reviews.apache.org commented on FLUME-1032:
------------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4368/#review6080
-----------------------------------------------------------
Ship it!
Looks good to me.
- Andrew
On 2012-03-15 21:42:49, Mike Percy wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/4368/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2012-03-15 21:42:49)
bq.
bq.
bq. Review request for Flume.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. Fixing various build issues:
bq.
bq. 1. Maven build against Hadoop 0.23 is misconfigured:
bq. - Referenced Hadoop artifact (0.23-SNAPSHOT) does not exist in central repo (build fails due to this)
bq. - slf4j-jcl gets pulled in, which breaks logging at runtime due to the inclusion of slf4j-log4j12 as well
bq. - downstream dependencies which should be transitively included are explicitly referenced only for hadoop-0.23 (commons-logging and commons-configuration)
bq. - hadoop-hdfs jar is missing
bq. (I think much of this was broken-build stuff in the SNAPSHOT which was fixed for release)
bq.
bq. 2. Several artifacts are missing from the -dist archive:
bq. - SDK jar
bq. - Legacy sources
bq. - log4j appender client
bq.
bq.
bq. This addresses bug FLUME-1032.
bq. https://issues.apache.org/jira/browse/FLUME-1032
bq.
bq.
bq. Diffs
bq. -----
bq.
bq. flume-ng-clients/flume-ng-log4jappender/pom.xml d1c443d
bq. flume-ng-dist/pom.xml f7e0dd9
bq. flume-ng-dist/src/main/assembly/dist.xml afe7a44
bq. flume-ng-dist/src/main/assembly/src.xml 21278dc
bq. flume-ng-sinks/flume-hdfs-sink/pom.xml 76d69a3
bq. pom.xml cf10727
bq.
bq. Diff: https://reviews.apache.org/r/4368/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq. Tested 3 profiles: default (hadoop-0.20.205), -Dhadoop.profile=100 (hadoop-1.0.0), -Dhadoop.profile=23 (hadoop-0.23)
bq.
bq.
bq. Thanks,
bq.
bq. Mike
bq.
bq.
> 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
>
> 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
[jira] [Updated] (FLUME-1032) Fix / clean up Flume NG build
Posted by "Mike Percy (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Percy updated FLUME-1032:
------------------------------
Status: Patch Available (was: Open)
> 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.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