[Henning Schmiedehausen]

This bug has been present ever since MyEclipse gained maven support. I am able to verify this bug on MyEclipse 7.5, 8.0 and 8.5. And it annoys me:

We develop web applications using MyEclipse in Jetty 6 and we use maven to manage our dependencies. So far, that works ok, all required jars are deployed into WEB-INF/lib and the webapp starts.

Now, if you debug the web application and set a breakpoint on a class in one of the dependencies (or step into a class that is inside a jar), then instead of the class, a tab is shown saying “Source not found” and the “Edit Source Lookup Path…” button. If you press this button, you see the source lookup path. And lo and behold, it contains “Default”, which in turn contains my web project and the Jars from the JDK. And my web project in turn contains my source folders. BUT NOT THE MAVEN MANAGED DEPENDENCIES.

I tried “Add…”, select “Java Library” and “Maven Managed Dependencies”, clicking “Next” shows the “Use Maven Project settings to configure Maven dependency resolution” page and “Finish” then does … nothing! No additional library shows up, nothing. And obviously, it does not work.

I have the source to all my maven dependencies and I can browse the source just fine. Only the debugger is unable to find the source from the maven dependencies. What I can do is add source as external jars, e.g. press “Add…” -> “External Archive” -> select /home/henning/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4-sources.jar” so all the classes in commons-lang are displayed. However, there is still a slight snatch with that (besides that it is cumbersome) and that is that the debugger now stops in a tab that is called “StringUtils.java” while the editor and the IDE itself uses a second tab that is called “StringUtils.class”. Both tabs have the same contents, but e.g. breakpoints behave strange and sometimes you have to set them in “StringUtils.class” even though they are displayed (and hit) in “StringUtils.java”.

This behavior has been like this ever since MyEclipse 7.5. I can easily reproduce it on MyEclipse 8.0 and 8.5.

As I assume that my use case (“Develop a web application using Maven and deploy into a local container”) is not really exotic, I would love to get this bug fixed. It is very cumbersome and makes me ponder about alternatives every time I have to add my 100+ dependencies one-by-one to the source path of a project.

Linux x86_64 and i386, MyEclipse 7.5/Eclipse Classice 3.4.2 and MyEclipse 8.5/Eclipse Classic 3.5.2, Jetty 6.1.19 and Jetty 6.1.22, deployed as “exploded”.

[Brian Fernandes]

Just to clarify your experience, while developing – when you open a class that is in a JAR which is part of the “Maven Managed Dependencies” container in Eclipse – you can see the source. However, if you hit a breakpoint, the debugger cannot find the source?

Thanks for bringing this to my attention, I have filed this as a high priority item for our Maven team.

[Henning Schmiedehausen]

@Support-Brian wrote:

Just to clarify your experience, while developing – when you open a class that is in a JAR which is part of the “Maven Managed Dependencies” container in Eclipse – you can see the source. However, if you hit a breakpoint, the debugger cannot find the source?

Thanks for bringing this to my attention, I have filed this as a high priority item for our Maven team.

Yes, you got it. I will send you a bunch of screen shots with explanations via PM.

[Brian Fernandes]

Screenshots received, thank you very much for your time!
I have my Maven team looking into the issue right now.

[Henning Schmiedehausen]

That is great, thank you.

[Author]

Posts