Maven 2 & 3

Description

Welcome to the issue tracker for the Maven Core! Here you can report bugs or feature requests that affect the heart of Maven. If you would like to report an issue for a particular plugin, please go to the plugin's JIRA project as listed on the Plugin Index. Likewise, issues about the Maven Ant Tasks should not be filled here but in their own JIRA project. If you encounter a problem while trying to run Maven via some IDE integration, please report the issue to the respective integrator.

Important:
When reporting an issue, please keep in mind that enabling developers to reproduce your problem is crucial for fixing it. Some bugs show only up on certain operating systems, JDK versions or project structures. Therefore, your report should include the following items:

• The debug output from your failing build. This can be obtained by adding the flag -X to the Maven command line and piping the output into a file:
  mvn -X goal > build.log.
  You can then use the JIRA command "Attach file" to upload this log. Among others, this log will reveal your Maven version, the Java version, the operating system and the plugin versions.
• Your POM files used for the build. Even more handy would be a minimal test project that demonstrates the failure such that a developer can simply unpack this project and jump right into your problem. Packaging this demo project as outlined in Creating a Maven Integration Test would be appreciated most because this allows to quickly incorporate the project into Maven's IT suite and guards against regressions of the problem.

Once your issue is created, please be patient. Both the number of volunteers developing Maven and their time is limited and Maven is not one of the smallest projects. Resolving an issue is potentially accelerated by Submitting a Patch, preferrably accompanied by a unit test to prevent regressions. Helping hands are always welcome so if you would like to contribute more, check out our Guide to Helping with Maven.

Finally note that the issue tracker is not the right place to ask questions about Maven's usage. Instead, post an email to the Maven User List. This way, your question will not only reach the Maven developers but other users, too. Additionally, you can browse the official FAQ as well as the unofficial FAQ for popular questions.

• URL:http://maven.apache.org/
• Lead: Maven Developers List
• Key:MNG

MoreIssues: Due

• MNG-591 2005-07-14T15-32 2008-12-13T18-35 Integration tests lifecycle
• MNG-624 2005-07-20T20-56 2009-12-31T00-13 automatic parent versioning
• MNG-2157 2006-03-17T19-35 2009-12-30T13-20 Properties defined in top-level profiles.xml do no propagate to child modules

Issues: 30 Day Summary

MoreIssues: Updated recently

• MNG-4561 2010-02-09T10-32 Today 05:44 PM Proxies not handled correctly
• MNG-4428 2009-11-05T02-18 Today 05:35 PM Permament move (error 301) not handled properly by Maven
• MNG-4560 2010-02-09T07-18 Today 07:23 AM Crash if command line parameter ends in space

MoreVersions: Due

• 2.0.11  
• 2.2.2  
• 3.0-alpha-7  

Activity Stream