In the SVN version control, novices often encounter this problem:
1, while the entire project will be submitted with bin, gen, .project submitted together to the server
2, to avoid submitting compiler, and other local configuration file separately in the project to src , res submit, however, the project is still to have not submitted documents state
3, since the bin mechanism is to remove all of its content recreate the compiled file, resulting in svn conflict, abnormal
solution is simple:
case 1: Creating the initial project
directly to the bin, file gen, .project and so do not need to submit a unified version and join ignore list
Scenario 2: You have to develop medium-term, project applications
1, has been conflict
will clean up project to restore the original version, will then update and harmonize their svn join ignore list submit
2, common path
to restore or update to the svn version after adding unified ignore list
after performing a skip control in myeclipse or windows interface TortioseSVN tool can be directly submitted to the whole project will not affect the compiled files.
PS
1) TortioseSVN tool, right-List the ignore the Add
2) Android project proposals ignore: .settings, bin, gen, .project