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

Hudson commented on AMBARI-8583:
--------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit-docker #663 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/663/])
Revert "AMBARI-8583. Ambari-Web build generates incorrect 'app.js.map' file 
(alexantonenko)" (sgunturi: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ddbd346c2a764c0a8938367decf85ab5abcb52a0)
* ambari-web/toggle-experimental.sh
* ambari-web/set-ambari-version.sh
* ambari-web/set-default-stack-version.sh
* ambari-web/pom.xml
AMBARI-8583. Ambari-Web build generates incorrect 'app.js.map' file - no map 
files. (srimanth) (sgunturi: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=685f9dd7313a85e9adf90c23824bdf9fea887b9a)
* ambari-web/config.coffee


> Ambari-Web build generates incorrect 'app.js.map' file
> ------------------------------------------------------
>
>                 Key: AMBARI-8583
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8583
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 1.7.0
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8583.patch, AMBARI-8583_2.patch
>
>
> Ambari-web builds have always generated an {{app.js.gz}} file and a 
> {{app.js.map}} file. The {{app.js.map}} file should provide a map of where 
> individual JS files are located in the single {{app.js}} file. 
> However these mappings are always wrong. Every UI debug session starts out by 
> removing this {{app.js.map}} file. We should either fix the builds so that 
> the correct map file is generated, or we should just get rid of the mapping 
> file if it serves no better purpose.



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

Reply via email to