[forge-issues] [JBoss JIRA] (FORGE-803) Promote usage of ShrinkWrap Resolver instead of using Aether directly

[Lincoln Baxter III (JIRA)]

    [ https://issues.jboss.org/browse/FORGE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790854#comment-12790854 ] 

Lincoln Baxter III commented on FORGE-803:
------------------------------------------

What I think makes more sense is to create a ShrinkWrap addon for Forge 2. This would expose the relevant resolution services for those who need to use it in their Addons. 

If people want to use ShrinkWrap resolver in tests, that would obviously depend on if it conflicts with our own Arquillian deployment mechanism, or of we can isolate it effectively enough to do so. 

Currently there is not much need whatsoever for a feature like this, since tests are run against the Addon which is fully resolved by the forge container manager itself, so... not much point really in my opinion since all of the work is already done by Maven and the POM.

I suppose I could see an instance where someone would want to create a test deployment that used some resolved libraries, but again, I don't see that being a very common scenario since the tests more than mostly tend to rely directly on the actual addon under test.
                
> Promote usage of ShrinkWrap Resolver instead of using Aether directly
> ---------------------------------------------------------------------
>
>                 Key: FORGE-803
>                 URL: https://issues.jboss.org/browse/FORGE-803
>             Project: Forge
>          Issue Type: Enhancement
>          Components: Build Tools - Maven
>    Affects Versions: 2.0.0.Alpha1
>            Reporter: George Gastaldi
>
> The MavenDependencyResolver should use ShrinkWrap Resolver APIs instead of using the Aether APIs directly. 
> This is believed to bring some performance enhancements also, due to internal improvements in the latest version of SWR.

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