Doug,

I spent considerable time trying to reproduce this NullPointerException without any success. So, please create bug report in jira and attach complete Eclipse projects that would allow to reproduce this issue and also specify what Eclipse version you are running.

I should have mentioned in the announcement, that defaults for nested module management been changed in 0.0.11 version. By default nested modules are disabled but you can enable it either using popup menu Maven / Enable Nested Modules, or directly trough configuration of the "Maven Dependencies" classpath container. See http://docs.codehaus.org/display/M2ECLIPSE/Dependency+Management

The reason for this is to better support project import, so nested modules are imported as separate projects by default, but again it can be changed in advanced settings to use old behavior. http://docs.codehaus.org/display/M2ECLIPSE/Importing+Maven+projects

Also note that most if not all issues related to "Maven Dependencies" container can be resolved by closing your projects, then reopening them and running Project / Clean. In some cases you may also need to refresh your Eclipse workspace if you are doing changes outside of Eclipse. Your steps to reproduce issue aren't detailed enough to tell what exactly you are doing to create projects, folders, and to edit poms, so maybe it is as simple as that.

 regards,
 Eugene


Doug Bateman wrote:
I just installed the latest m2eclipse 0.0.11.20070916 plugin and am encountering two errors. This is the second of the two emails describing the second error. Problem Description: The m2eclipse plugin throws a NullPointerException I attempt to use the "Enable Nested Modules" menu item on a project. Steps to Reproduce:
  1. Create a maven project.
  2. Create sub folders for "sub modules".
  3. Create poms for each, in the appropriate sub folder.
4. Create a top level pom which uses the standard <modules><module>...</module>...</modules> syntax to create a standard maven multi-module build.
  5. Put dependencies in some of the sub projects.
6. Enable the .m2 plugin's dependency management on the top level folder/project. 7. Notice none of the dependencies show up in the project (they used to appear in prior versions of the plugin). 8. Attempt to fix this by using the right click menu item "Maven->Enable Nested Models".
  9. Observe the NullPointerException.
10. Go to the menu "Window->Show View->Other". Select "PDE Runtime->Error Log".
 11. In the error log, note the logged exception, which reads:

    java.lang.NullPointerException
     at
    
org.maven.ide.eclipse.container.Maven2Builder.addModulePoms(Maven2Builder.java:103)
     at
    
org.maven.ide.eclipse.container.Maven2Builder.addModulePoms(Maven2Builder.java:110)
     at
    org.maven.ide.eclipse.container.Maven2Builder.build(Maven2Builder.java:80)
     at
    org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:624)
     at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java :37)
     at
    
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:166)
     at
    
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:197)
     at org.eclipse.core.internal.events.BuildManager$1.run
    (BuildManager.java:246)
     at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
     at
    
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:249)
     at org.eclipse.core.internal.events.BuildManager.basicBuildLoop
    (BuildManager.java:302)
     at
    org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:334)
     at
    org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:137)
     at org.eclipse.core.internal.events.AutoBuildJob.run
    (AutoBuildJob.java:235)
     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

My Questions for the Mailing List:
+ I'd like to get at least 1 other person to try the steps to recreate above and confirm the problems do indeed happen for them.
+ Should I go ahead and open a JIRA issue for this?
+ Does this latest plugin simply not support a project with nested modules (ie multi-module builds)?


---------------------------------------------------------------------
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email

Reply via email to