- **status**: review --> in-progress
- **Comment**:

Looking good so far -- just a few things to check into.

1) Make sure Apache licenses are added to new files (if applicable)
2) Make sure the build directory `Allura/allura/public/nf/js/build/` exists 
(maybe add a .gitkeep inside the directory)
3) The package.json could use some additional meta-data.  We can also add 
aliases to many of the scripts we run to make things more intuitive... Maybe 
something like:

~~~~~
::json

  "homepage": "https://allura.apache.org/";,
  "description": "Apache Allura development asset pipeline",
  "bugs": {
    "url": "https://forge-allura.apache.org/p/allura/tickets/";
  },
  "scripts": {
    "test": "tests here?",
    "build": "broccoli build Allura/allura/public/nf/js/build/",
    "web": "gunicorn --paste Allura/development.ini --chdir Allura/"
  },

~~~~~



---

** [tickets:#7976] JSX support**

**Status:** in-progress
**Milestone:** unreleased
**Labels:** sf-current sf-2 
**Created:** Mon Aug 24, 2015 02:54 PM UTC by Dave Brondsema
**Last Updated:** Tue Sep 29, 2015 03:50 PM UTC
**Owner:** Dave Brondsema


We may need JSX support for [#7920]  If so, we'll need to configure things like:

* JSX compiling for development (with minimal dependencies added)
    * step-by-step instructions
    * Docker setup
* script or something to run it for final "production-ready" output
* run that script during `asf-release.sh` so that our releases don't require 
JSX tools to be installed


---

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed 
to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://forge-allura.apache.org/p/allura/admin/tickets/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.

Reply via email to