|
||||||||
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-212) Install dependencies... Petar Tahchiev (JIRA)
- [mojo-dev] [jira] (MAPPASM-212) Install depende... Petar Tahchiev (JIRA)
- [mojo-dev] [jira] (MAPPASM-212) Install depende... Dan Tran (JIRA)
- [mojo-dev] [jira] (MAPPASM-212) Install depende... Petar Tahchiev (JIRA)
- [mojo-dev] [jira] (MAPPASM-212) Install depende... Dan Tran (JIRA)
- [mojo-dev] [jira] (MAPPASM-212) Install depende... Petar Tahchiev (JIRA)
- [mojo-dev] [jira] (MAPPASM-212) Install depende... Petar Tahchiev (JIRA)
- [mojo-dev] [jira] (MAPPASM-212) Install depende... Dan Tran (JIRA)
Again, same thing as https://jira.codehaus.org/browse/MAPPASM-213
My oppinion is that this is a one-line FEATURE that the Maven Appassembly plugin could provide. I know this could be achieved with maven antrun plugin or exec plugin, but why do we have the APPASSEMBLY in first place? The whole JSW generation I could do with antrun plugin or exec plugin!!
I could provide with a test-case if the team decides to incorporate this feature.