Cannot apply into multi-modules project about deeplinkdispatch

[felipecsl]

This didn't really work well since there is no way to know where the annotation will be generated. Reopening until we have it actually fixed.
I think the best way to go about it is to always enforce the the @DeepLinkHandler annotation somewhere and just have the generated classes be based on the annotated one

[nimengbo]

@felipecsl Hey guys, I already test this case used @DeepLinkHandler, And in multi-module with DeepLink, It's all green .
What's the problem in this issue answer?

[felipecsl]

@nimengbo the problem is that having @DeepLink annotations in multiple modules would cause DeepLinkDispatch to generate multiple duplicated classes, since it would generate one DeepLinkActivity for each module and they would all have the same package and same name.
SInce you can't have 2 classes with the exact same name and package name, the dexer would fail with duplicate class definition error.

[felipecsl]

Fixed in 3.0.0-rc1