You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Herman Chen (JIRA)" <ji...@apache.org> on 2012/06/21 17:36:43 UTC
[jira] [Created] (BIGTOP-640) Sync up dependency library versions
automatically
Herman Chen created BIGTOP-640:
----------------------------------
Summary: 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
[jira] [Commented] (BIGTOP-640) Sync up dependency library versions
automatically
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426611#comment-13426611 ]
Harsh J commented on BIGTOP-640:
--------------------------------
I think Bigtop, since it packages jsvc independently now, can also ship a bigtop package update out to resolve such bumps?
> 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
> Fix For: 0.5.0
>
>
> 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
[jira] [Commented] (BIGTOP-640) Sync up dependency library versions
automatically
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431330#comment-13431330 ]
Roman Shaposhnik commented on BIGTOP-640:
-----------------------------------------
@Harsh, are you saying we should just bump it to a particular version? Which one do you have in mind?
> 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
> Fix For: 0.5.0
>
>
> 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
[jira] [Commented] (BIGTOP-640) Sync up dependency library versions
automatically
Posted by "Konstantin Boudnik (JIRA)" <ji...@apache.org>.
[ 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