incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Boudnik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BIGTOP-640) Sync up dependency library versions automatically
Date Fri, 22 Jun 2012 05:56:42 GMT

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

Konstantin Boudnik commented on BIGTOP-640:
-------------------------------------------

The point of the BigTop is to produce traceable and predictable sets of components. Thus,
providing dynamic versions tracking would do more harm than good.

I'd suggest to close this.
                
> Sync up dependency library versions automatically
> -------------------------------------------------
>
>                 Key: BIGTOP-640
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-640
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: General
>            Reporter: Herman Chen
>
> Currently BigTop hardcodes the versions of dependency libraries to use, e.g. https://svn.apache.org/repos/asf/incubator/bigtop/trunk/bigtop.mk
uses 1.0.10 for jsvc.  Let's say hypothetically that HDFS fixes a bug by bumping it to 1.0.11,
then BigTop would have to be updated manually to reflect that.  I can imagine scenarios where
a static definition in BigTop is desired, but a way to automatically pick up the projects'
dependencies seem valuable.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message