|
||||||||
|
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] (MAPPASM-213) Allow generation of... Petar Tahchiev (JIRA)
- [mojo-dev] [jira] (MAPPASM-213) Allow generati... Petar Tahchiev (JIRA)
- [mojo-dev] [jira] (MAPPASM-213) Allow generati... Dan Tran (JIRA)
- [mojo-dev] [jira] (MAPPASM-213) Allow generati... Petar Tahchiev (JIRA)
- [mojo-dev] [jira] (MAPPASM-213) Allow generati... Petar Tahchiev (JIRA)
- [mojo-dev] [jira] (MAPPASM-213) Allow generati... Dan Tran (JIRA)
- [mojo-dev] [jira] (MAPPASM-213) Allow generati... Dennis Lundberg (JIRA)

Hi Petar, this plugin, the jsw part, is all about JSW. It has not nothing to do with J2EE. This plugin should not be done work on behalf of others. This means you will need some help from other plugins like antrun, resource, dependency, etc to glue things up together.
Regarding log location, currently this plugin hardwire, but configurable, to wrapper.logfile=%BASEDIR%/logs/wrapper.log. it may justify for this plugin to create logs directory, but i am still not comfortable since I believe any sizable project with JSW as one of its plugin will need to so some kind if footprint preparation any way.