Community
Participate
Working Groups
Build Identifier: 201111221000 The m2e plugin fails with a NullPointerException when the "Update project configuration..." action is selected from the Maven context menu on a project in Eclipse. This happens when there is a resource in pom.xml with a relative directory path outside of the maven project. Like: <resource> <directory>../another-module/src/main/resource</directory> </resource> It also happens when the the ${basedir} maven property is used in the directory definition: <resource> <directory>${basedir}/../another-module/src/main/resource</directory> </resource> Possible workaround to prevent the NPE is to use the following definition: <resource> <directory>${project.build.directory}/../../another-module/src/main</directory> </resource> Reproducible: Always Steps to Reproduce: 1. Define a resource in your pom.xml which is outside of your maven project (see the Details section) - for example a file from an another maven project module 2. Select the "Maven -> Update project configuration..." context menu on the project 3. The m2e fails with the reported NPE
Created attachment 208137 [details] Stacktrace from the eclipse's log file
m2e plugin version, where the problem occurs: 1.0.100.20110804-1717
The bug has been already reported in: https://jira.codehaus.org/browse/MECLIPSE-701
please report m2e/wtp integration problems to https://issues.sonatype.org/browse/MECLIPSEWTP
Reported in https://issues.sonatype.org/browse/MECLIPSEWTP as it has been suggested. See: https://issues.sonatype.org/browse/MECLIPSEWTP-193
Moved to https://github.com/eclipse-m2e/m2e-core/issues/