|
||||||||||||||
|
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] (MOJO-1872) [MOSXBUNDLE] mvn clean ... Fred Cooke (JIRA)
- [mojo-dev] [jira] (MOJO-1872) [MOSXBUNDLE] mvn c... Fred Cooke (JIRA)
- [mojo-dev] [jira] (MOJO-1872) [MOSXBUNDLE] mvn c... Fred Cooke (JIRA)
- [mojo-dev] [jira] (MOJO-1872) [MOSXBUNDLE] mvn c... Fred Cooke (JIRA)
- [mojo-dev] [jira] (MOJO-1872) [MOSXBUNDLE] mvn c... Fred Cooke (JIRA)
- [mojo-dev] [jira] (MOJO-1872) [MOSXBUNDLE] mvn c... Mark Struberg (JIRA)
- [mojo-dev] [jira] (MOJO-1872) [MOSXBUNDLE] mvn c... Fred Cooke (JIRA)

I was wrong! That didn't solve it. What did though, is this:
chflags -R nouchg target/finalname/name.app
This should be added after the other operations in order to prevent bad behaviour both by maven during clean and on other systems post install.
Patch coming soon.