Arnout Engelen
Arnout Engelen
> Although I agree that the other (not yet reported) split-package issue are not so easy to fix, I think this one can and should be fixed now by renaming...
> @raboof did you get anywhere with this already? I don't think so ;)
> The more conservative approach to the first step would be to deprecate and keep the implementation classes for another version. I think I'd be fine with that...
I guess the question is, in your test situation, why do you want to treat this specific exception specially and not just catch _any_ `Exception`? Perhaps a generic public `ConnectionException`...
Makes sense to remove it here as it is unlikely to break, and when it breaks we will find out when the example in the separate repository breaks :+1:
"Currently the asynchronous clients for Amazon Kinesis, Amazon DynamoDB and Amazon CloudWatch modules in version 2.0 are production ready and can be used in production environments. All other modules are...
I'd understand the "not recommended for production use" on the sdk-for-java developer guide to refer to the latest 2.x version, though, so in this case 2.0.5, right?
Not really part of 'bootstrap' per se, but might be good to cross-link to (and expand) the advice at https://doc.akka.io/docs/akka/snapshot/additional/deploy.html?
Also let's enforce it with https://github.com/akka/akka/blob/master/akka-actor/src/main/scala/akka/AkkaVersion.scala#L22 (though that will fail with a `ClassNotFoundException` before 2.5.9 ;) )
maybe it'd be reasonable to add a context parameter like `?graceful=false` to allow non-gracefully removing the node?