You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Patrick Wendell (JIRA)" <ji...@apache.org> on 2012/07/23 06:07:33 UTC
[jira] [Created] (FLUME-1390) flume-ng-dist produces conflicting
versions of flume-ng jars
Patrick Wendell created FLUME-1390:
--------------------------------------
Summary: flume-ng-dist produces conflicting versions of flume-ng jars
Key: FLUME-1390
URL: https://issues.apache.org/jira/browse/FLUME-1390
Project: Flume
Issue Type: Bug
Reporter: Patrick Wendell
The lib/ directory of the distribution contains both historical and SNAPSHOT flume jars. I ran into this when deploying flume locally to test out changes to the code - the changes weren't visible because the SNAPSHOT jars are shadowed by the 20120706.060402-2 jars.
This can be reproduced from a fresh build:
- Checkout flume
- mvn clean package -Dmaven.test.skip=true
- cd flume-ng-dist
- tar -xvzf apache-flume-1.3.0-SNAPSHOT-dist.tar.gz
- cd apache-flume-1.3.0-SNAPSHOT && ls lib/ |grep flume-ng
flume-ng-configuration-1.3.0-20120706.060402-2.jar
flume-ng-configuration-1.3.0-SNAPSHOT.jar
flume-ng-core-1.3.0-20120706.060403-2.jar
flume-ng-core-1.3.0-SNAPSHOT.jar
flume-ng-hbase-sink-1.3.0-20120706.060426-2.jar
flume-ng-log4jappender-1.3.0-20120706.060421-2.jar
flume-ng-node-1.3.0-20120706.060410-2.jar
flume-ng-node-1.3.0-SNAPSHOT.jar
flume-ng-sdk-1.3.0-20120706.060413-2.jar
flume-ng-sdk-1.3.0-SNAPSHOT.jar
--
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-1390) flume-ng-dist produces conflicting
versions of flume-ng jars
Posted by "Mike Percy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420522#comment-13420522 ]
Mike Percy commented on FLUME-1390:
-----------------------------------
Does this happen when you run mvn clean install -DskipTests ?
> flume-ng-dist produces conflicting versions of flume-ng jars
> ------------------------------------------------------------
>
> Key: FLUME-1390
> URL: https://issues.apache.org/jira/browse/FLUME-1390
> Project: Flume
> Issue Type: Bug
> Reporter: Patrick Wendell
>
> The lib/ directory of the distribution contains both historical and SNAPSHOT flume jars. I ran into this when deploying flume locally to test out changes to the code - the changes weren't visible because the SNAPSHOT jars are shadowed by the 20120706.060402-2 jars.
> This can be reproduced from a fresh build:
> - Checkout flume
> - mvn clean package -Dmaven.test.skip=true
> - cd flume-ng-dist
> - tar -xvzf apache-flume-1.3.0-SNAPSHOT-dist.tar.gz
> - cd apache-flume-1.3.0-SNAPSHOT && ls lib/ |grep flume-ng
> flume-ng-configuration-1.3.0-20120706.060402-2.jar
> flume-ng-configuration-1.3.0-SNAPSHOT.jar
> flume-ng-core-1.3.0-20120706.060403-2.jar
> flume-ng-core-1.3.0-SNAPSHOT.jar
> flume-ng-hbase-sink-1.3.0-20120706.060426-2.jar
> flume-ng-log4jappender-1.3.0-20120706.060421-2.jar
> flume-ng-node-1.3.0-20120706.060410-2.jar
> flume-ng-node-1.3.0-SNAPSHOT.jar
> flume-ng-sdk-1.3.0-20120706.060413-2.jar
> flume-ng-sdk-1.3.0-SNAPSHOT.jar
--
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-1390) flume-ng-dist produces conflicting
versions of flume-ng jars
Posted by "Patrick Wendell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420802#comment-13420802 ]
Patrick Wendell commented on FLUME-1390:
----------------------------------------
Hey Mike,
It looks like things work correctly with {{mvn clean install -DskipTests}}:
$ ls |grep flume-ng
flume-ng-configuration-1.3.0-SNAPSHOT.jar
flume-ng-core-1.3.0-SNAPSHOT.jar
flume-ng-hbase-sink-1.3.0-SNAPSHOT.jar
flume-ng-log4jappender-1.3.0-20120706.060421-2.jar
flume-ng-node-1.3.0-SNAPSHOT.jar
flume-ng-sdk-1.3.0-SNAPSHOT.jar
> flume-ng-dist produces conflicting versions of flume-ng jars
> ------------------------------------------------------------
>
> Key: FLUME-1390
> URL: https://issues.apache.org/jira/browse/FLUME-1390
> Project: Flume
> Issue Type: Bug
> Reporter: Patrick Wendell
>
> The lib/ directory of the distribution contains both historical and SNAPSHOT flume jars. I ran into this when deploying flume locally to test out changes to the code - the changes weren't visible because the SNAPSHOT jars are shadowed by the 20120706.060402-2 jars.
> This can be reproduced from a fresh build:
> - Checkout flume
> - mvn clean package -Dmaven.test.skip=true
> - cd flume-ng-dist
> - tar -xvzf apache-flume-1.3.0-SNAPSHOT-dist.tar.gz
> - cd apache-flume-1.3.0-SNAPSHOT && ls lib/ |grep flume-ng
> flume-ng-configuration-1.3.0-20120706.060402-2.jar
> flume-ng-configuration-1.3.0-SNAPSHOT.jar
> flume-ng-core-1.3.0-20120706.060403-2.jar
> flume-ng-core-1.3.0-SNAPSHOT.jar
> flume-ng-hbase-sink-1.3.0-20120706.060426-2.jar
> flume-ng-log4jappender-1.3.0-20120706.060421-2.jar
> flume-ng-node-1.3.0-20120706.060410-2.jar
> flume-ng-node-1.3.0-SNAPSHOT.jar
> flume-ng-sdk-1.3.0-20120706.060413-2.jar
> flume-ng-sdk-1.3.0-SNAPSHOT.jar
--
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