[
https://issues.apache.org/jira/browse/AMBARI-8583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238262#comment-14238262
]
Hudson commented on AMBARI-8583:
--------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #1130 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/1130/])
AMBARI-8583. Ambari-Web build generates incorrect 'app.js.map' file
(alexantonenko) (hiveww:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2e7b019e300caea925a056b3f4e5a4fcab1fb05e)
* ambari-web/toggle-experimental.sh
* ambari-web/pom.xml
* ambari-web/set-ambari-version.sh
* ambari-web/set-default-stack-version.sh
> 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)
