So, could think about commons-misc or something? I don’t think we are going to come up with a perfect module for these things.
Maybe the way it can work is: commons-misc exists. It is the landing place for things that seem to be outside the scope of commons-xxxx, but don’t justify a new module or sandbox effort. Things in misc can be reevaluated for inclusion in new modules at things go, and at that point @Depricated out of misc. ? On March 3, 2018 at 00:42:12, Matt Sicker (boa...@gmail.com) wrote: On 2 March 2018 at 13:31, Oliver Heger <oliver.he...@oliver-heger.de> wrote: > > One other suggestion: It was stated in the past that the concurrent > classes are also a bit out of scope for [lang], especially the circuit > breaker implementations. Would it make sense to move those into a new > module, and could this be a home for the watch classes, too? > Considering the amount of retry libraries there are out there, I think it makes perfect sense for circuit breaker libraries to be their own thing, too. See Hysterix for example. -- Matt Sicker <boa...@gmail.com>
