hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5504) [YARN-3368] Fix the YARN UI build
Date Fri, 19 Aug 2016 17:47:20 GMT

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

Wangda Tan commented on YARN-5504:
----------------------------------

Thanks for explanations, [~Sreenath].

I think it will be fine to leave some options to developers to say keep node_components and
bower_components, and also, it gonna be very important to make sure all untracked files generated
by build process will be removed after run "mvn clean". For example, we cannot add node_component
and bower_components gitignore file from all branches. That causes issue if a developer switch
to a different branch.

I would like to propose one solution: can we cleanup npm_components, etc. by default, and
have an option (like -Dkeep-yarn-ui-build-files) to explicitly tell mvn to keep these temporary
files. Sounds like a plan? [~sunilg].

For npm-cached: does it store files in a default location such as ~/.npm? Just like maven,
we will store downloaded files to local ~/.m2, this cannot solve all the issues, but can speed
up the whole build since it doesn't need to re-download dependencies.

For unit test, not quite sure when the issues will be triggered. What does the "cache proxy"
means? Is the "cache proxy" enabled by default? And what efforts needed for enable hinting?

Thanks



> [YARN-3368] Fix the YARN UI build
> ---------------------------------
>
>                 Key: YARN-5504
>                 URL: https://issues.apache.org/jira/browse/YARN-5504
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Sreenath Somarajapuram
>            Assignee: Sreenath Somarajapuram
>         Attachments: YARN-5504-YARN-3368-0001.patch
>
>
> - Disable tests as we don't have UTs.
> - Disable lint & hint as they are not followed by the current codebase, and are throwing
build errors.
> - Disable clearing of UI package on building, so that n/w is required only in the first
build.
> - Remove duplicate bower installs.
> - Change the default packaging.type to 'war' as our UI is a Web application- - Will keep
it in the profile
> - Final war should just contain the end result of the build and not all files-
> [~wangda] [~vinodkv] [~sunilg] please share your thoughts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message