[forge-issues] [JBoss JIRA] (FORGE-2217) Migrate from Aether to Maven public API

[Lincoln Baxter III (JIRA)]

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

Lincoln Baxter III closed FORGE-2217.
-------------------------------------
    Resolution: Won't Fix


While this would fix the problem, given that the Maven APis don't appear to support the functionality we need, we will need to solve it another way (if possible, in the Mojo itself, by avoiding the API conflict situation entirely. Not ideal, but... not much choice.) 

> Migrate from Aether to Maven public API
> ---------------------------------------
>
>                 Key: FORGE-2217
>                 URL: https://issues.jboss.org/browse/FORGE-2217
>             Project: Forge
>          Issue Type: Component  Upgrade
>          Components: Build Tools - Maven
>    Affects Versions: 2.14.0.Final
>            Reporter: Lincoln Baxter III
>             Fix For: 2.14.1.Final
>
>
> See: https://github.com/jboss-switchyard/tools/pull/377/files
> Related to FORGE-2184
> [~fbricon] - Do you have any information about how we might do this? Can Forge even replace the following code with this higher level Maven API? Does it allow us to customize the resolution process?
> Our custom stuff is here:
> https://github.com/forge/furnace/blob/master/manager/resolver/maven/src/main/java/org/jboss/forge/furnace/manager/maven/addon/MavenAddonDependencyResolver.java
> And here:
> https://github.com/forge/core/blob/master/maven/impl/src/main/java/org/jboss/forge/addon/maven/dependencies/MavenDependencyResolver.java



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)