Yes I'm guessing the commandline is too long. Can you use the debug view described below, to find out how long the commandline is? I'm curious how long it is, and what operating system are you using. Then you can compare this to the length of the commandline on the computers that work.
If that really is the problem, I think your only option is to put your maven repository at a higher point in the directory structure. If you are using m2eclipse's workspace resolution then the commandline will also include references to the class folders in your eclipse workspace. youhaodeyi wrote: > > Do you mean the length of the commandline is too long? If yes, how can I > fix it. I use maven dependency. The commandline includes all the path > relate to the maven repository. That would be pretty long. > > > scytacki wrote: >> >> 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. >> >> > -- View this message in context: http://www.nabble.com/javaw.exe-problem-when-doing-with-Maven-project-tp17958597p18022527.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
