[shrinkwrap-issues] [JBoss JIRA] (SHRINKRES-106) Provide Mechanism to Resolve "provided"- and "test"-scoped transitives, and "optional"

Andrew Rubinger (JIRA) jira-events at lists.jboss.org
Wed Jan 16 04:52:21 EST 2013


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

Andrew Rubinger resolved SHRINKRES-106.
---------------------------------------

    Resolution: Done


Found the magic sauce in Aether, and added some API love to give us hooks.

Upstream: https://github.com/ALRubinger/resolver/commit/af3a87e2b48023e23bd77433567306007289ea47 and https://github.com/ALRubinger/resolver/commit/6e125ced05aa93aff55dc03d353b07a3774c535c.
                
> Provide Mechanism to Resolve "provided"- and "test"-scoped transitives, and "optional"
> --------------------------------------------------------------------------------------
>
>                 Key: SHRINKRES-106
>                 URL: https://issues.jboss.org/browse/SHRINKRES-106
>             Project: ShrinkWrap Resolvers
>          Issue Type: Feature Request
>            Reporter: Andrew Rubinger
>            Assignee: Andrew Rubinger
>             Fix For: 2.0.0-alpha-7
>
>
> We currently support only the default Maven behavior with respect to the resolution of transitive dependencies as documented by: 
>   http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
> In particular, it's currently impossible to resolve "provided" and "test" scope transitives, as well as those marked "optional".  Ales has provided a use case which shall act as the basis for this feature request.

--
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


More information about the shrinkwrap-issues mailing list