[
https://issues.apache.org/jira/browse/TEZ-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296031#comment-15296031
]
TezQA commented on TEZ-3262:
----------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12805587/TEZ-3262_branch-0.8_1.patch
against master revision 5dd47c6.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1745//console
This message is automatically generated.
> Tez UI : zip.js is not having a bower friendly versioning system
> ----------------------------------------------------------------
>
> Key: TEZ-3262
> URL: https://issues.apache.org/jira/browse/TEZ-3262
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Sreenath Somarajapuram
> Assignee: Sreenath Somarajapuram
> Attachments: TEZ-3262.1.patch, TEZ-3262_branch-0.8_1.patch
>
>
> We are facing build issues in using git SHA with bower.
> - In some environments, on adding a git repo as a direct dependency, we were
> facing issue with bower install.
> - This was happening only while pointing to a specific commit SHA.
> {code}"zip":
> "https://github.com/gildas-lormeau/zip.js.git#bfd76c66293305faaf9fcbb65b5ff7fe2dbe621a",{code}
> - It was observed that if the dependency was a proper bower component that's
> pointing to a specific git tag, the issue wasn't happening.
> {code}"zip-js": "1.0.0"{code}
> So:
> - Create a fork of zip.js
> - Add bower json into the zip.js repo
> - Add a git version tag for bower to use
> This will enable us to use zip.js as other packages with a fixed version
> instead of the git SHA.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
