Tomcat deployment is normal, jetty deployment fails

Recently transferred to a project team to help, after the code compiled through the MyEclipse jetty plug-in deployment is not up, and finally helpless only through Tomcat deployment (completion of the task is important).

Now idle, continue to tangle, contrast jetty release and Tomcat release process, the difference is that jetty is directly read Src/main/java after the compiled target directory and directly read the Src/main/resource path under the configuration file, and then publish , while Tomcat copies the Src/main/java compiled target directory and the Src/main/resource configuration file to the WebApps directory and publishes it.

Then look at the jetty release error message, found that the read configuration file path actually has%20 such words,, will not be because the file path in the presence of a space, the attitude of holding a try, re-pull the code (before the SVN project path in the parent directory of the existence of spaces), Ensure that there are no spaces in the local path, compile, publish, find everything OK.

The evil of the space Ah,,,, is again a space pit;