[
https://issues.apache.org/jira/browse/BIGTOP-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105935#comment-13105935
]
Bruno Mahé commented on BIGTOP-98:
----------------------------------
Andrew> What if we make sure each project does not hardcode versions but uses
properties which define their versions for their dependencies (similar to what
HBase does here https://github.com/apache/hbase/blob/trunk/pom.xml )? We could
then override them.
Konstantin> I believe the goal would be more about ensuring a coherent set of
dependencies and ensuring that inter-dependencies between projects are correct
and respected. For instance, when I build flume packages, maven/ivy would pull
the same versions of zookeeper we distribute and not some other arbitrary one
which may or may not be compatible. Maybe Roman could clarify a little bit more?
We should also check with mentors and Apache people if it would be allowed.
Because of what has been decided during the incubation process, we cannot patch
for security or build issues. And overriding dependencies versions might make
us create artifacts not based on what was voted on for each project (if we want
to be strict about it, which I don't really want to).
Furthermore, we would loose all the testing done by each of these projects. So
we would have the additional burden of proving these changes wouldn't break
anything.
But this seems to be something helpful and worthy to pursue or at least to
think about.
> 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
