Overview and mode of operation
Allows Eclipse Java debugger lookup sources of Java classes dynamically loaded by Maven, such as Maven plugins. Supports multiple versions of the same class loaded by the Maven VM. Sources are looked up among Eclipse workspace projects or resolved from Maven repositories as necessary.
Implementation uses -javaagent to instrument classes loaded by the target JVM with informtation about actual classes folder or jar file the classes are being loaded from. This information is captured in new JSR-45 SMAP stratum and retrived by Eclipse JDT debugger over JDWP.
The class folders and jar files are scanned for META-INF/maven/**/pom.properties to identify m2e project location and Maven artifact (groupId,artifactId,version) tuple or "GAV" for short. Enabled Maven (Nexus) indexes are also consulted to identify jar file GAV.
The search for sources is performed in the following order
- m2e workspace project name and location, if present, are matched to existing workspace projects
- artifact GAV is matched to existing workspace projects
- sources jar artifact corresponding to the GAV is resolved from Maven repositories.
In addition to Maven-specific source code lookup, implementation also supports Equinox-based runtimes, which is particularly useful for debugging Tycho builds where Equinox is embedded in Maven runtime.
- Install Eclipse SDK 4.4.1 or better from http://download.eclipse.org/eclipse/downloads/
Avoid Eclipse Eclipse 4.4/Luna and 4.5/Mars M1 Use Eclipse 4.4.1 or 4.5 M2 instead. See bug 437193 for more details.
- Install m2e 1.5 or better from http://www.eclipse.org/m2e/download/
- Install Dynamic Sources Lookup m2e extension from http://ifedorenko.github.com/m2e-extras/
Use for Maven launch configuration
Dynamic Sources Lookup m2e extension does not require any special configuration and is enabled by default for all debug Maven launches.
Manual configuration of Dynamic Sources Lookup
Dynamic Sources Lookup can be enabled for Java Application, Remote Java Application, JUnit and likely all other java launch configuration types.
-javaagentto VM arguments using launch configuration dialog
<stringAttribute/>element to .launch file
Source Lookup workspace preference page can be used to copy&paste exact values.
New in 220.127.116.11409041614
- Use Sonatype Central Repository REST API to identify artifacts
- Harder, but not impossible, to install on Eclipse 4.3.x
New in 18.104.22.168406131218
- asm 5.0.3, java 8 should be fully supported now
New in 22.214.171.124402131627
- Equinox classloading hook can now be used instead of javaagent to instrument classes
New in 126.96.36.199402120526
- Ability to manually enable Dynamic Sources Lookup for any java launch configuration
New in version 188.8.131.52401182304
- Preliminary java 8 support
New in version 184.108.40.206309291737
- Maven 3.1.x and Tesla 3.1.x compatibility
New in version 1.1
- Requires m2e 1.3 and Eclipse 4.3 (Kepler) M5
- [new] Maven (Nexus) indexes are now used to identify jar files GAV.
- [new] Ability to import artifacts as "Maven Binary" projects. Binary projects allow conditional breakpoints and other operations that require java project.
- [fix] Source editor should more reliably refresh after sources jar download.
- [fix] Exception stack traces do not show source file names
- Sources resolution uses repositories and pluginRepositories configured in Maven User settings.xml but not the actual repository or snapshot repository from the artifact the class was loaded from.
- javaagent implementation will not instrument classes that have existing JSR-45 SMAP.