*, svn client project upload and deployment
Premise: I am using the plug-in svn configured in MyEclipse, the IDE Step 1: The current project disconnects the previous svn connection Step 2: The current project share project Step 3: The path of the url is the root directory of the current project, pay attention to the root directory In other words, the current project as a whole is uploaded to svn Step 4: Use the project name as the folder name or rename it Step 5: Add a comment finish Step 6: Right-click on the current project to synchronize with the resource library and then submit the target file Step 7: There may be a red conflict in the project root directory after completing the above operations Step 8: Right-click on the current project to synchronize -> Overwrite/Update Step 9: The current project is resynchronized and then submitted to the root directory
*, Bugs that should not appear there - (No bean named 'sessionFactory' is defined)
First of all: If the configuration in the conventional framework configuration file is correct, and you can indeed find the bean that the bug reports cannot be found, then look down; Then: the project is thoroughly cleaned up: all files in the classes folder under web-inf, clean in IDE, remove under Tomcat deployment, and files that are not needed for work under the Tomcat folder under the physical path can be deleted if you don’t want them. delete, delete Next: Check whether the jdk version in the project's java compliance is consistent To sum up: It can be seen here that the cause of the problem is the cache rather than the bug of the project itself, ahaha
*, the difference between overwrite/update and update
overwrite/update Abandon local files and force update the latest version of files on svn renew Update content on svn that doesn't already exist locally but local content remains
Remark:
Since the .classpath and .project files were abandoned when uploading, other members need to select "check out as a new project" when downloading the project to generate the above two files by themselves (PS: You can also copy and modify them from other places) , you need to pay attention to the project type of the project, such as java project, java web project, etc.
*, modify the original url of the project in svn
Due to the company changing servers and other problems, you may encounter svn address changes, there are many ways For example, the svn resource library is directly relocated by right-clicking; If the above method fails, you can modify the url field in the resposibilil table in wc.db in the project path, haha I didn't write it in detail this time, if you have any questions, you can @ me, hehe
*, migration, migration of the entire project, migration with svn information
In a job handover, because the functional code that has been written cannot be launched in time, it needs to be handed over directly to other colleagues. After all, practice brings out true knowledge. result? Of course it works, haha However, when copying the project file from the local machine to the virtual machine, it always prompts an exception of 200 type, and then I guess whether it can be packaged as a compressed package, but I didn't expect that it is not only possible, but also the speed is simple and cool.
*,Accident
Once I encountered a case of win10 sharing failure, after reading it, Daniel guessed that the software caused the abnormal sharing function of win10, so the software should be used with caution (the problem will be updated after verification-November 28, 2017 16:13:14 , currently need to share using ftp, see http://lbovinl.iteye.com/blog/2401144)!