[
https://issues.apache.org/jira/browse/BIGTOP-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143280#comment-14143280
]
Roman Shaposhnik commented on BIGTOP-1456:
------------------------------------------
I've been thinking about the sam issue for quite some time in a more general
context: it would be useful to provide a full graph of dependencies between
Bigtop components (not just ZooKeeper and Hadoop). My initial attempts of
automating it sort of failed, but that was before most of the projects moved to
Maven. With Maven it should be way easier, but still I believe we would be
better off maintaining it semi-manually.
Note that in the ideal world the same dependency graph information will also be
baked in package code AND packages would depend of jars present in other
packages instead of shipping copies of JARs. We already to that in a few
places, but spending an effort to regularize it even more would be really
appreciated.
Finally, even if do all of that, it will still not solve a problem of parallel
builds performed on different slaves, but perhaps we can at least check for
dependencies being present in .m2, etc. Or something (I'm totally looking for
suggestions).
> zookeeper should build before hadoop
> ------------------------------------
>
> Key: BIGTOP-1456
> URL: https://issues.apache.org/jira/browse/BIGTOP-1456
> Project: Bigtop
> Issue Type: Bug
> Components: build
> Affects Versions: 0.8.0
> Reporter: stanley shi
>
> Currently in the big 0.8 branch, if two components are specified to be built,
> the order of the components will be the same as the occurrence in the
> bigtop.mk file;
> Now in bigtop.mk, hadoop occurs before zookeeper;
> But hadoop build actually has dependency on zookeeper; from any perspective,
> zookeeper should build before hadoop;
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
