When developing applications that can be distributed/downloaded from Android Market/Google Play place in more than one flavor, we usually implement the project structure in such a way so that the code is needed only for a particular version that is located inside a package or a module and is completely isolated from the rest of the application. Let's focus on the user story As a developer, I want to maintain in parallel two versions of my application, one feature-limited and a full paid version. We can achieve this isolation by keeping the code needed for the paid version in a different package or in a completely different library. In the following section, we will show you how you can configure Maven to handle both cases and create two different build strategies. If you understand the fundamental concepts and the way we handle in Maven different versions of the same application, then you expand this knowledge to cover more than two versions, for instance, have an...