You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2014/11/06 01:13:33 UTC
[jira] [Commented] (TEZ-1708) Make UI part of TEZ build process
[ https://issues.apache.org/jira/browse/TEZ-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199428#comment-14199428 ]
Hitesh Shah commented on TEZ-1708:
----------------------------------
Comments:
- Info in tez-ui/README.txt seems more relevant as a section in the top level BUILDING.txt
- tez-ui/pom.xml - fix naming of module using similar approach used in other modules. Why is version 0.0.1 ?
- tez-ui/pom.xml should not have versions for any plugin that is used.
- any reason why the surefire plugin section is copypasted from the top level pom?
- nodeVersion and npmVersion should be properties
- some plugins that are used are new and do not have a version no. specified? Are they meant to be listed in the pluginMgmt section in the top level pom?
- tez-ui/src/assembly/bin.xml does not have a license header
> Make UI part of TEZ build process
> ---------------------------------
>
> Key: TEZ-1708
> URL: https://issues.apache.org/jira/browse/TEZ-1708
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Sreenath Somarajapuram
> Assignee: Sreenath Somarajapuram
> Attachments: TEZ-1708.1.patch, TEZ-1708.2.patch, patch.sh
>
>
> - Ensure that the code base follow maven standards.
> - On build, a web tar and Ambari jar must be created in the target folder.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)