[ https://issues.jboss.org/browse/JBIDE-15495?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15495: ------------------------------------- As a summary of what's going on here, the provided PRs were committed to both master and branch. However, it was revealed that the openshift server actually needs a full workspace lock, due to code in egit, and so this improvement is completely impossible for openshift. Sorry guys. On the bright side, the improvement will be working in all OTHER astools servers :D So ASTools Servers will be much more efficient with workspace locking now! (yay!) But this issue is essentially rejected or marked until later, since egit requires the workspace lock. See CommitOperation#execute(). I feel this could be optimized such that egit could only lock the projects that share a repository with the repo being committed, but, even if it did that, that set of projects may still be larger than the set of projects with modules being published, so... we'd still have to end our rule and let their rule take over for the commit and push portions. For now it makes sense that openshift requires a workspace lock., bc the egit methods do too. But if egit ever optimized, then we should optimize in kind. -- 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