[ http://jira.codehaus.org/browse/MNGECLIPSE-185?page=comments#action_73363 ] Eugene Kuleshov commented on MNGECLIPSE-185: --------------------------------------------
Please clarify if you have single Eclipse project or multiple and provide step by step instructions what exactly you are trying to do here. Also note, that dependency management has been greatly improved in 0.0.10 (unreleased yet). So, I just need to verify your use case. > bug with dependencyManagement section in a parent pom > ----------------------------------------------------- > > Key: MNGECLIPSE-185 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-185 > Project: Maven 2.x Extension for Eclipse > Issue Type: Bug > Affects Versions: 0.0.9 > Environment: maven 2.0.4 on Windows with eclipse 3.1 > Reporter: Nicolas Cazottes > Assigned To: Eugene Kuleshov > Attachments: projects.zip > > > I have also an issue related to dependencyManagement section in parent pom > with m2eclipse plugin on windows. > I have attached the projects that show the problem : when a project (projectD > in my example) is defined with a dependencyManagement section in the parent > pom in order to allow other projects to define its version (projectC in my > example), the build in eclipse with a clean on the project (calling the > install goal) fails when creating the jar. > The trace is the following : > org.apache.maven.lifecycle.LifecycleExecutionException: Error assembling JAR > ... > ... 8 more > Caused by: java.lang.NullPointerException > at > org.apache.maven.artifact.ArtifactUtils.copyArtifact(ArtifactUtils.java:109) > ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
