Unless you are using maven plugins not supported by m2e 1.0 lifecycle or by specific connectors, I believe m2e will be able to generate all eclipse configuraton needed for your project to work at project import time.
But keep in mind I'm just a user speaking. I'm not from m2e development team, so don't trust 100% in what I'm saying. But I can tell that everytime I delete Eclipse configuration and imported the project it have always worked for me. On Thu, Aug 25, 2011 at 12:07 PM, Fabricio Lemos < [email protected]> wrote: > Is it really required? Do I have to lose all eclipse configurations for > the project in order to import it? > > On 12/8/2011 15:52, Rafael Vanderlei wrote: > > Fabricio, before you import projects created using previous m2e versions, > did you delete all eclipse related files? (.classpath, .project, .settings, > etc) > > I believe it to be a required step to "upgrade" m2e version on existing > Eclipse projects > > On Fri, Aug 12, 2011 at 3:42 PM, Fabricio Lemos < > [email protected]> wrote: > >> We started having problems deploying the app, maybe because of classpath >> issues. A college of mine created a new project, did a copy and paste of the >> contents and now things are working. It seems the problems is only in the >> import of "old" projects, created before m2e 1.0. As soon as I manage to >> create an example project I will file the issue in Jira. >> >> >> >> 12/8/2011 14:44, Fabricio Lemos wrote: >> >> I just initialized Eclipse and got this exception: >> >> !ENTRY org.eclipse.osgi 2 0 2011-08-12 14:32:15.159 >> !MESSAGE While loading class >> "org.eclipse.m2e.jdt.internal.MavenClasspathContainerInitializer", thread >> "Thread[Worker-0,5,main]" timed out waiting (5000ms) for thread >> "Thread[Worker-4,5,main]" to finish starting bundle >> "org.eclipse.m2e.jdt_1.0.100.20110804-1717 [1038]". To avoid deadlock, >> thread "Thread[Worker-0,5,main]" is proceeding but >> "org.eclipse.m2e.jdt.internal.MavenClasspathContainerInitializer" may not be >> fully initialized. >> !STACK 0 >> org.osgi.framework.BundleException: State change in progress for bundle >> "reference:file:plugins/org.eclipse.m2e.jdt_1.0.100.20110804-1717.jar" by >> thread "Worker-4". >> at >> org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1087) >> at >> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:297) >> at >> org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268) >> at >> org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) >> at >> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:462) >> at >> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:476) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) >> at >> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:248) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:345) >> at >> org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:229) >> at >> org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1207) >> at >> org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174) >> at >> org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) >> at >> org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) >> at >> org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) >> at >> org.eclipse.jdt.core.JavaCore.computeClasspathContainerInitializer(JavaCore.java:2832) >> at >> org.eclipse.jdt.core.JavaCore.getClasspathContainerInitializer(JavaCore.java:2808) >> at >> org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2844) >> at >> org.eclipse.jdt.internal.core.JavaModelManager$11.run(JavaModelManager.java:2769) >> at >> org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) >> at >> org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2809) >> at >> org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1872) >> at >> org.eclipse.jdt.core.JavaCore.initializeAfterLoad(JavaCore.java:3543) >> at >> org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:36) >> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) >> Caused by: >> org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException >> ... 30 more >> Root exception: >> >> org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException >> at >> org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1087) >> at >> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:297) >> at >> org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268) >> at >> org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) >> at >> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:462) >> at >> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:476) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) >> at >> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:248) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:345) >> at >> org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:229) >> at >> org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1207) >> at >> org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174) >> at >> org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) >> at >> org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) >> at >> org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) >> at >> org.eclipse.jdt.core.JavaCore.computeClasspathContainerInitializer(JavaCore.java:2832) >> at >> org.eclipse.jdt.core.JavaCore.getClasspathContainerInitializer(JavaCore.java:2808) >> at >> org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2844) >> at >> org.eclipse.jdt.internal.core.JavaModelManager$11.run(JavaModelManager.java:2769) >> at >> org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) >> at >> org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2809) >> at >> org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1872) >> at >> org.eclipse.jdt.core.JavaCore.initializeAfterLoad(JavaCore.java:3543) >> at >> org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:36) >> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) >> >> !ENTRY org.eclipse.osgi 2 0 2011-08-12 14:32:45.940 >> !MESSAGE While loading class >> "org.eclipse.m2e.jdt.internal.MavenClasspathHelpers", thread >> "Thread[Worker-0,5,main]" timed out waiting (5000ms) for thread >> "Thread[Worker-4,5,main]" to finish starting bundle >> "org.eclipse.m2e.jdt_1.0.100.20110804-1717 [1038]". To avoid deadlock, >> thread "Thread[Worker-0,5,main]" is proceeding but >> "org.eclipse.m2e.jdt.internal.MavenClasspathHelpers" may not be fully >> initialized. >> !STACK 0 >> org.osgi.framework.BundleException: State change in progress for bundle >> "reference:file:plugins/org.eclipse.m2e.jdt_1.0.100.20110804-1717.jar" by >> thread "Worker-4". >> at >> org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1087) >> at >> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:297) >> at >> org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268) >> at >> org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) >> at >> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:462) >> at >> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:476) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) >> at >> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:248) >> at >> org.eclipse.m2e.jdt.internal.MavenClasspathContainerInitializer.initialize(MavenClasspathContainerInitializer.java:46) >> at >> org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2863) >> at >> org.eclipse.jdt.internal.core.JavaModelManager$11.run(JavaModelManager.java:2769) >> at >> org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) >> at >> org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2809) >> at >> org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1872) >> at >> org.eclipse.jdt.core.JavaCore.initializeAfterLoad(JavaCore.java:3543) >> at >> org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:36) >> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) >> Caused by: >> org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException >> ... 22 more >> Root exception: >> >> org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException >> at >> org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1087) >> at >> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:297) >> at >> org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268) >> at >> org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) >> at >> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:462) >> at >> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:476) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) >> at >> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) >> at >> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:248) >> at >> org.eclipse.m2e.jdt.internal.MavenClasspathContainerInitializer.initialize(MavenClasspathContainerInitializer.java:46) >> at >> org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2863) >> at >> org.eclipse.jdt.internal.core.JavaModelManager$11.run(JavaModelManager.java:2769) >> at >> org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) >> at >> org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2809) >> at >> org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1872) >> at >> org.eclipse.jdt.core.JavaCore.initializeAfterLoad(JavaCore.java:3543) >> at >> org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:36) >> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) >> >> !ENTRY org.eclipse.core.jobs 4 2 2011-08-12 14:32:45.940 >> !MESSAGE An internal error occurred during: "Initializing Java Tooling". >> !STACK 0 >> java.lang.NullPointerException >> at >> org.eclipse.m2e.jdt.internal.MavenClasspathContainerInitializer.getBuildPathManager(MavenClasspathContainerInitializer.java:86) >> at >> org.eclipse.m2e.jdt.internal.MavenClasspathContainerInitializer.initialize(MavenClasspathContainerInitializer.java:48) >> at >> org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2863) >> at >> org.eclipse.jdt.internal.core.JavaModelManager$11.run(JavaModelManager.java:2769) >> at >> org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) >> at >> org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2809) >> at >> org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1872) >> at >> org.eclipse.jdt.core.JavaCore.initializeAfterLoad(JavaCore.java:3543) >> at >> org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:36) >> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) >> >> My eclipse config file is attached. I will try to reproduce it with a >> smaller project and file the issue. >> >> thanks >> >> On 12/8/2011 12:59, Fred Bricon wrote: >> >> mmm I think it's the first time I see this exception. >> If you can reproduce it reliably, please create an issue in >> https://issues.sonatype.org/browse/MECLIPSEWTP and attach your project's >> eclipse config file + pom.xml >> >> regards, >> >> Fred Bricon >> >> 2011/8/12 Fabricio Lemos <[email protected]> >> >>> >>> On 10/8/2011 11:41, Fred Bricon wrote: >>> >>> Can you get more details on the exception you're getting? >>> (<workspace>/.metadata/.log) >>> >>> >>> This exception occurs after I import the project: >>> >>> !ENTRY org.eclipse.core.jobs 4 2 2011-08-12 11:23:37.552 >>> !MESSAGE An internal error occurred during: "Importing Maven projects". >>> !STACK 0 >>> java.lang.IllegalArgumentException >>> at >>> org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.addProjectFacet(FacetedProjectWorkingCopy.java:816) >>> at >>> org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:301) >>> at >>> org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) >>> at >>> org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339) >>> at >>> org.maven.ide.eclipse.wtp.WebProjectConfiguratorDelegate.configure(WebProjectConfiguratorDelegate.java:144) >>> at >>> org.maven.ide.eclipse.wtp.AbstractProjectConfiguratorDelegate.configureProject(AbstractProjectConfiguratorDelegate.java:84) >>> at >>> org.maven.ide.eclipse.wtp.WTPProjectConfigurator.configure(WTPProjectConfigurator.java:54) >>> at >>> org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:72) >>> at >>> org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:302) >>> at >>> org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProject(ProjectConfigurationManager.java:234) >>> at >>> org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:150) >>> at >>> org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$1.doCreateMavenProjects(MavenImportWizard.java:164) >>> at >>> org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:73) >>> at >>> org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$3.runInWorkspace(MavenImportWizard.java:249) >>> at >>> org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) >>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) >>> >>> >>> Does updating the maven configuration on your projects work after import? >>> >>> >>> Strangely, it works only in the second time. The first time I run it, it >>> shows: "Unable to update maven configuration for the following projects: >>> solare-intranet" and still shows the error "Project configuration is not >>> up-to-date with pom.xml". >>> The second time, the message "Unable to update..." still shows, but the >>> "Project configuration is not up-to-date..." is gone and the >>> MAVEN2_CLASSPATH_CONTAINER warning appears. >>> >>> When I click to update project configuration, nothing appears in the >>> console. >>> >>> >>> >>> 2011/8/10 Fabricio Lemos <[email protected]> >>> >>>> I installed m2e 1.0.100 and imported an existing war project. I >>>> received the error: "An internal error occurred during: "Importing Maven >>>> projects" java.lang.IllegalArgumentException" >>>> >>>> And after I´m stuck with >>>> MECLIPSEWTP-125<https://issues.sonatype.org/browse/MECLIPSEWTP-125>but the >>>> workaround does not apply because I have an war project. >>>> >>>> Is there a fix or any other workaround? >>>> >>>> thanks, >>>> Fabricio Lemos >>>> >>>> >>>> _______________________________________________ >>>> m2e-users mailing list >>>> [email protected] >>>> https://dev.eclipse.org/mailman/listinfo/m2e-users >>>> >>>> >>> >>> >>> -- >>> "Have you tried turning it off and on again" - The IT Crowd >>> >>> >>> _______________________________________________ >>> m2e-users mailing >>> [email protected]https://dev.eclipse.org/mailman/listinfo/m2e-users >>> >>> >>> _______________________________________________ >>> m2e-users mailing list >>> [email protected] >>> https://dev.eclipse.org/mailman/listinfo/m2e-users >>> >>> >> >> >> -- >> "Have you tried turning it off and on again" - The IT Crowd >> >> >> _______________________________________________ >> m2e-users mailing >> [email protected]https://dev.eclipse.org/mailman/listinfo/m2e-users >> >> >> >> _______________________________________________ >> m2e-users mailing >> [email protected]https://dev.eclipse.org/mailman/listinfo/m2e-users >> >> >> _______________________________________________ >> m2e-users mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/m2e-users >> >> > > > _______________________________________________ > m2e-users mailing > [email protected]https://dev.eclipse.org/mailman/listinfo/m2e-users > > > _______________________________________________ > m2e-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/m2e-users > >
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
