bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shaposhnik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BIGTOP-98) Ability to force ivy/maven version inter-dependency needs to be implemented
Date Mon, 19 Sep 2011 22:48:08 GMT

    [ https://issues.apache.org/jira/browse/BIGTOP-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108200#comment-13108200
] 

Roman Shaposhnik commented on BIGTOP-98:
----------------------------------------

Ok, here's a bit of investigation I've done as far as the current state of tweakability of
deps is concerned:

1. ant projects (* marks the one that need to be made tweakable):
  1.1. zookeeper -- no explicit dependencies on other stack components 
  1.2. hadoop -- no explicit dependencies on other stack components
  1.3. flume -- no explicit dependencies on other stack components
  1.4. sqoop --  depends on hadoop-core(*), hadoop-test(*), hbase
  1.5. pig -- depends on  hadoop-core, hadoop-test, zookeeper, hbase
  1.6. hive -- quite broken :-(

2. maven projects
  2.1. hbase -- hadoop-core, zookeeper
  2.2. mahout -- hadoop-core(*)
  2.3. oozie -- quite broken :-(
  2.4. whirr -- hadoop-core

Overall, I think we're doing pretty well. I'll try to run a custom build once BIGTOP-100
gets integrated.



> Ability to force ivy/maven version inter-dependency needs to be implemented
> ---------------------------------------------------------------------------
>
>                 Key: BIGTOP-98
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-98
>             Project: Bigtop
>          Issue Type: Bug
>            Reporter: Roman Shaposhnik
>
> We need to have a mechanism in place to be able to force compile-time inter-dependencies
to be within stack of Bigtop components. Currently we rely on whatever projects specify at
release time. This leads to an unfortunate side effect of components compiling against one
version of artifacts and deploying against a different one.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message