Eugene,
Latest dev build (the one you just posted) shows this in the .log when
creating a maven project:
!ENTRY org.eclipse.equinox.registry 4 1 2008-09-02 17:34:14.889
!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>(Unknow
n Source)
at java.lang.Class.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Unknown Source)
at
org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecu
tableExtension(Unknown Source)
at
org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExt
ension(Unknown Source)
at
org.eclipse.core.internal.registry.ConfigurationElement.createExecutable
Extension(Unknown Source)
at
org.eclipse.core.internal.registry.ConfigurationElementHandle.createExec
utableExtension(Unknown Source)
at
org.maven.ide.eclipse.internal.ExtensionReader.readProjectConfiguratorEx
tensions(Unknown Source)
at
org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.getCo
nfigurators(Unknown Source)
at
org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.updat
eProjectConfiguration(Unknown Source)
at
org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.confi
gureNewMavenProject(Unknown Source)
at
org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.enabl
eMavenNature(Unknown Source)
at
org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.creat
eSimpleProject(Unknown Source)
at
org.maven.ide.eclipse.wizards.MavenProjectWizard$4.runInWorkspace(Unknow
n Source)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(Unknown
Source)
at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)
Other than that the log is empty.
Hugo
-----Original Message-----
From: Eugene Kuleshov [mailto:[EMAIL PROTECTED]
Sent: dinsdag 2 september 2008 14:24
To: [email protected]
Subject: Re: [m2eclipse-user] An internal error occurred during:
"Updating Maven Dependencies".
Visser, Hugo wrote:
> OK, I did some quick tests:
>
> New Maven project without archetype selection does not create a Java
> project on RAD 7.006.
> Various NullPointerExceptions with this stacktrace:
>
> java.lang.NullPointerException
> at
> org.maven.ide.eclipse.jdt.internal.MavenClasspathContainerInitializer.
> ge
> tBuildPathManager(Unknown Source)
> ...
>
This NPE happen on the following line:
MavenJdtPlugin.getDefault().getBuildpathManager();
Something seriously went wrong in your install. Can you please send me
full log from <workspace>/.metadata/.log
I saw similar issues in other environments, but they usually go away
after Eclipse restart.
> I get these too on creating a project, so looks like the main cause
> for broken projects.
> One other error that is related to m2eclipse occurs on checkout of an
> existing project:
>
> "Can't load legacy resolver configuration"
> Stacktrace:
> Java Model Exception: Java Model Status [<projectname> does not exist]
> ...
>
> Sorry I can't give you more detail at the moment, I hope this is
> useful anyway.
>
What version of m2eclipse you are using? This legacy project
configuration (stored inside container entry in .classpath) been changed
quite while ago...
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
