On the importance of engineering structure design

The original intention of writing this article is due to a task today: to replace Baidu live with CC live.

We use as development, there are 3 projects, all in one project, naturally dependent libraries are also a bunch of piles.

CC Live Integration Well, I want to put Baidu live. Java and resource files to kill, so the problem came, I put. Java killed, related resources file too many, I do not know which is Baidu, want to delete, not to do. However, if the first Baidu live to make a libary, and then want to remove the directly delete the dependent library on it, how refreshing!

Think of a project will refer to a lot of jar and so library, all placed under a libs, bound to see clutter. And then another project, you have to copy the jar package.

Can multiple running module fit in a project????

。。。 Various scenarios tell us to create a dependent library

What to look for when creating a dependent library:

1. MINSDK to be consistent with the project

2. Note that the jar packages between the different libraries cannot have the same, otherwise there will be multidex exceptions. If you can't avoid it, add Multidex = True in Gradle.

3. 
   

This article is from the "line of the World" blog, please be sure to keep this source http://4259297.blog.51cto.com/4249297/1784585

On the importance of engineering structure design