[jira] [Commented] (MNG-7630) Support listing of workspace models and implement upcomming interface methods

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-7630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17647875#comment-17647875 ] 

ASF GitHub Bot commented on MNG-7630:
-------------------------------------

laeubi opened a new pull request, #913:
URL: https://github.com/apache/maven/pull/913

   ... and implement upcoming interface methods of [MRESOLVER-307](https://issues.apache.org/jira/browse/MRESOLVER-307).
   
   Currently the WorkspaceReader has a way to list versions or resolve the file for an artifact or the model, but there is no way of really get a list of workspace artifacts or models itself.
   
   This adds ways to list artifact and models a WorkspaceReader manages.
   
   Following this checklist to help us incorporate your
   contribution quickly and easily:
   
    - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MNG-7630) filed
          for the change (usually before you start working on it).  Trivial changes like typos do not
          require a JIRA issue. Your pull request should address just this issue, without
          pulling in other changes.
    - [x] Each commit in the pull request should have a meaningful subject line and body.
    - [x] Format the pull request title like `[MNG-XXX] SUMMARY`, where you replace `MNG-XXX`
          and `SUMMARY` with the appropriate JIRA issue. Best practice is to use the JIRA issue
          title in the pull request title and in the first line of the commit message.
    - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
    - [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will
          be performed on your pull request automatically.
    - [ ] You have run the [Core IT][core-its] successfully.
   
   If your pull request is about ~20 lines of code you don't need to sign an
   [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
   please ask on the developers list.
   
   To make clear that you license your contribution under
   the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
    - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   
    - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   [core-its]: https://maven.apache.org/core-its/core-it-suite/
   




> Support listing of workspace models and implement upcomming interface methods
> -----------------------------------------------------------------------------
>
>                 Key: MNG-7630
>                 URL: https://issues.apache.org/jira/browse/MNG-7630
>             Project: Maven
>          Issue Type: Improvement
>            Reporter: Christoph Läubrich
>            Priority: Major
>
> This is the Maven counterpart of MRESOLVER-307.
> As this will be most likely be released in resolver 2.0  only maven can still already have an implementation for the new methods to:
> - show how they would look like
> - if upgrading source is already prepared
> - Maven has an own extension of that interface that should have similar behaviour



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