Community
Participate
Working Groups
What steps will reproduce the problem? 1. run Java Application from "Run As" context menu... 2. run configurations window -> classpath: there is no project folder under user entries first son node "uaapConsole" folder,just an icon without name 3. -- Error Details -- Date: Wed Aug 11 17:51:06 CST 2010 Message: The project: uaapConsole which is referenced by the classpath, does not exist. Severity: Error Product: Eclipse 1.3.0.20100617-0521 (org.eclipse.epp.package.jee.product) Plugin: org.eclipse.jdt.launching Session Data: eclipse.buildId=I20100608-0911 java.version=1.5.0_22 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=zh_CN Framework arguments: -product org.eclipse.epp.package.jee.product -XX:+UseParallelGC Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product -XX:+UseParallelGC
Created attachment 176318 [details] unnormal classpath
Are there any build path errors associated with thiw project. The default runtime classpath is derived from the project's build path, and it looks like some of the references on the build path do not exist?
Created attachment 176432 [details] the buildpath the output chalsspath is uaapConsole/app-inf/classes not the web-inf/classes
Created attachment 176433 [details] in EclipseGanymede, applicable one
project "uaapConsole" has been deployed right and run no errors,and it is a web application. the buildpath screenshot is in Attachement list run in Eclipse ganymede ,there is no-error with run JavaApplication within project Doing non-changes,just import the project with Eclipse Helios(on another PC) and run JavaApplication within project-->ERROR
This reads like a configuration issue. Can you attach a project that demonstrates the problem?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
