You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Mahadev konar (JIRA)" <ji...@apache.org> on 2013/11/19 18:31:22 UTC
[jira] [Updated] (AMBARI-3567) Make provisions for
ambari-web/public content to be read from a static location
[ https://issues.apache.org/jira/browse/AMBARI-3567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar updated AMBARI-3567:
----------------------------------
Fix Version/s: 1.4.3
> Make provisions for ambari-web/public content to be read from a static location
> -------------------------------------------------------------------------------
>
> Key: AMBARI-3567
> URL: https://issues.apache.org/jira/browse/AMBARI-3567
> Project: Ambari
> Issue Type: Improvement
> Components: build
> Affects Versions: 1.4.1
> Environment: Fedora 19
> Reporter: Trevor McKay
> Assignee: Trevor McKay
> Fix For: 1.4.3
>
> Attachments: static-dir.patch, static-web.patch, update-static.patch
>
>
> Nodejs dependencies add to the number of things that have to be packaged in order to include Ambari in Fedora (and potentially other distributions).
> If the content in ambari-web/public can be added to the Ambari source tree and read from that location by ambari-server at build time, then nodejs will not be a required dependency on Fedora. Static web content can be generated as needed and updated in the Ambari source tree.
> To this end, the current maven build system should support an option to skip the ambari-web module at build time.
--
This message was sent by Atlassian JIRA
(v6.1#6144)