[
https://issues.apache.org/jira/browse/BIGTOP-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176874#comment-13176874
]
Bruno Mahé commented on BIGTOP-316:
-----------------------------------
Matt, I believe Roman was aiming at contributors being able to mix and match
versions, not really users. I don't see how users would be able to do so and I
personnaly see Bigtop as a coherent stack instead of a kit to build stacks
(although nothing prevent anyone from selecting their own favourite downstream
versions).
Even if Bigtop would not specify any version in dependencies sections, there
would still work needed to make sure components compile against each others
(for instance, doing a maven build on hbase, would pull hadoop from its default
profile, not the one we want to exercise, so the way a component is build may
have to be tweaked) as well as testing their integration.
But mixmatching is only one of many benefits
> split up hadoop packages into common, hdfs, mapreduce (and yarn)
> ----------------------------------------------------------------
>
> Key: BIGTOP-316
> URL: https://issues.apache.org/jira/browse/BIGTOP-316
> Project: Bigtop
> Issue Type: Sub-task
> Components: General
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.3.0
>
>
--
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
