Bugzilla – Full Text Bug Listing
| Summary: | NullPointer trying to enable Maven on some projects | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Ben Tatham <bentatham> | ||||
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Ben Tatham
Created attachment 198479 [details]
NullPointerException
An internal error occurred during: "Enabling Maven Dependency Management".
java.lang.NullPointerException
I attached the full NPE from the Error Log view.
The project is a bit complex, with many levels of parent poms of which some add <pluginExecution> definitions to the lifecycleMappingMetadata. Looking at the effective pom, it seems that those configurations do not accumulate. Standard maven plugin configuration would dictate that since there is only one <lifecycleMappingMetadata> parameter to be passed to the lifecycle-mapping plugin, that they would not accumulate, but that means that all projects must redefine the same pluginExecutions.
Eclipse IDE for Java Developers
Version: Indigo Release
Build id: 20110615-0604
M2E 1.0.0.20110607-2117
*** This bug has been marked as a duplicate of bug 347602 *** |