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)
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)
at org.eclipse.jdt.core.JavaCore.create(Unknown Source)
<snip>
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]
at
org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(Unknown
Source)
at
org.eclipse.jdt.internal.core.JavaModelManager.getPerProjectInfoCheckExi
stence(Unknown Source)
at
org.eclipse.jdt.internal.core.JavaProject.getPerProjectInfo(Unknown
Source)
at
org.eclipse.jdt.internal.core.JavaProject.getRawClasspath(Unknown
Source)
at
org.eclipse.jdt.internal.core.JavaProject.getRawClasspath(Unknown
Source)
at
org.maven.ide.eclipse.internal.project.LegacyBuildPathManager.getResolve
rConfiguration(Unknown Source)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.readResol
verConfiguration(Unknown Source)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.refresh(U
nknown Source)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.refresh(U
nknown Source)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerRefreshJob.run
(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)
Sorry I can't give you more detail at the moment, I hope this is useful
anyway.
Hugo
-----Original Message-----
From: Visser, Hugo [mailto:[EMAIL PROTECTED]
Sent: maandag 1 september 2008 16:40
To: [email protected]
Subject: RE: [m2eclipse-user] An internal error occurred during:
"Updating Maven Dependencies".
Eugene,
If possible we'll migrate to 7.5 (in terms of costs licensing and
whatever I don't know if it's a paid upgrade for example) We're planning
to test the beta this week.
I did try the m2eclipse-dev version today on RAD 7 but it gave me really
strange bugs, like source folders not appearing and such. I didn't
investigate any further though...
Thanks for the fix, I really appreciate it, and I'm sure my team members
will too :)
Hugo
-----Original Message-----
From: Eugene Kuleshov [mailto:[EMAIL PROTECTED]
Sent: maandag 1 september 2008 16:20
To: [email protected]
Subject: Re: [m2eclipse-user] An internal error occurred during:
"Updating Maven Dependencies".
Hugo,
This is one of not very obvious backward incompatibilities in Eclipse
3.2 used by RAD7.
I will commit fix shortly and it will be incorporated into future
builds.
By the way, are you planning to migrate to RAD7.5? I believe it is
using newer Eclipse version (hence less problems with m2eclipse) and
beta version is already available for download at
http://tinyurl.com/64bexr
Thanks
Eugene
Visser, Hugo wrote:
> Hi,
>
> I'm getting "An internal error occurred during: "Updating Maven
> Dependencies"." when opening or checking out projects. The stacktrace
> in the log is:
>
> java.lang.IllegalArgumentException:
> at org.eclipse.core.runtime.Assert.isLegal(Unknown Source) at
> org.eclipse.core.runtime.Assert.isLegal(Unknown Source) at
> org.eclipse.core.runtime.Status.setMessage(Unknown Source) at
> org.eclipse.core.runtime.Status.<init>(Unknown Source) at
> org.maven.ide.eclipse.core.MavenLogger.log(Unknown Source) at
> org.maven.ide.eclipse.internal.project.MavenProjectManagerRefreshJob.r
> un
> (Unknown Source)
> at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)
>
> Any idea what may be causing this? I'm using RAD 7 (Eclipse 3.2).
>
> Thanks,
>
> Hugo
>
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
