[
https://issues.apache.org/jira/browse/TEZ-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602826#comment-15602826
]
Sreenath Somarajapuram commented on TEZ-3489:
---------------------------------------------
bq. However, using the cache without checking if the cache matches the actual
requirements is not good.
- "npm install" does that normally. Its just that in some cases we would have
to use -PcleanUICache. Some are follows
-- Where the package name change
-- A different linux user have done a build - we might end up with permission
issues in doing npm install.
-- An npm install failed, and succeeding installs are not able to recover the
dependencies folder.
- Guess we can run "npm prune" also as part of the build, that would remove
packages that are not listed in package.json. Didn't add it initially as it was
slightly adding the build time.
> Tez UI: Dependencies are not cleaned on 'mvn clean'
> ---------------------------------------------------
>
> Key: TEZ-3489
> URL: https://issues.apache.org/jira/browse/TEZ-3489
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.8.3
> Reporter: Sreenath Somarajapuram
>
> On building Tez UI, dependencies are downloaded onto node, node_modules &
> bower_components folder in tez/tez-ui/src/main/webapp. On 'mvn clean' these
> folders are not cleared.
> Ideally these dependencies must be added to target and must be removed with
> target on clean.
> As of now, we need to activate an extra profile for clearing these files :
> -PcleanUICache
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
