- This topic has 6 replies, 2 voices, and was last updated 15 years, 6 months ago by
.
-
Posts
-
I inadvertently updated from 7.1 to 7.1.1 this morning (clicking through update dialogs without paying attention), and in general things are still ok, but now Tomcat 6 webapp deployment operations have started failing with this error in the .metadata\.log file of my workspace:
!ENTRY org.eclipse.core.jobs 4 2 2009-04-30 15:53:11.151
!MESSAGE An internal error occurred during: “Add Deployment”.
!STACK 0
java.lang.NoClassDefFoundError: org/maven/ide/eclipse/jdt/BuildPathManagerI didn’t see any errors during the update. Is there some way to recover from this without a reinstall? I have no clue what jar this would have been inside (not even which plugin) or why it’s gone. Eclipse restarts don’t help.
Thanks in advance for any tips.
skolson,
Are you using Maven? If not I would recommend you to discontinue maven support, check this thread here http://www.myeclipseide.com/PNphpBB2-viewtopic-t-21172-postdays-0-postorder-asc-start-15.html
Not sure what you mean – I have made a webapp in MyEclipse like normal, and am using the standard button and subsequent dialog in MyEclipse to deploy the webapp to my local tomcat in prep for trying to run it. The deploy operation fails, and the above exception is in the Eclipse log as a result. If Maven’s involved in that, it’s not to my knowledge. My web project certainly has no POM or other related maven artifacts.
This standard webapp deploy operation worked day before yesterday and consistently since I’ve been on 7.1 (weeks). It started failing yesterday after the software update.
Are you saying that this deploy operation MyEclipse does uses Maven under the covers, and that I should try to disable it somewhere in the preferences, which is what the thread you reference seems to say?
Thanks for the quick response. Let me know if i need to provide more info.
More info, in case this is helpful – I checked, and Maven4MyEclipse option is not enabled in my preferences.
Sorry for the multiple posts – here’s the full call stack on the error from the eclipse .log file:
!ENTRY org.eclipse.core.jobs 4 2 2009-05-01 09:11:33.982
!MESSAGE An internal error occurred during: “Add Deployment”.
!STACK 0
java.lang.NoClassDefFoundError: org/maven/ide/eclipse/jdt/BuildPathManager
at com.genuitec.eclipse.maven.core.M2EclipseUtil.isMavenLibrary(M2EclipseUtil.java:586)
at com.genuitec.eclipse.maven.core.M2EclipseDelegate.isMavenLibrary(M2EclipseDelegate.java:64)
at com.genuitec.eclipse.j2eedt.core.MavenUtil.isMavenLibrary(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.WarPackager.getWarDependencyProjects(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.DefaultPackagerStrategy.getLibraryProjects(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.DefaultPackagerStrategy.getProjectDependencies(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.DefaultPackagerStrategy.explodeDependentProjects(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.PackageUtils.explodeDependentProjects(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.WebDeployment.Ä„(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.WebDeployment.doProjectTypeSpecificPostResyncAll(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.Deployment.resyncAll(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ModuleDeployment.deployAsExplodedArchive(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.jobs.A.ÄÂ�(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.jobs.A.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)I gave up and downloaded and installed the 7.1.1 release from scratch and it fixed me up. I don’t know what the Software Update process did, so I don’t have a way to diagnose. I’ll definitely be more careful about use of the Software Update path in the future until it looks more reliable…
