You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2020/03/28 14:59:02 UTC

[jira] [Commented] (MNG-5695) inconsistent custom scope bindings

    [ https://issues.apache.org/jira/browse/MNG-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069548#comment-17069548 ] 

Hudson commented on MNG-5695:
-----------------------------

Build failed in Jenkins: Maven TLP » maven-studies » maven-metrics #4

See https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/4/

> inconsistent custom scope bindings
> ----------------------------------
>
>                 Key: MNG-5695
>                 URL: https://issues.apache.org/jira/browse/MNG-5695
>             Project: Maven
>          Issue Type: Bug
>            Reporter: Igor Fedorenko
>            Assignee: igorfie
>            Priority: Major
>             Fix For: 3.2.5
>
>
> Session scope is only available for maven core and core extensions components (i.e. -Dmaven.ext.class.path stuff), but does not work for components from maven plugins. Mojo execution scope works for components from maven plugins but not for maven core and core extensions. Need to consistently bind custom scopes in all realms.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)