Version Control and Android Library Projects

When using the Android Library Project, does anyone have a good version control solution for projects that use these libraries?

For example, if I have two applications, say, a free version and a paid one, a phone or tablet or any other script, and I want them to use some shared library that is contained in the Android Lib Project, how can I safely add these projects to Svn? Since they are separate projects, I do not know what I know when someone commits another (library).

I am using Eclipse with the Subclipse SVN plugin, does anyone know if there is a way to link projects, so that fixing on one will transmit to the other?

Any advice here would be welcome - since I'm relatively new to SVN - maybe that is not the way to think about it :)

thank

+5
source share
2 answers

You cannot ensure that both of them are fixed at the same time (this is not how SVN works), but you can still do it (according to the words big stones say, using Ctrl + Click or putting them both in a working set, and doing this).

The way Android libraries are really wrong is one of the reasons for this.

+5
source

, Subclipse, , lib ( ctrl-click), "" , .

, , lib, , , . , , lib "" , .

+1

All Articles