Bigtop
  1. Bigtop
  2. BIGTOP-640

Sync up dependency library versions automatically

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: General
    • Labels:
      None

      Description

      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.

        Activity

        Hide
        Konstantin Boudnik added a comment -

        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.

        Show
        Konstantin Boudnik added a comment - 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.
        Hide
        Harsh J added a comment -

        I think Bigtop, since it packages jsvc independently now, can also ship a bigtop package update out to resolve such bumps?

        Show
        Harsh J added a comment - I think Bigtop, since it packages jsvc independently now, can also ship a bigtop package update out to resolve such bumps?
        Hide
        Roman Shaposhnik added a comment -

        @Harsh, are you saying we should just bump it to a particular version? Which one do you have in mind?

        Show
        Roman Shaposhnik added a comment - @Harsh, are you saying we should just bump it to a particular version? Which one do you have in mind?
        Hide
        Konstantin Boudnik added a comment -

        I believe jsvc isn't just a dependency library: it is a component of the Bigtop much like tomcat, etc. So, I don't see why we need to make such a change for one component and not the others? Perhaps, a better way of packaging jsvc should be devised instead?

        Show
        Konstantin Boudnik added a comment - I believe jsvc isn't just a dependency library: it is a component of the Bigtop much like tomcat, etc. So, I don't see why we need to make such a change for one component and not the others? Perhaps, a better way of packaging jsvc should be devised instead?

          People

          • Assignee:
            Unassigned
            Reporter:
            Herman Chen
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:

              Development