[ https://issues.apache.org/jira/browse/MRESOLVER-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645919#comment-17645919 ]
ASF GitHub Bot commented on MRESOLVER-307: ------------------------------------------ laeubi commented on PR #230: URL: https://github.com/apache/maven-resolver/pull/230#issuecomment-1345910655 > implements this class, but also Tycho, m2e Tycho/m2e is actually the reason I'd like to have such method :-) > so a LOT of breakage here... That's the question, do we really "break" anything? As it is a default implemented method, everything will compile as before and no one will really notice even though it is not 100% binary compatible. > Ideally, I'd make this in 2.0 of resolver, Is there actually any plan for 2.0 release anywhere soon or is it more "sometimes in the future"? Should I target another branch? If 2.x is the way to go I'll update this to not use a default method then, beside this do you think this can be done that way or are there any other concerns? > and would introduce "safety measures" like for the rest: iface directly should not be implemented, but provide a "support class"? What do you mean by "support class"? And how is it more safe than in interface? I think interfaces are more appropriate for this and are as safe as an (abstract) class? > 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)