[
https://issues.apache.org/jira/browse/AMBARI-3567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trevor McKay updated AMBARI-3567:
---------------------------------
Attachment: update-static.patch
The update-static.patch modifies the ambari-web/pom.xml so that if the
updateStatic environment variable is "true", maven will copy ambari-web/public
to ambari-web/static at the end of the "compile" phase.
Default is false.
So, if a dev is working on static content, just set the -DupdateStatic from the
mvn cli on every build or get things right then run
mvn -X compile -DupdateStatic=true
in the ambari-web subdirectory once before checkin.
> 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-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)
