Summarize the problem of the day that happened today. Angry fire 1. First eclipse, after changing the JDK, my ecplise incompatible with JDK7, but I go to the official website is always under the right version, the result is the wrong page, did not know which eclipse which version corresponds to which name
2. Then the MAVEN setting.xml configuration did not change, the result eclipse an update will all of my configured configuration to restore all, people crazy AH (copy of today's project is this situation, let people spit blood, but I configured it right)
3. The Web project will not be published automatically after the modification, this is really, put all the configuration looked over and over again, absolutely right, almost angry cry, Then I see validate has been verifying the springmvc.xml, look at the annoyance, the validation of the XML turned off, the results of the problem solved, in order to prove that this is the reason for the ghost check, I opened the check, sure enough, and can not be automatically released.
In short, today a lot of bad day, let people my chicken fly dog jump, pain so I tidied up a new JDK after a possible problem 1. After modifying the environment variable, java-version is still the original old JDK, Baidu has all the means, delete the system32 below all Java.exe Javaw.exe file, can succeed pass; if not, modify the registry, Baidu also has the method, restart and try again, you can succeed on the pass; Maybe when you were with the old version of the JDK, the path was less than a few environment variables, causing the entire JRE folder to be copied below the C drive. Of course, this is a person guessing, if you try to do all the work, open the Task Manager, look at your Java process file path, find it, delete. At this time, in the run Java-version may report the lack of system file errors, you can go back to the environment variables, the path, all the Java variables on the top, I do not know why, anyway successfully solve the problem. 2.ecplise may not be compatible, when you in accordance with the Baidu hint, repeatedly set up Eclipse.ini file still can't run up, did not report JDK mismatch error, but always let you see a log file, open a look inside is not understand the exception, regardless of, You should consider whether your eclipse supports your JDK, you can find a Reademe folder in the Eclipse folder, open a document in it, check the document, and it will tell you the supported JDK, Now the latest series of oxygen series corresponds to the 4.7 version, the previous neon is 4.6, 4.6>= only support JDK 1.8, that is, you want to use JDK1.7 you can download up to 4.5 of the Mars series 3. Eclipse can come in, the first thing is to configure the basic things (in my personal habits as an example) (1) Configure the text size, (2) Configure the various file character encoding and ; (3) The default encoding of the configuration item and (modified in Peference--general--workspace), (4) then the new runtime Evrionment, (5) Create a new server, set the basic configuration of the server, for example, the location of the release, Publishing the rules, the other configuration picking bar, these two are still more important; (6) in the configuration of preference, it is strongly recommended that the validation of the XML close, deceptive things, check with a DTD; (7) Be sure to remember maven. Setting.xml settings changed, or there is a strange strange error (8) You can create a new JSP template,The original template is to use the system's default encoding and can create a new utf-8 template 4. Well, the basic configuration, you can create a new test project to verify that the environment is completed (in the case of Springmvc) (1) Copy project has been a problem, dare not copy, Or a new MAVEN--->web project, OK, there is nothing wrong to solve the error, generally missing Java and test two source code folder, the server is generally not bound, it is possible that the JRE will also error (2) Copy template configuration file, need to change the configuration has, Log4j.xml,spring,xml,springmvc.xml, change the package name is good, the database changed, Db.properties also need to modify (3) Copy Web. xml file, must not forget, there is a version= "3.0" must have, otherwise you can not modify the org.eclipse.wst.common.project.facet.core inside the configuration, check the front-end links must also need a central forwarding class. Above the test finished, you can put eclipse into use, in fact, no accident, the environment is only the transplant is not change, directly packaged in the new building, and maintain the same configuration (path), you can, Eclipse, maven warehouse, MySQL, And so on can directly copy the past, MySQL may also need to do a bit of basic configuration just fine. above purely personal opinion, if there is improper, you big brother adults have a lot of
What to do with a new eclipse, about the murder of a different JDK
