You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2023/04/04 09:04:00 UTC

[jira] [Updated] (DOXIASITETOOLS-294) Replace legacy artifact resolution with Maven Resolver

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

Michael Osipov updated DOXIASITETOOLS-294:
------------------------------------------
    Description: The current artifact resolver has been deprecated for ages and uses {{localRepository}} which is now discouraged as well. Another issue is that the current solution abuses the site descriptor as marker file with zero byte if the descriptor could not be found. This handles Resolver for us without going through loops and hoops.  (was: The current artifact resolver has been depercated for ages and uses {{localRepository}} which is now discouraged as well. Another issue is that the current solution abuses the site descriptor as marker file with zero byte if the descriptor could not be found. This handles Resolver for us without going through loops and hoops.)

> Replace legacy artifact resolution with Maven Resolver
> ------------------------------------------------------
>
>                 Key: DOXIASITETOOLS-294
>                 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-294
>             Project: Maven Doxia Sitetools
>          Issue Type: Improvement
>          Components: Integration Tools
>    Affects Versions: 2.0.0-M5
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 2.0.0-M6
>
>
> The current artifact resolver has been deprecated for ages and uses {{localRepository}} which is now discouraged as well. Another issue is that the current solution abuses the site descriptor as marker file with zero byte if the descriptor could not be found. This handles Resolver for us without going through loops and hoops.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)