Fix DependencyResolutionResult not dispatched when resolution fails (fix #8635) - LifecycleDependencyResolver dispatched the result only on the success path; on failure the exception was wrapped before the dispatch point, so listeners received the request but never a result - Move the dispatch into both the success and catch branches immediately after the resolution call; remove the post-try dispatch; event order on success is unchanged, aggregator builds that tolerate failure still receive the result exactly once - Add LifecycleDependencyResolverEventsTest: result fires once on success, once on failure, and once when an aggregator tolerates the failure
Apache Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting and documentation from a central piece of information.
If you think you have found a bug, please file an issue in the Maven Issue Tracker.
More information can be found on Apache Maven Homepage. Questions related to the usage of Maven should be posted on the Maven User List.
You can download the release source from our download page.
If you are interested in the development of Maven, please consult the documentation first and afterward you are welcome to join the developers mailing list to ask questions or discuss new ideas/features/bugs etc.
Take a look into the contribution guidelines.
This code is under the Apache License, Version 2.0, January 2004.
See the NOTICE file for required notices and attributions.
Do you like Apache Maven? Then donate back to the ASF to support the development.
If you want to bootstrap Maven, you'll need:
mvn -DdistributionTargetDir="$HOME/app/maven/apache-maven-4.1.x-SNAPSHOT" clean package