[ 
https://issues.apache.org/jira/browse/TEZ-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sreenath Somarajapuram updated TEZ-3285:
----------------------------------------
    Attachment: TEZ-3285.4.patch

[~sseth] Please help in reviewing the patch.

-The patch is for migrating to Yarn package manager.
-- It helps to lockdown dependency versions
-- Enabled offline building
- Some of the build time warnings were also removed.
- As pure clean build was taking more than one minute, Im not cleaning the UI 
file caches. -PcleanUICache profile can be used for a pure clean build.

- As Yarn (Latest versions of NPM also) causes the UTs to fail in RHEL6 I have 
added a new profile to use old version of NPM. It can be used by adding 
-PuseNPM into the build command.

> 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. This affects the reliability 
> of the UI build.
> 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.
> Bower:
> Bower doesn't have a hierarchy and this issue can be avoided by locking on a 
> specific version for all dependent package in the bower.json itself.



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

Reply via email to