[
https://issues.apache.org/jira/browse/BIGTOP-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13106759#comment-13106759
]
Andrew Bayer commented on BIGTOP-98:
------------------------------------
Bruno - I think Roman's talking about being able to, say, do test builds where
we build a pre-release version of Hadoop, and then set all the other components
to depend on that pre-release version we just built.
I think working with the component projects to get overrideable dependency
versions for those dependencies within Bigtop would be part of the right
solution here - we've got that with Ant/Ivy already, and the HBase approach
seems portable to the other Maven projects as well. It's not the best approach
on a purely Maven level - I'm not a huge fan of the indirection of using
property values for one-off dependency versions - but it's functional.
> 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
