[
https://issues.apache.org/jira/browse/MRESOLVER-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17943959#comment-17943959
]
ASF GitHub Bot commented on MRESOLVER-700:
------------------------------------------
cstamas commented on PR #685:
URL: https://github.com/apache/maven-resolver/pull/685#issuecomment-2800150673
For example we could achieve this by some extra params:
* by default (as in this PR) the ZIP file must exists and is read obly
* if URL has `?create=true` QP, then Resolver could enforce ZIP file does
not exists, and could make it read-write (and would become usable with
`altDeployRepository` for example).
> 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)
