[ALOY-280] Remove alloy.jmk from default projects
| GitHub Issue | n/a |
|---|
| Type | Story |
|---|
| Priority | Medium |
|---|
| Status | Resolved |
|---|
| Resolution | Fixed |
|---|
| Resolution Date | 2012-09-19T08:26:42.000+0000 |
|---|
| Affected Version/s | 2012 Sprint 19 |
|---|
| Fix Version/s | 2012 Sprint 19, Release 3.0.0 |
|---|
| Components | Runtime, XML |
|---|
| Labels | n/a |
|---|
| Reporter | Tony Lukasavage |
|---|
| Assignee | Unknown |
|---|
| Created | 2012-09-19T06:58:22.000+0000 |
|---|
| Updated | 2018-03-07T22:25:37.000+0000 |
|---|
Description
alloy.jmk allows a developer to add pre/post compile hooks for executing javascript code. While powerful, this is likely to very rarely be used. In the cases where it would be used, an advanced developer will have access to documentation on composing these files. Much like Titanium compiler plugins, this does not need to be present by default.
alloy.jmk functionality should remain the same in the compile command, but it should not be added to projects by default. It should be created manually (or perhaps through a generate command) by a developer when needed.
Comments
JSON Source
Removed alloy.jmk from new projects and added
alloy generate jmkcommand