I'd guess the problem is the length of the commandline that is generated by Eclipse when you run the project. Like Eugene said, if you open the debug view (not debug the project), you can right click on the process and look at its commandline. You can open the debug view by going to window -> show view -> other... debug/debug
I'd guess it is only a problem on this computer because of the directory structure is deeper than on your other computers. youhaodeyi wrote: > > The "running this project" means run this project in Eclipse. I got an > "socket closed" error when debugging the project. I found that not all the > Maven Project in eclipse have this problem. Only the projects which have > many dependencies have this problem. > > > Eugene Kuleshov wrote: >> >> >> I am not sure what exactly you meant by "running this project". >> However, when you run pretty much anything in Eclipse, you can see the >> actual command line used in Debug view. That could shed the light on the >> issue. See more details in the following wiki page. >> http://docs.codehaus.org/display/M2ECLIPSE/Reporting+Issues#ReportingIssues-process >> >> regards, >> Eugene >> >> >> youhaodeyi wrote: >>> I am working on a maven project in eclipse. When running this project, >>> it >>> always prompt an error dialog indicating that the javaw.exe has a >>> problem. >>> There is no such error when I use other machines. I have reinstalled my >>> JDK >>> and the problem is still there. >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> >> > > -- View this message in context: http://www.nabble.com/javaw.exe-problem-when-doing-with-Maven-project-tp17958597p17982765.html Sent from the Maven Eclipse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
