Yes, since there is no possibility for the Mojo to reserve ports until they are really used, ports may be used by other processes. And I see this situation occurs very often since when a process requests a port, OS usually gives the same ones (at least it is the case on our CI server).

The patch only guarantees to block ports until they are all identified (i.e. opened and saved as property). This step should be very quick so I must admit I don't get the point here (even if I understand it's better than before).

Maybe I don't use this feature as planned originally, but it's now working great with a quick & dirty patch.

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
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Reply via email to