|
||||||||
|
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-1870) [MOSXBUNDLE] Add option... Axel Wienberg (JIRA)
- [mojo-dev] [jira] (MOJO-1870) [MOSXBUNDLE] Add o... Fred Cooke (JIRA)
- [mojo-dev] [jira] (MOJO-1870) [MOSXBUNDLE] Add o... Axel Wienberg (JIRA)
- [mojo-dev] [jira] (MOJO-1870) [MOSXBUNDLE] Add o... Fred Cooke (JIRA)

I take it that you're not using anything with jGit? Symlinks being present in a directory scanned by jGit can/often (always?) cause a long running scan of the target as jGit just treats it as a directory and keeps traversing.
By swallowed, do you mean versioned/tracked/stored or removed/erased/deleted? Also, they don't have to be huge, from what I recall. I'll have a poke around later and provide more detail.
However, a call to create a symlink during the build, and remove it post assembly, should be OK and minimise the chance of it causing headaches with jGit based plugins/apps.
I agree that it should be OOTB behaviour, however it should also be possible to disable it IMO.