Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 354314

Summary:	NullPointerException in various scenarios with Maven update/enable dependencies
Product:	z_Archived	Reporter:	Adi R <adir1>
Component:	m2e	Assignee:	Project Inbox <m2e.core-inbox>
Status:	CLOSED NOT_ECLIPSE	QA Contact:
Severity:	normal
Priority:	P3	CC:	igor
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Adi R

2011-08-09 19:14:27 EDT

Build Identifier: 201107091000 (STS)

!MESSAGE An internal error occurred during: "Enabling Maven Dependency Management".
!STACK 0
java.lang.NullPointerException
	at org.eclipse.jst.common.internal.modulecore.ClasspathContainerReferenceResolver.canResolve(ClasspathContainerReferenceResolver.java:30)
	at org.eclipse.wst.common.componentcore.resolvers.ReferenceResolverUtil.getResolver(ReferenceResolverUtil.java:43)
	at org.eclipse.wst.common.componentcore.internal.StructureEdit.createVirtualReference(StructureEdit.java:295)
	at org.eclipse.wst.common.componentcore.internal.resources.VirtualComponent.getReferences(VirtualComponent.java:437)
	at org.eclipse.jst.j2ee.componentcore.util.EARVirtualComponent.getHardReferences(EARVirtualComponent.java:89)
	at org.eclipse.jst.j2ee.componentcore.util.EARVirtualComponent.getReferences(EARVirtualComponent.java:192)
	at org.maven.ide.eclipse.wtp.EarProjectConfiguratorDelegate.setModuleDependencies(EarProjectConfiguratorDelegate.java:145)
	at org.maven.ide.eclipse.wtp.WTPProjectConfigurator.mavenProjectChanged(WTPProjectConfigurator.java:63)
	at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.mavenProjectChanged(ProjectConfigurationManager.java:646)
	at org.maven.ide.eclipse.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:636)
	at org.maven.ide.eclipse.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:767)
	at org.maven.ide.eclipse.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:346)
	at org.maven.ide.eclipse.project.MavenProjectManager.refresh(MavenProjectManager.java:65)
	at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.configureNewMavenProject(ProjectConfigurationManager.java:209)
	at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.enableMavenNature(ProjectConfigurationManager.java:317)
	at org.maven.ide.eclipse.actions.EnableNatureAction$1.run(EnableNatureAction.java:123)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)


Reproducible: Always

Steps to Reproduce:
Happens in various scenarios, every time same ClasspathContainerReferenceResolver.canResolve crashes, even though different stack gets there.
1. Imported Maven Project (working and compiling via command line)
2. Disabled Dependency Management via maven->disable right-click on project
3. Enable Dependency Management via maven->enable right-click on project
NPE pops up

Comment 1 Adi R

2011-08-09 19:15:57 EDT

Already checked all our project (and dependent) pom files for pluginExecutionFilter issue with missing versionRange, reported in another bug. Looks like all our pluginExecutionFilter definitions have valid versionRange entry.

Comment 2 Igor Fedorenko

2011-08-09 22:36:07 EDT

m2e-wtp issues should be reported to https://issues.sonatype.org/browse/MECLIPSEWTP. Also, you appear to be using old version of m2e and m2e-wtp, so I'd check if current version solved this problem already.

Comment 3 Denis Roy

2021-04-19 13:25:59 EDT

Moved to https://github.com/eclipse-m2e/m2e-core/issues/