incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shaposhnik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BIGTOP-98) Ability to force ivy/maven version inter-dependency needs to be implemented
Date Fri, 16 Sep 2011 18:47:09 GMT

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

Roman Shaposhnik commented on BIGTOP-98:
----------------------------------------

@Cos

I think I might not have been as clear as I needed to be in my description -- what I'm talking
about is having a functionality in place that would ensure that what we build against and
what we run against is the same set of versioned components. So far, we're actually dependent
on the versioning of dependencies supplied by every upstream component. So lets take our .22
effort as an example -- we would like to bump a Hadoop version to .22 and that's easy. Yet,
things like Pig and HBase will still pull the versions of hadoop-core artifacts that were
recorded in their ivy/maven properties at the time of a component release (definitely NOT
.22). All of this will lead to an unfortunate situation where we are going to build Pig against
0.20.2 and execute against .22.

@Bruno

1. On a technical side -- we have to problems to solve:
   * Making sure that we can make freshly built bits available to downstream parts of the
build as dependencies
   * 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.

2. On a political side -- there's a legitimate problem to be solved here. The problem being
-- we can NOT rely on the version
information recorded as part of the release of leaf-node components, since different customers
will ALWAY have different 
needs. E.g. Pig 0.9.0 is currently released as requiring 0.20.2. Yet there's plenty of customers
who need it to be part
of the stack that has Hadoop 0.20.20X as the basis OR Hadoop 0.21 as the basis, etc.

> 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

        

Mime
View raw message