To my knowledge, Dagger does generate code, while Guice and Spring rely on runtime processing, thus Dagger works faster, but requires more work on programmer side. Because of performance edge it's good for mobile (Android) development.
However, when we are left with Guice and Spring, the latter has lots of integrations. What's the point of developing/using Guice, if we can use Spring Framework (that does basically same thing, but offers ex. easier database access)?
Isn't Google trying to reinvent wheel by creating their own DI tool, instead of using (and possibly contributing to) Spring Framework?
I am looking for decision tree, that guides through choosing DI tool.
It's important to realize that Dagger was created after Guice, by one of Guice's creators ("Crazy Bob" Lee) after his move to Square:
javax.injectannotations in October 2009, with heavy input from Google (Bob Lee), Spring, and other industry players.
In that sense, the continued curation of Guice isn't "reinventing the wheel" so much as maintenance on a long-running and widely-consumed software package that thoroughly predates any version of Dagger. To list and amend to the differences you have above:
Beyond that, keep an eye out for maintenance/deprecation patterns and policies among any framework you use, but leave it up to the integrations and performance you need alongside your team's technical judgment.