After upgrading from MyEclipse 8.0 to 8.5, we have noticed that the "Import > General > Maven Projects" function is now simply missing. We have new team members and they cannot get out projects to import into MyEclipse.

How do you re-enable the Maven Project import function? We absolutely need it.

Our projects are using nested modules, and so when we attempt to import using the "General > Existing Projects into Workspace", it only pulls in the top level "parent" project, which will not allow us to compile, etc. We need each module project imported, just as we had working with MyEclipse 8.0 with Sonatype's Maven4YourEclipse replacement.

We have the standard Maven4MyEclipse plugin installed and we have checked the "Enable Maven4MyEclipse features" checkbox in the "Preferences > MyEclipse > Maven4MyEclipse" settings tab.

Tom Harris
tharris (at) axispoint (dot) com

You have to check the box titled "Support multiple Maven modules mapped to a single Eclipse workspace project" in the "Preferences > MyEclipse > Maven4MyEclipse > Maven" settings tab. Then you are able to choose "Import > Maven4MyEclipse > Existing Maven Projects". The functionality is not without issues though. I continue to get this error over and over:

An internal error occurred during: "Importing Maven projects".
Invalid thread access

Not sure what's that all about.

Tom Harris

Hi Tom Harris,

I have escalated this to the dev team member, they will get back to you on this.

Thanks,
Chakri.

Tom, Sorry for the delayed response

Quote:

The functionality is not without issues though. I continue to get this error over and over: An internal error occurred during: "Importing Maven projects". Invalid thread access

Is there any stack trace in your error log that accompanies this error? Are your projects successfully imported? I assume you have issues during the import process but simply try again and it works?

Support-Brian wrote:

Tom, Sorry for the delayed response Quote: The functionality is not without issues though. I continue to get this error over and over: An internal error occurred during: "Importing Maven projects". Invalid thread access Is there any stack trace in your error log that accompanies this error? Are your projects successfully imported? I assume you have issues during the import process but simply try again and it works?

I have the same problem with MyEclipse 8.6, "Invalid thread access"
Here is exception trace:

Code:

!ENTRY org.eclipse.core.jobs 4 2 2010-10-16 09:54:40.044 !MESSAGE An internal error occurred during: "Importing Maven projects". !STACK 0 org.eclipse.swt.SWTException: Invalid thread access    at org.eclipse.swt.SWT.error(SWT.java:3884)    at org.eclipse.swt.SWT.error(SWT.java:3799)    at org.eclipse.swt.SWT.error(SWT.java:3770)    at org.eclipse.swt.widgets.Widget.error(Widget.java:463)    at org.eclipse.swt.widgets.Shell.<init>(Shell.java:282)    at org.eclipse.swt.widgets.Shell.<init>(Shell.java:373)    at org.eclipse.jface.window.Window.createShell(Window.java:487)    at org.eclipse.jface.window.Window.create(Window.java:430)    at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)    at org.eclipse.jface.window.Window.open(Window.java:790)    at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:327)    at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:357)    at org.eclipse.jface.dialogs.MessageDialog.openQuestion(MessageDialog.java:456)    at com.genuitec.eclipse.j2eedt.core.internal.project.B.ā(Unknown Source)    at com.genuitec.eclipse.j2eedt.core.internal.project.B.convert(Unknown Source)    at com.genuitec.eclipse.maven.project.MyEclipseProjectSupport$1.run(MyEclipseProjectSupport.java:81)    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1782)    at com.genuitec.eclipse.maven.project.MyEclipseProjectSupport.configureWebProject(MyEclipseProjectSupport.java:105)    at com.genuitec.eclipse.maven.project.MyEclipseProjectSupport.configure(MyEclipseProjectSupport.java:57)    at org.maven.ide.eclipse.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:57)    at org.maven.ide.eclipse.internal.project.GenericLifecycleMapping.configure(GenericLifecycleMapping.java:48)    at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:332)    at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.configureNewMavenProject(ProjectConfigurationManager.java:267)    at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:175)    at org.maven.ide.eclipse.wizards.MavenImportWizard$1.runInWorkspace(MavenImportWizard.java:94)    at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Has there been any progress on this problem. It has been an entire year since this original post. In trying to get around this problem I found the following article that helps get you a working project in MyEclipse.

http://www.myeclipseide.com/PNphpBB2-printview-t-25961-start-0.html

But, why must we have to go through this convaluted process rather than have the Maven4MyEclipse tool just work??

My company is also seariously looking at other tools that support Maven and Seam properly.

gkar,

We are working on a solution to all these issues; due to the number of changes required, it is impractical for us to deliver a fix in the MyEclipse 9 stream. Rest assured that MyEclipse 10 will address all these issues, significantly improved Maven support is a primary goal of the MyEclipse 10 release. MyEclipse 10 (for Eclipse 3.7) will be released in early August; though we may have milestones available before then.