Record an error report, solve the experience, rely on repetition

There are several cases of this type of error reporting , When I met this time module The same class inside depends on multiple times .

1、 For example, the duplicate package is A.B rely on A,C Also depends on A,D rely on B and C and A. So here's the practical solution D The problem of repeated dependence . therefore B Medium A and C Medium A Need to use implementation To rely on . such D There will be no dependency repetition .D Dependency in A It can be used api perhaps implementation All right . In general, this is the case , This A It's kind of like public api 了 . For public api I personally think it can be similar to that kind of Google Library , Use both directly implementation That's it . Or set up a public module, The libraries inside are all based on api Form dependent provision .

Here is a confusing place .

B api A , C implementation D.

If D implementation B：D have access to A,C Out of commission B.

D api B： D have access to A,C Be able to use B.