[
https://issues.apache.org/jira/browse/AMBARI-3567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trevor McKay updated AMBARI-3567:
---------------------------------
Attachment: static-web.patch
This patch creates a default profile which includes the ambari-web build and
causes ambari-server to read from ambari-web/public during generation of an rpm.
It also adds a new profile "static-web" which skips the ambari-web build and
causes ambari-server to read from ambari-web/static.
(ambari-web/static is just a suggestion for a location, the path for static
content in the source tree could be anywhere)
> 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
> Attachments: static-web.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)
