maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Janning Vygen (JIRA)" <>
Subject [jira] Created: (MECLIPSE-542) Source not found. in debug session with m2eclipse and jetty
Date Wed, 01 Apr 2009 15:41:12 GMT
Source not found. in debug session with m2eclipse and jetty

                 Key: MECLIPSE-542
             Project: Maven 2.x Eclipse Plugin
          Issue Type: Bug
          Components: Core : Dependencies resolution and build path (.classpath)
         Environment: Version is unknown, my plugin shows "Maven Integration for Eclipse
I hope "Maven 2.x Eclipse Plugin" means "Maven Integration for Eclipse"
            Reporter: Janning Vygen
         Attachments: maven-debug-issue.txt

Attached is exception log from eclispe, my jetty launch configuration and my debug launch

When debugging source from the project itself is found but not from the "Maven Dependencies"
Source code is available and downloaded. I can open it, set a breakpoint and the breakpoint
gets triggered,  it opens an editor shows the source code for less than half a second and
then it shows "Source not found / Edit Lookup Path". Funny that the hierarchy in Maven Dependencies
in the package explorer is opened when i have "Link with editor".  So it seams to be found
but overriden by someone

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message