[
https://issues.apache.org/jira/browse/MNG-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16847322#comment-16847322
]
Benedikt Ritter commented on MNG-6659:
--------------------------------------
I guess it must be somewhere here:
[https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/lifecycle/internal/LifecycleDependencyResolver.java#L234-L273]
maybe moving the `eventSpyDispatcher.onEvent( result )` to the top of the
catch block would fix the problem?
> DependencyResolutionResult not fired when dependency resolutions fails
> ----------------------------------------------------------------------
>
> Key: MNG-6659
> URL: https://issues.apache.org/jira/browse/MNG-6659
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.6.1
> Reporter: Benedikt Ritter
> Priority: Major
>
> When dependency resolution starts Maven fires a DependencyResolutionRequest
> event object. After dependencies have been resolved a
> DependencyResolutionResult event is fired. The problem is, that the result is
> only fired if dependency resolution is successful. If dependency resolution
> fails, one has to listen for ExecutionEvent carrying a LifeCycleException
> with DependencyResolutionException as cause. The
> DependencyResolutionException will have the DependencyResolutionResult
> containing the cause of why resolution failed.
> It would be great if the DependencyResolutionResult would be fired as an
> event even if dependency resolutions fails.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
