ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chad Roberts (JIRA)" <>
Subject [jira] [Commented] (AMBARI-3567) Make provisions for ambari-web/public content to be read from a static location
Date Thu, 24 Oct 2013 19:08:02 GMT


Chad Roberts commented on AMBARI-3567:

I made the comment on #apacheambari, but I'll make it here for completeness.

It seems like the current patches would require an undesirable extra step (and remembering
to take the extra step) by contributors making changes to the web directory sources.  Ideally,
there would be a little bit more automation built-in here.  Maybe always building with the
update-static flag turned on, but having that flag be a bit smarter so that it wouldn't unnecessarily
touch any static files that were unchanged.

> Make provisions for ambari-web/public content to be read from a static location
> -------------------------------------------------------------------------------
>                 Key: AMBARI-3567
>                 URL:
>             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
> 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

View raw message