[
https://issues.apache.org/jira/browse/BIGTOP-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13106743#comment-13106743
]
Bruno Mahé commented on BIGTOP-98:
----------------------------------
{quote}Making sure that we can make freshly built bits available to downstream
parts of the build as dependencies {quote}
I am not sure to follow. It's very likely an upstream project has already its
artifacts in a maven repository. So they will already be available downstream.
If a project does not publish artifacts for maven, maybe we should focus on
helping projects do that
{quote}Making sure that we can override build dependencies of the downstream
parts of the build to pick up versions that we specify
I'm about to investigate how easy/difficult it'll be to solve both of them.
Feel free to chime in. {quote}
How far can we go? A patch would be perfect so we can separate the build
responsibility from the version specification.
As for the political side, I don't disagree with you, but this is still
something to clear up
> 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
