You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Srimanth Gunturi (JIRA)" <ji...@apache.org> on 2015/01/06 01:23:35 UTC

[jira] [Reopened] (AMBARI-8583) Ambari-Web build generates incorrect 'app.js.map' file

     [ https://issues.apache.org/jira/browse/AMBARI-8583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Srimanth Gunturi reopened AMBARI-8583:
--------------------------------------

Reopening issue.
The problem with current change is that it changes source, which show up as outgoing changes. Hence reverting the change.
Another way to fix this is to not generate the map files at all.

> 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-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)