You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2011/09/16 08:37:09 UTC

[jira] [Issue Comment Edited] (BIGTOP-98) Ability to force ivy/maven version inter-dependency needs to be implemented

    [ https://issues.apache.org/jira/browse/BIGTOP-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105902#comment-13105902 ] 

Konstantin Boudnik edited comment on BIGTOP-98 at 9/16/11 6:36 AM:
-------------------------------------------------------------------

Such on-the fly parametrization of dependencies would be disastrous IMO for it will allow to create stacks with pretty much unknown set of dependent artifacts.

      was (Author: cos):
    Such on-the fly parametrization of dependencies would be disastrous IMO for it will allow to create stacks with pretty much unknown set of dependencies.
  
> 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