Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[m2e-dev] NPE with Change 'made maven launch logic easier to reuse'

Hi Igor,

a recent commit raises a NPE when lauching a Maven Build.

http://git.eclipse.org/c/m2e/m2e-core.git/commit/org.eclipse.m2e.launching/src/org/eclipse/m2e/internal/launch/MavenLaunchDelegate.java?id=2eeb2e47d3b1beb654c229bf109d7459721dcaf0

java.lang.NullPointerException
at org.eclipse.m2e.internal.launch.MavenLaunchDelegate.getProgramArguments(MavenLaunchDelegate.java:98)
at org.eclipse.m2e.internal.launch.MavenLaunchDelegate.launch(MavenLaunchDelegate.java:61)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:858)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

Seems like the getProgramArguments() method, which is invoked at line 61 uses this.extensionsSupport, before it gets instantiated in line 65.

Best regards
Andreas

Back to the top