Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 318527 - project suddenly died with "Local configuration cannot be nested in a directory." for no apparent reason, and cant get it working
Summary: project suddenly died with "Local configuration cannot be nested in a directo...
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.0   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-30 19:20 EDT by Simon Hobbs CLA
Modified: 2010-07-29 02:23 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Hobbs CLA 2010-06-30 19:20:04 EDT
Build Identifier: 20100617-1415

Have a basic maven based project checked out from SVN.  It was building in eclipse without problems. The, out of the blue, nothing would build, and it cant resolve classes.  The Error log shows:

org.eclipse.core.runtime.CoreException: Local configuration cannot be nested in a directory.
	at org.eclipse.debug.internal.core.LaunchConfigurationType.newInstance(LaunchConfigurationType.java:463)
	at org.maven.ide.eclipse.actions.ExecutePomAction.createLaunchConfiguration(ExecutePomAction.java:191)
	at org.maven.ide.eclipse.actions.ExecutePomAction.getLaunchConfiguration(ExecutePomAction.java:248)
	at org.maven.ide.eclipse.actions.ExecutePomAction.launch(ExecutePomAction.java:128)
	at org.maven.ide.eclipse.actions.ExecutePomAction.launch(ExecutePomAction.java:116)
	at org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.launch(LaunchShortcutExtension.java:434)
	at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.run(LaunchShortcutAction.java:73)
	at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.runWithEvent(LaunchShortcutAction.java:121)
	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
	at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
	at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427)
	at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1383)


Now the project wont build in that its not showing any files in the explorer thing as having errors, but if I open any source file, almost everything is "xxx cannot be resolved to a type", and not even clean works (just gives that error, doesnt even clean the class files).

The project in question is a simple example sub project of mybatis which I used the m2 checkout from SCM to bring into eclipse some days ago. I have to build the war using "mvn -Pdev war:war", I could not get elcipse to do this.  No idea if this has any bearing on it.

-- Configuration Details --
Product: Eclipse 1.3.0.20100617-0520 (org.eclipse.epp.package.reporting.product)
Installed Features:
 org.eclipse.platform 3.6.0.v20100602-9gF78GpqFt6trOGhL60z0oEx3fz-JKNwxPY


Reproducible: Always

Steps to Reproduce:
1.I have no idea what broke the project with this error.
2.I have no idea how to fix this problem and get the project working again.
3.I found similar bugs with the same message, but no work arounds, and its supposed to be fixed in this version of eclipse.
I tried to sumbit this bug directly from eclipse, but I just get: "submit failed: An unknown repository error has occured: match failed" which gives me no clue why, so had to use the web form instead.
Comment 1 Remy Suen CLA 2010-06-30 20:16:17 EDT
It's not clear to me what this bug has to do with the UI of the Eclipse framework. I suggest you take it up with the folks that wrote the Maven plug-in.
Comment 2 Simon Hobbs CLA 2010-07-01 07:32:49 EDT
I just tried to create a brand new project in my workspace, using the m2eclipse new archtipe of a vaadin sample project, and get exactly the same error, ie.e

Error
Thu Jul 01 13:24:16 CEST 2010
Local configuration cannot be nested in a directory.

It wont resolve any of the dependences, althougth the pom.xml ect is fine.  Doing any of the maven operations (build/install/package etc) causes the same error.

It wont run in the servlet engine, gives:

javax.servlet.ServletException: Wrapper cannot find servlet class com.vaadin.terminal.gwt.server.ApplicationServlet or a class it depends on
	org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
	org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852)
	org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
	org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
	java.lang.Thread.run(Thread.java:619)

So Im completely stuffed.  I guess the next step is to delete all my work, delete eclipse including all the hours of installing the required plugins, and start from scratch.  If the same thing happens again I'm really stuffed.

Ha anyone else had the same error?
Comment 3 Remy Suen CLA 2010-07-01 07:36:42 EDT
Please follow-up with the m2eclipse team.
https://issues.sonatype.org/browse/MNGECLIPSE-2191
Comment 4 Prakash Rangaraj CLA 2010-07-29 02:23:15 EDT
(In reply to comment #3)
> Please follow-up with the m2eclipse team.
> https://issues.sonatype.org/browse/MNGECLIPSE-2191

    Marking as not-eclipse