> WDYT? The suggestion looks good to me (unsurprisingly ;-)), but if we feel it's too much work at this late stage for something that won't be around for that long anyway, I'd also be OK with dropping the Options object and simply having an ExecutorService argument at the end of the overloaded method.
At the very least, we could decouple the two steps and do the simple method renaming (i.e. dropping "xxxConcurrently") first, then considering the Options refactoring in a separate PR. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-chef/pull/47#issuecomment-49447134
