Android Project SVN code management issues

With the SVN control version, SVN itself does not recognize what to pass, which should not, which leads to some things about the path (such as the path to expand the jar) is also uploaded, and when others download, the path for the person may not exist, project compilation will be problematic. The SVN plugin was installed with Eclipse, and the Android project could not be transmitted on a single brain.

Android projects have the following file contents that do not need to be added to version control:

• Bin directory
• Gen Catalog
• . classpath file
• . project file

To block them in eclipse, you need to do this:

1. Click on Window-Preferences
2. Select Team--ignored Resources
3. Click on Add Pattern and enter "Bin"
4. Click on Add Pattern and enter "target"
5. Click on Add Pattern and enter "M2-target"
6. Click on Add Pattern and enter "GEN"
7. Click on Add Pattern and enter ". Classpath"
8. Click on Add Pattern and enter ". Project"
9. Click on Apply and then OK

This will automatically block out when you submit it later, and it will not be updated.

Another problem is that every time the compilation, eclipse will be in the SRC directory of Things to the bin, so. SVN will follow in, so that even if the bin is blocked, but there is a problem with SVN, the workaround:

Menu-Project-properties-java Build path-source-xxx/src-excluded, double-click or edit on the right, add "**/.svn/**" to exclusion patterns and let EC Lipse ignore the. SVN directory.

Reproduced above: http://www.cnblogs.com/CSU-PL/p/3221122.html

Personal advice: Remove the filter for the following files when configuring.

. classpath file

. project file

Otherwise in the checkout, there will be some problems, need to manually configure

Android Project SVN code management issues