Depreciation of alia-all multi module in favor or "pick & choose" and minor ns reorg (spec related)

[mpenet]

• I am very tempted to depreciate releases for alia-all in favor of forcing users to pick and choose manually what they need. I have had to deal a few times with people blindly getting alia-all and have troubles with transitive deps (ex nippy). This ultimately should not cause trouble to anyone.

• right now I can't spec things such as a core.async/channel or manifold deferred because I have no guarantee core.async will be present in the classpath of a user. One solution would be to split specs per "module", either integrated into the module itself, or in a separate modules (for people who still like to use AOT). Not sure about that one yet, but 1 project/module per spec context might be better.

[mccraigmccraig]

no argument from here against deprecating alia-all

[mpenet]

nippy and eaio.uuid modules are gone, all will be next in a future release.