You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Paul Lindner <li...@inuus.com> on 2010/04/17 03:52:54 UTC

cleaning up web content

I have a patch that doesn't upload nicely to codereview, so I'm sending this
email instead..

I'd like to move the files in javascript to a new top-level directory called
content

This will contain resources that will be loaded at the root level of the
deployment.  Structure will look something like this:

  content/
     index.html (replacing README)
     container/ (with existing content)
     samplecontainer/ (with existing content)
     gadget-specs/ (new)
     sampledata/ (with existing content)

This content was mapped to /gadgets/files previously which was pretty
clunky.

With this in place it allows a cleaner build, and a it allows us to use the
maven plugin jetty:run to do live deployments without building and deploying
a war file.  I've tested with all the existing tests for both java and PHP
and all looks fine.

If no objections I'll commit this late this weekend.