[jbosstools-issues] [JBoss JIRA] (JBIDE-15322) NullPointerException when updating a Maven project

Alexey Kazakov (JIRA) jira-events at lists.jboss.org
Mon Aug 5 17:01:26 EDT 2013


    [ https://issues.jboss.org/browse/JBIDE-15322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795222#comment-12795222 ] 

Alexey Kazakov commented on JBIDE-15322:
----------------------------------------

After some investigation with George we found out that one of the projects had a broken .project file which caused the error:

{code}
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
	<name>org.jboss.forge.resources-api</name>
	<comment></comment>
	<projects>
	</projects>
	<buildSpec>
		<buildCommand>
			<name>org.eclipse.jdt.core.javabuilder</name>
			<arguments>
			</arguments>
		</buildCommand>
		<buildCommand>
			<name>org.eclipse.ui.externaltools.ExternalToolBuilder</name>
			<triggers>full,incremental,</triggers>
			<arguments>
				<dictionary>
					<key>LaunchConfigHandle</key>
					<value>&lt;project&gt;/.externalToolBuilders/org.jboss.tools.jst.web.kb.kbbuilder.launch</value>
				</dictionary>
			</arguments>
		</buildCommand>
		<buildCommand>
			<name>org.eclipse.wst.validation.validationbuilder</name>
			<arguments>
			</arguments>
		</buildCommand>
		<buildCommand>
			<name>org.eclipse.m2e.core.maven2Builder</name>
			<arguments>
			</arguments>
		</buildCommand>
	</buildSpec>
	<natures>
		<nature>org.eclipse.jdt.core.javanature</nature>
		<nature>org.eclipse.m2e.core.maven2Nature</nature>
		<nature>org.jboss.tools.jst.web.kb.kbnature</nature>
	</natures>
</projectDescription>
{code}

KB nature org.jboss.tools.jst.web.kb.kbnature presents but the KB builder org.jboss.tools.jst.web.kb.kbbuilder is missing. Removing .project file and re-importing solved the problem.
                
> NullPointerException when updating a Maven project
> --------------------------------------------------
>
>                 Key: JBIDE-15322
>                 URL: https://issues.jboss.org/browse/JBIDE-15322
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: common/jst/core
>    Affects Versions: 4.1.0.Final
>         Environment: eclipse.buildId=4.3.0.I20130605-2000
> java.version=1.7.0_21
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments:  -product org.eclipse.epp.package.jee.product
> Command-line arguments:  -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
>            Reporter: George Gastaldi
>            Assignee: Alexey Kazakov
>             Fix For: 4.2.0.Alpha1
>
>
> This happens when selecting multiple maven projects in working sets and "Maven -> Update Project" is issued:
> {code}
> java.lang.NullPointerException
> 	at org.eclipse.core.internal.resources.ProjectDescription.setBuildSpec(ProjectDescription.java:565)
> 	at org.jboss.tools.jst.web.WebModelPlugin.addNatureToProjectWithValidationSupport(WebModelPlugin.java:211)
> 	at org.jboss.tools.cdi.core.CDIUtil.enableCDI(CDIUtil.java:97)
> 	at org.jboss.tools.maven.cdi.configurators.CDIProjectConfigurator.configureInternal(CDIProjectConfigurator.java:110)
> 	at org.jboss.tools.maven.cdi.configurators.CDIProjectConfigurator.configure(CDIProjectConfigurator.java:86)
> 	at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:109)
> 	at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:472)
> 	at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> 	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:161)
> 	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:137)
> 	at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:465)
> 	at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:403)
> 	at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:316)
> 	at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:1)
> 	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:161)
> 	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:137)
> 	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:89)
> 	at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1301)
> 	at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:313)
> 	at org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob.runInWorkspace(UpdateMavenProjectJob.java:77)
> 	at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list