[
https://issues.apache.org/jira/browse/MRESOLVER-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645945#comment-17645945
]
ASF GitHub Bot commented on MRESOLVER-307:
------------------------------------------
cstamas commented on PR #230:
URL: https://github.com/apache/maven-resolver/pull/230#issuecomment-1346002536
It is a bit japicm as well, see here
https://github.com/siom79/japicmp/issues/201
But presence of "indirection" in form of support class allows us:
* to move iface from source to binary only compat change (then build would
not fail)
* implement any newly added methods in support class, to retain source
compatibility
I bet there are cases like in Maven as well, but somewhere we have to start
:smile:
> Support listing of workspace artifacts
> --------------------------------------
>
> Key: MRESOLVER-307
> URL: https://issues.apache.org/jira/browse/MRESOLVER-307
> Project: Maven Resolver
> Issue Type: Improvement
> Reporter: Christoph Läubrich
> Priority: Major
>
> Currently the WorkspaceReader has a way to list versions or resolve the file
> for an artifact, but there is no way of really get a list of workspace
> artifacts itself.
> The javadoc states:
> {quote}Manages a repository backed by the IDE workspace, a build session or a
> similar ad-hoc collection of artifacts.{quote}
> so the goal is to have a way getting hold of the "collection of artifacts"
> this Workspacereader manages.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
