[
https://issues.apache.org/jira/browse/BIGTOP-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105781#comment-13105781
]
Andrew Bayer commented on BIGTOP-98:
------------------------------------
This is actually pretty tough to do without patching the underlying components
- I think we may be able to get away with passing properties to Ant/Ivy builds
to force new versions for dependencies without actually editing any files, but
off the top of my head, I'm not sure there's a way to do that with Maven.
> 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
