[
https://issues.apache.org/jira/browse/MRESOLVER-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17943957#comment-17943957
]
ASF GitHub Bot commented on MRESOLVER-700:
------------------------------------------
cstamas commented on PR #685:
URL: https://github.com/apache/maven-resolver/pull/685#issuecomment-2800148001
Initial idea is really just to disseminate the idea that one can "mount" ZIP
files as remote repositories. Like repository staging, and there, the main use
case is usually to perform some sort of "testing" with newly baked artifacts.
This PR makes Resolver able to _consume_ these bundle ZIP files (essentially
ZIP files containing artifacts laid down on remote repo layout).
> Bundle transport
> ----------------
>
> Key: MRESOLVER-700
> URL: https://issues.apache.org/jira/browse/MRESOLVER-700
> Project: Maven Resolver
> Issue Type: Task
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.9
>
>
> It is becoming more and more common that various services require "zipped up
> bundle" (using remote repository layout) of things like releases. As
> experiment shows, these can be used as "remote repositories" as well (with
> existing classpath transport). What if we have a dedicated transport? As
> before, we defined remote repository that point to a staging repo, but have
> it point to a ZIP file (either local or remote).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
