Mailing-List: contact issues-help@aurora.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.incubator.apache.org
Date: Mon, 8 Sep 2014 19:28:30 +0000 (UTC)
From: "Chris Lambert (JIRA)" <jira@apache.org>
To: issues@aurora.incubator.apache.org
Message-ID: <JIRA.12738699.1409718518000.19301.1410204510575@Atlassian.JIRA>
In-Reply-To: <JIRA.12738699.1409718518000@Atlassian.JIRA>
References: <JIRA.12738699.1409718518000@Atlassian.JIRA>
 <JIRA.12738699.1409718518335@arcas>
Subject: [jira] [Updated] (AURORA-678) Serve static HTTP assets out of a
 classpath directory
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AURORA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Lambert updated AURORA-678:
---------------------------------
    Sprint: Q3 Sprint 2

> Serve static HTTP assets out of a classpath directory
> -----------------------------------------------------
>
>                 Key: AURORA-678
>                 URL: https://issues.apache.org/jira/browse/AURORA-678
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>            Reporter: Bill Farner
>            Assignee: Bill Farner
>
> Static asset registration with our HTTP server is somewhat complicated, requiring a manual mapping to be made from the request to match, and the classpath entry to serve.  Jetty has built-in support for serving static assets out of a directory on the classpath, which would reduce all of our asset binding code to a few lines.  It also opens the doors to easy extension of the web interface at runtime by adding to the classpath, and would also reduce iteration time when developing the web interface.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)