|
||||||||
|
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)

You might want to integrate with vim using "mvn process-test-sources" instead. Jetty is configured to present both target/classes and target/test-classes under the one context path.
Perhaps the improvement request needs to be re-worded with respect to enhancing the documentation to show how this can all be used in the context of vim. I think that would be useful. Perhaps you can bed things down and then we can re-visit the request with that in mind?
I appreciate your feedback.