Eclipse Error Troubleshooting

I. Resolving the Cannot open git-upload-pack problem in the Git plugin in Eclipse

Sometimes when you use plug-ins on eclipse to synchronize code with Egit on GitHub or OSC, there are times when cannot open git-upload-pack is a problem.

The general cause of this problem is two: first, network problems, network access to the Internet will always appear a variety of instability factors. Second, eclipse in the Egit plug-in configuration issues.

The first problem is solved by itself, and not much is said.

2nd: Configuration issues.

Open Windows-->preferences-->team-->git-->configuration-->user Settings in Eclipse. Then click Add Entry to create a new key value pair , enter http.sslverify=false.

Then make sure that git can pull and push normally.

The premise is that you can access https://github.com/or https://bitbucket.org/with your browser.

2.eclipse New Installation First start error: Java was started but returned exit code=13 ...
This is due to inconsistencies between the JDK and the number of bits in Eclipse and the computer, either 32-bit or 64-bit.

3. Introducing the MAVEN project into a new Eclipse space: project build error:non-resolvable pom:could not find ...
Just re-update MAVEN's setting file.

4.Eclipse There is no Src/main/resources folder solution under the MAVEN project created with the Maven-archetype-quickstart framework.

Select Project Right-click New, Source folder---fill in the folder name with the Src/main/resources

5. After importing Hibernate core, it is still not possible to eject the configuration class quickly.

Manually write import Orgorg.hibernate.cfg.Configuration

The input section will automatically prompt you.

Note: Other classes cannot be automatically prompted or can be resolved like this

6.No compiler is provided in this environment. Perhaps is running on a JRE rather than a JDK?

Because Eclipse is run on the JRE by default, some features of m2eclipse require the use of the JDK.
workaround 1. Window > Preferences > Java > Installed jres add JDK.

workaround 2. Configure the Eclipse.ini file for the Eclipse installation directory, and in front of the-vmargs parameter, add the VM configuration to the JDK. For example:
--launcher.appendvmargs
-vm
%java_home%\bin\javaw.exe
-vmargs
-dosgi.requiredjavaversion=1.6
-xms40m
-xmx512m

7.web.xml is missing and <failOnMissingWebXml> are set to True

At this point you need to right-click the project-->java EE tools-->generate Deployment descriptor Stub. The Web. xml file is then added to the Src/main/webapp/web_inf file. Error Resolution!

Of course, this approach is for Web project solutions, if your project is not a Web project, then there is another solution, is to configure the Pom file failonmissingwebxml. The specific configuration is as follows:

<build>  <plugins>   <plugin>    <groupid>org.apache.maven.plugins</groupid >    <artifactId>maven-war-plugin</artifactId>    <version>2.6</version>    < configuration>     <failOnMissingWebXml>false</failOnMissingWebXml>    </configuration>   </plugin>  </plugins> </build>

Eclipse Error Troubleshooting