I also tuned the starting parameters and did some further investigation .. without any success! On every startup the "Initializing Java Tooling" error occurs .. no dependency resolution, no M2 classpath container ... that's really really bad for us here. :-(( I managed to get the POM editor with its dependency graph running here from time to time .. but the dependency container in the project explorer is not visible and the dependencies are not resolved in the classes at any time.
OK, it is RAD 7, but does this matter? It is based on Eclipse 3.2 so it is not limited to RAD .. and if I study the m2eclipse ticketing system correctly there are a couple of similar issues in the past respectively currently ... :-| > Eugene Kuleshov wrote: >> >> >> I don't think we tried to run m2eclipse on IBM JRE, at least not >> recently. >> You could probably play with its settings, like >> -Xshareclasses:singleJVM,keep and see if it would help. >> Not sure if RAD7 would work on Sun's JDK, but it may worth a shot. >> >> regards, >> Eugene >> >> > > hi eugene, > well - actually working on the same problem. > i have pretty much the same env as michael (IBM's RAD 7 based on eclipse > 3.2, using the dev build of m2eclipse, with maven embedder, maven eclipse > integration and POM editors - but i also tried without the editors - with > only the two basic features - didn't work either). > > tried toying with IBM VM's options (shareclasses set to 'none' and > 'nonfatal' did not work). > also followed your hint - and switched to sun's VM (it wouldn't be a > solution anyway even if it worked) and verified that it doesn't change > anything. > the following vm setup (in eclipse.ini) > -vm > C:\jdk1.6.0_07\bin\javaw.exe > -vmargs > -Xms256m > -Xmx768m > -Xincgc > -XX:MaxPermSize=512M > gives the following error: > !ENTRY org.eclipse.core.jobs 4 2 2008-10-08 15:23:34.312 > !MESSAGE An internal error occurred during: "Creating > maven-archetype-quickstart". > !STACK 0 > java.lang.NullPointerException > at > org.maven.ide.eclipse.jdt.internal.MavenClasspathContainerInitializer.getBuildPathManager(MavenClasspathContainerInitializer.java:78) > at > org.maven.ide.eclipse.jdt.internal.MavenClasspathContainerInitializer.initialize(MavenClasspathContainerInitializer.java:41) > at > org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:1924) > at > org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1267) > at > org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:1470) > at > org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2169) > at > org.eclipse.jdt.internal.core.ClasspathEntry.validateClasspath(ClasspathEntry.java:1312) > at > org.eclipse.jdt.internal.core.SetClasspathOperation.verify(SetClasspathOperation.java:840) > at > org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:773) > at > org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3016) > at > org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3032) > at > org.maven.ide.eclipse.jdt.internal.JavaProjectConfigurator.addMavenClasspathContainer(JavaProjectConfigurator.java:583) > at > org.maven.ide.eclipse.jdt.internal.JavaProjectConfigurator.configure(JavaProjectConfigurator.java:90) > at > org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:230) > at > org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.configureNewMavenProject(ProjectConfigurationManager.java:184) > at > org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:142) > at > org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.createArchetypeProject(ProjectConfigurationManager.java:446) > at > org.maven.ide.eclipse.wizards.MavenProjectWizard$5.runInWorkspace(MavenProjectWizard.java:284) > at > org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58) > > to make it a bit more precise - this happens when trying to create a maven > project from the basic archetype (maven-archetype-quickstart from > org.apache.maven.archetypes). but similar thing happens for simple maven > project w/o archetype, or even when i try importing existing project > sources > (created in eclipse 3.4) into RAD. > any ideas? > cheers, > michal > -- > View this message in context: > http://www.nabble.com/No-%22Maven-Dependencies%22-entry-..-and-an-exception-while-checkout-tp19842486p19878907.html > Sent from the Maven Eclipse - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
