Description
Maven 2.x Eclipse Plugin.
Note: This project is not the right place to fill issues about the Maven Integration for Eclipse (M2Eclipse).
Carefully read How to Report Bugs Effectively.
Failure to provide a good bug report will delay or even prevent resolution of your issue.
Proper bug reports include self-contained example projects with precise instructions on how to reproduce the bug.
As a minimum, a debug log (mvn -X goal > build.log) is required to collect necessary information about your software stack (OS, Java, Maven, plugins) like versions and configuration. Please note that the plugin configuration dumps in a debug log might contain sensitive information like passwords, so be sure to erase those before log submission.
A good bug report will include a test case (as an integration test) and a patch file. If you have these your chances of getting it applied are greatly increased.
Before reporting a new bug, please double check whether the bug is still present in the latest release version. There is generally no reason to fill duplicate bug reports for issues that have already been fixed in newer releases.
Useful Resources:
-
- Lead:
- Maven Developers List
- Key:
- MECLIPSE
Issues: Due
-
MECLIPSE-566
The plugin fails to exclude certain dependencies.
-
MECLIPSE-604
Building Multiple eclipse Project with Maven
-
MECLIPSE-708
mvn eclipse:eclipse fails with NullPointerException on Java 7 if pom.xml contains version range
Issues: 30 Day Summary
Issues: 4 created and 0 resolved
Issues: Updated recently
-
MECLIPSE-713
Today 5:05 AM
Please release 2.9
-
MECLIPSE-712
Last Friday 9:03 AM
filteredResources in Eclipse .project is not supported and discarded by the Maven 2.x Eclipse Plugin
-
MECLIPSE-704
30/Jan/12
Request to merge when 'filtering' is not identical
