OK, fresh RAD 7 install, after restart the package explorer now errors
on restart on the latest dev version:
java.lang.NullPointerException
at
org.maven.ide.eclipse.jdt.internal.MavenClasspathContainerInitializer.ge
tBuildPathManager(Unknown Source)
at
org.maven.ide.eclipse.jdt.internal.MavenClasspathContainerInitializer.in
itialize(Unknown Source)
at
org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(Unkno
wn Source)
at
org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(Unk
nown Source)
at org.eclipse.jdt.core.JavaCore.getClasspathContainer(Unknown
Source)
at
org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(Unknown
Source)
at
org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(Unknown
Source)
at
org.eclipse.jdt.internal.core.JavaModelManager.determineIfOnClasspath(Un
known Source)
at org.eclipse.jdt.internal.core.JavaModelManager.create(Unknown
Source)
at org.eclipse.jdt.internal.core.JavaModelManager.create(Unknown
Source)
Is there any way to debug this (in my spare time) so I can provide more
info?
Hugo
-----Original Message-----
From: Eugene Kuleshov [mailto:[EMAIL PROTECTED]
Sent: dinsdag 2 september 2008 18:07
To: [email protected]
Subject: Re: [m2eclipse-user] An internal error occurred during:
"Updating Maven Dependencies".
Visser, Hugo wrote:
> Latest dev build (the one you just posted) shows this in the .log when
> creating a maven project:
>
> !MESSAGE Plug-in "org.maven.ide.eclipse.jdt" was unable to instantiate
> class "org.maven.ide.eclipse.jdt.internal.JavaProjectConfigurator".
> !STACK 0
> java.lang.NullPointerException
> at
> org.maven.ide.eclipse.jdt.internal.JavaProjectConfigurator.<init>(Unkn
> ow
> n Source)
> at java.lang.Class.newInstanceImpl(Native Method)
> at java.lang.Class.newInstance(Unknown Source)
> at
> org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExe
> cu
> tableExtension(Unknown Source)
> at
> org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableE
> xt
> ension(Unknown Source)
> ...
>
> Other than that the log is empty.
>
What happen if you restart Eclipse after that error?
I'll make initialization of JavaProjectConfigurator more lazy in the
next builds.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
