Bug 359398 - Source not found (debugging a Jetty webapp)
Summary: Source not found (debugging a Jetty webapp)
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.8   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2011-09-29 07:06 EDT by toby CLA
Modified: 2012-07-18 03:45 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description toby CLA 2011-09-29 07:06:40 EDT
Build Identifier: 3.5.1  M20090917-0800

This is a bug I know for ages and it is so annoying I am reporting it now - it cost me lots of time already.

When I run a web app using for example a maven plugin with "jetty:run" - and I use this configuration for debugging the  webapp, it sometimes says "source not found".

When I click on add and then "ok" - even without doing anything, the source is shown for 1-2 seconds and disappears again. You can do this all the time and it is reproducable.

I have had this problem 1 year ago and I have it now with the latest Yoxos Eclipse with some J2ee tools

The only solution I know for this, is to use Netbeans....

Reproducible: Always

Steps to Reproduce:
1. Install any Eclipse
2. Get a project (e.g. from me)
3. Run it in debug mode
Comment 1 toby CLA 2011-09-29 07:07:49 EDT
....or alternative to using Netbeans ;-) is of course to go to another pc with another Eclipse version ( an older one) that does not have this problem.
Comment 2 Michael Rennie CLA 2011-10-03 09:34:46 EDT
> When I run a web app using for example a maven plugin with "jetty:run" - and I
> use this configuration for debugging the  webapp, it sometimes says "source not
> found".

What kind of launch configuration is it you are debugging with? JDT Debug only provides support for Java Application / Java Applet / Remote Java configurations.
Comment 3 Michael Rennie CLA 2011-10-12 16:00:23 EDT
Marking not_eclipse without more information and the mention of Yoxos + web app debugging.
Comment 4 Peter CLA 2012-07-18 03:28:35 EDT
I Got the same Problem. Please reopen!

My Problem: 
I got an maven webapp and use failsafe to make integrationtests using command "mvn verify". Therefore failsafe starts an jetty server and deploy the webapp. The webapp does *not* contains the /src/test/java/** test-classes and i have to run the integraiontests parallel to the jetty-server (guess its the same vm).

Thats all the story, in fact eclipse neither find the sources of the integration-tests nor the sources of the webapp! 

win7 64bit, thread-launcher is 
eclipse indigo 64bit
org.codehaus.plexus.classworlds.launcher.Launcher.

Command line is:

 "C:\***\jdk1.7.0_05\bin\javaw.exe" -agentlib:jdwp=transport=dt_socket,suspend=y,address=localhost:*** -Dmaven.home=EMBEDDED -Dclassworlds.conf=C:\***\.metadata\.plugins\org.eclipse.m2e.core\launches\m2conf247423526109835068.tmp -Dfile.encoding=Cp1252 -classpath /***/.eclipse/org.eclipse.platform_3.7.0_1709980481/plugins/org.eclipse.m2e.maven.runtime_1.1.0.20120529-1956/jars/plexus-classworlds-2.4.jar org.codehaus.plexus.classworlds.launcher.Launcher "-Dmaven.surefire.debug=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000 -Xnoagent -Djava.compiler=NONE" -B -s C:\***\.m2\settings.xml clean assembly:assembly verify
Comment 5 Peter CLA 2012-07-18 03:45:52 EDT
Hm, after a few restarts of the computer the problem went away.