[ 
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
                static-web.patch

Tweaked these patches

1) the static web dir is now ambari-web/public-static per a suggestion from 
Yusaku.  The directory will be created if it is not there when the special 
profile is used.

2) The profile name for copying from public to public-static is "update-static" 
with a dash instead of an underscore.  So:

mvn -P update-static -X compile

3) Note there was an earlier patch that has been deleted which created the 
static directory in the source tree.  That was unnecessary and has been removed.

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

Reply via email to