|
||||||||
|
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] (MEXEC-93) Exec plugin not mar... Archimedes Trajano (JIRA)
- [mojo-dev] [jira] (MEXEC-93) Exec plugin no... radai rosenblatt (JIRA)
- [mojo-dev] [jira] (MEXEC-93) Exec plugin no... Kristian Rosenvold (JIRA)
- [mojo-dev] [jira] (MEXEC-93) Exec plugin no... Kristian Rosenvold (JIRA)
- [mojo-dev] [jira] (MEXEC-93) Exec plugin no... Kristian Rosenvold (JIRA)

@Archimedes The general contract of "threadsafe" does not mean all permutations has to work, it only implies the mojo is safely runnable in a concurrent context.
If a mojo decides to allocate a TCP/IP port, it is up to the mojo to safely find a free port, or for the user to use some mechanism that allocates a port per thread. In the same manner, exec can easily run into concurrency issues (file locking on windows comes to mind), but it does not prevent the mojo from being @threadSafe.
I'll see if I can fix this