Issue 569 in q4e: An internal error occurred during: "Updating classpath container: ..."
q...@googlecode.com
Owner: ----
New issue 569 by david.pedowitz: An internal error occurred
during: "Updating classpath container: ..."
http://code.google.com/p/q4e/issues/detail?id=569
All Maven Projects keep throwing the following error
Eclipse IAM 0.11.0.201001181900
eclipse.buildId=M20090917-0800
java.version=1.6.0_15
java.vendor=Sun Microsystems Inc.
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
java.lang.NullPointerException
at
org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.removeLink(VirtualResource.java:300)
at
org.eclipse.iam.wtp.core.internal.war.MavenWarClasspathListener.addOverlayWarFolders(MavenWarClasspathListener.java:89)
at
org.eclipse.iam.wtp.core.internal.war.MavenWarClasspathListener.resolved(MavenWarClasspathListener.java:57)
at
org.eclipse.iam.jdt.core.classpath.container.MavenClasspathContainer.resolveArtifacts(MavenClasspathContainer.java:272)
at
org.eclipse.iam.jdt.core.classpath.container.MavenClasspathContainer.refreshClasspath(MavenClasspathContainer.java:141)
at
org.eclipse.iam.jdt.core.classpath.container.MavenClasspathContainer.newClasspath(MavenClasspathContainer.java:181)
at
org.eclipse.iam.jdt.core.classpath.container.UpdateClasspathJob.runInWorkspace(UpdateClasspathJob.java:80)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
q...@googlecode.com
Comment #1 on issue 569 by carlossg: An internal error occurred
http://code.google.com/p/q4e/issues/detail?id=569
Can you provide more details?
is it for all proejct types? war/jar/pom ?
for projects that you had already opened?
after importing new projects?
what facets are enabled in the project properties/project facets?
if you uncheck and check again "Use Maven dependency management" for the
projects,
does it get fixed?
and please next time open issues in our Eclipse bugzilla
https://bugs.eclipse.org/bugs/buglist.cgi?product=IAM&bug_status=__open__
q...@googlecode.com
Comment #2 on issue 569 by david.pedowitz: An internal error occurred
http://code.google.com/p/q4e/issues/detail?id=569
war projects, jar seems fine
All projects regardless of open/close
Adding 'Use Maven dependency management' for the first time, unchecking
makes it go
away, rechecking brings it back
Here's an example .project and .classpath:
<projectDescription>
<name>project</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
<buildCommand>
<name>org.eclipse.jdt.core.javabuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.eclipse.wst.common.project.facet.core.builder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.eclipse.iam.jdt.core.mavenIncrementalBuilder</name>
<arguments>
</arguments>
</buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.iam.jdt.core.mavenNature</nature>
<nature>org.eclipse.jdt.core.javanature</nature>
<nature>org.eclipse.wst.common.project.facet.core.nature</nature>
</natures>
</projectDescription>
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry including="**/*.java" kind="src"
output="target/test-classes"
path="src/test/java"/>
<classpathentry including="**/*.java" kind="src" path="src/main/java"/>
<classpathentry kind="con"
path="org.eclipse.iam.jdt.core.mavenClasspathContainer">
<attributes>
<attribute name="org.eclipse.jst.component.dependency"
value="/WEB-INF/lib"/>
</attributes>
</classpathentry>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry kind="output" path="target/classes"/>
</classpath>
q...@googlecode.com
Comment #3 on issue 569 by david.pedowitz: An internal error occurred
http://code.google.com/p/q4e/issues/detail?id=569
Sorry about the bug location....
q...@googlecode.com
Comment #4 on issue 569 by carlossg: An internal error occurred
http://code.google.com/p/q4e/issues/detail?id=569
I can see the ModuleCoreNature missing, adding it should fix it, but can we
tell me
whether you had the project in Eclipse and upgraded to 0.11.0, installed
and then
imported,... ?
and what version of WTP are you using? (about - installation details)
<nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>
q...@googlecode.com
Comment #5 on issue 569 by david.pedowitz: An internal error occurred
http://code.google.com/p/q4e/issues/detail?id=569
Do I simply add:
<nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>
to the .project file?
I installed Eclipse IAM
0.10.0.20090627114955616-7L9C4FA42kP8riBRsvtsYU_U on
7/1/09 according to the installation history.
Usually I create a project from the command line, do mvn eclipse:eclipse
and then
import and enable maven dependancy management...
q...@googlecode.com
Comment #6 on issue 569 by carlossg: An internal error occurred
http://code.google.com/p/q4e/issues/detail?id=569
yeah, you are not supposed to to mvn eclipse:eclipse, just Import -> Maven
2 project
and that's it.
If you delete your .project .classpath and .settings files/folders and do
the import
you should see everything working.
q...@googlecode.com
Status: Moved-to-IAM
Comment #7 on issue 569 by carlossg: An internal error occurred
during: "Updating classpath container: ..."
http://code.google.com/p/q4e/issues/detail?id=569
Moved to https://bugs.eclipse.org/bugs/show_bug.cgi?id=302351