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

Posted to issues@maven.apache.org by "Robert Scholte (Jira)" <ji...@apache.org> on 2019/10/25 15:45:00 UTC

[jira] [Assigned] (MSHARED-817) Change eclipse aether dependency scope to provided

     [ https://issues.apache.org/jira/browse/MSHARED-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte reassigned MSHARED-817:
--------------------------------------

    Assignee: Robert Scholte

> Change eclipse aether dependency scope to provided
> --------------------------------------------------
>
>                 Key: MSHARED-817
>                 URL: https://issues.apache.org/jira/browse/MSHARED-817
>             Project: Maven Shared Components
>          Issue Type: Improvement
>          Components: maven-artifact-transfer
>            Reporter: Gabriel Belingueres
>            Assignee: Robert Scholte
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In order to collect dependencies (see MSHARED-801), access is needed to use many aether classes. The current strategy is to shade some necessary aether classes into the artifact-transfer jar file but this won't work for collecting because it will actually force to use those classes of the specific aether 0.9.0.M2 fixed version shaded in the jar at build time, and this implies there won't be using the local distribution aether version any longer.
> However, to use the local Maven distribution version of aether, their classes need to be explicitly imported to be available.



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