You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Sreenath Somarajapuram (JIRA)" <ji...@apache.org> on 2017/03/31 20:01:41 UTC

[jira] [Commented] (TEZ-3285) Tez UI: Lock down dependency versions

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

Sreenath Somarajapuram commented on TEZ-3285:
---------------------------------------------

[~Ayappan] With reference to TEZ-3470. Please help in ensuring that with TEZ-3285.4.patch the build works as expected in PPC64.

> Tez UI: Lock down dependency versions
> -------------------------------------
>
>                 Key: TEZ-3285
>                 URL: https://issues.apache.org/jira/browse/TEZ-3285
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Sreenath Somarajapuram
>            Assignee: Sreenath Somarajapuram
>         Attachments: TEZ-3285.1.patch, TEZ-3285.2.patch, TEZ-3285.3.patch, TEZ-3285.4.patch, TEZ-3285_batch-0.8_1.patch
>
>
> All dependencies of tez-ui is having fixed versions. But the dependencies of our dependencies are not. Hence a level down in the dependency tree, the build might be looking for the latest packages in every build. This affects the reliability of the UI build. This must be fixed in both the package managers used by Tez UI - NPM & Bower.
> -NPM:-
> -npm shrinkwrap create a separate JSON from the currently installed packages, and ensure that the complete dependency tree is intact across all the build.-
> Yarn:
> Replace NPM with Yarn. Yarn is a package manager developed to solve this issue and many more.
> Bower:
> Bower shrinkwrap resolver plugin can be used to lock the dependency versions.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)