[tharrisxx]

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

[tharrisxx]

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

[support-chakri]

Hi Tom Harris,

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

Thanks,
Chakri.

[Brian Fernandes]

Tom, Sorry for the delayed response

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?

[Fuad Efendi]

@Support-Brian wrote:

Tom, Sorry for the delayed response

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:

!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)

[gkar47]

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.

[Brian Fernandes]

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.

[schanamolu]

Hi,

We have Maven projects that currently compile and build out side ide from command prompt. I was asked by Boss to evaluate the capabilities of my eclipse, so that I can import the Maven projects, debug and deploy it in JBOSS WITH IN myeclipse.

This existing capability should be there with out impacting or making changes POM.XML

Let me know

Thanks,
sreedhar

[Brian Fernandes]

sreedhar,

MyEclipse 10.x will suit your needs. We can even import Maven projects which have no Eclipse metadata whatsoever – the deployment settings will be correctly made on import and no changes to your pom.xml should be required.

Please try 10.5 and let me know if you need additional assistance.

[schanamolu]

Brian,

Can you please guide me a tutorial how to import Maven project with in Myeclipse 10.5 as I installed on my machine yesterday.

Pl also provide me tutorial for deployment, debugging after I import Maven project.

We have 3 Layered Maven Project.

Parent: Pom.xml

Child 1 : Pom.xml

Child 2 : Pom.xml —————> It generates war file which we need to deploy in JBOSS Server.

Currently Incommand Line prompt we run Parent MVN File : mvn install which will excute child 1and child 2 generate a war file . If this one works we are dedicted 8 developers will buy my eclipse professional license. Let me know as I have dead line by monday COB

Let me know

Thanks,
Sreedhar

[Brian Fernandes]

Sreedhar,

You would need to import your parent project into MyEclipse using the File > Import > Maven4MyEclipse > Existing Maven projects. Selecting just the parent POM will also list all the modules within then and import them correctly.

You can debug these projects just like you debug normal applications in MyEclipse – these tutorials are available in our integrated help; there is no special Maven debugging tutorial.

If you still wish to generate WARs, you can look at the “Run As > Maven Install” context menu item for each of the projects.

MyEclipse is available free for 30 days, so I would encourage you to download and try these steps yourself.

[schanamolu]

I try to Import the MavenProject Parent Pom.xml, then Iam getting following error in one of screen

Setup Maven PlugIn connectors Screen:

Discover and map Eclipse plugins to Maven plugin goal executions

.

.No marketplace entries found to handle maven-apt-plugin:1.0:process in Eclipse.  Please see Help for more information
No marketplace entries found to handle maven-dependency-plugin:2.1:copy in Eclipse.  Please see Help for more information

[Brian Fernandes]

Sreedhar,

1) Could you confirm if you are importing your project from the local file system or from a repository?

2) Is the machine on which you are importing connected to the Internet?

3) Are there references to the plugins in any of your pom.xml files? If so, can you past the pom.xml here please or send it to support@genuitec.com with a link to this thread?

[schanamolu]

Hi,
Please check my responses.

1) Could you confirm if you are importing your project from the local file system or from a repository? ————> Local File System

2) Is the machine on which you are importing connected to the Internet? —-> Yes it is connected to Internet.

3) Are there references to the plugins in any of your pom.xml files? If so, can you past the pom.xml here please or send it to support@genuitec.com with a link to this thread?

Please let me know if u want Parent Pom.xml or Children Pom.xml or Both?
POM.XML

Please check the attached in zip format with the following items in place.
Parent
Children1
Children2
Children3

Let me know

Sreedhar

Attachments:

You must be logged in to view attached files.

[Author]

Posts