|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [mojo-dev] [jira] (MJS-49) Enable ability to hot-d... Travis Webb (JIRA)
- [mojo-dev] [jira] (MJS-49) Enable ability to ... Travis Webb (JIRA)
- [mojo-dev] [jira] (MJS-49) Enable ability to ... Travis Webb (JIRA)
- [mojo-dev] [jira] (MJS-49) Enable ability to ... Christopher Hunt (JIRA)
- [mojo-dev] [jira] (MJS-49) Enable ability to ... Christopher Hunt (JIRA)
- [mojo-dev] [jira] (MJS-49) Enable ability to ... Travis Webb (JIRA)
- [mojo-dev] [jira] (MJS-49) Enable ability to ... Travis Webb (JIRA)
- [mojo-dev] [jira] (MJS-49) Enable ability to ... Travis Webb (JIRA)
- [mojo-dev] [jira] (MJS-49) Enable ability to ... Christopher Hunt (JIRA)
- [mojo-dev] [jira] (MJS-49) Enable ability to ... Travis Webb (JIRA)
- [mojo-dev] [jira] (MJS-49) Enable ability to ... Christopher Hunt (JIRA)

So I have to directly edit the deployed code in target/classes, even though the version-controlled code, by design, is in src/main/js? That makes no sense at all. Moreover, this not the way other plugins of this type are designed. The GWT plugin, for example, allows you to make changes to your Java code in src/main/java and automatically hot-deploys changes.
Please tell me I've misunderstood something and it isn't this bad...