[forge-issues] [JBoss JIRA] (FORGE-1661) project-add-dependency ignore new scope

[Aslak Knutsen (JIRA)]

     [ https://issues.jboss.org/browse/FORGE-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aslak Knutsen updated FORGE-1661:
---------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/forge/core/pull/403

    
> project-add-dependency ignore new scope
> ---------------------------------------
>
>                 Key: FORGE-1661
>                 URL: https://issues.jboss.org/browse/FORGE-1661
>             Project: Forge
>          Issue Type: Bug
>          Components: Projects
>    Affects Versions: 2.1.1.Final
>            Reporter: Aslak Knutsen
>            Assignee: Aslak Knutsen
>             Fix For: 2.x Future
>
>
> When you have a bom defined in depmgm that include the dep you're trying to add as a direct dependency, you will get the question: This is a managed resource, would you like to include this version?
> When you attempt to add a reference to a managed dependency in a given scope, the new scope is ignored if you say yes to not override the managed version. 
> Take Arquillian as an example, arquillian-bom is defined in depmgm.
> project-add-dependencies org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-depchain::test:pom
> Do you like to use managed version? Y
> Results in:
> org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-depchain:::pom
> Resolver is now in Compile scope. Wanted Test scope.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira