You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/04/13 09:59:00 UTC

[jira] [Commented] (MRESOLVER-700) Bundle transport

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

ASF GitHub Bot commented on MRESOLVER-700:
------------------------------------------

cstamas opened a new pull request, #685:
URL: https://github.com/apache/maven-resolver/pull/685

   That is based on slightly improved file transport, that uses FileSystem which can by ZIPFS or JIMFS as well.
   
   WIP




> Bundle transport
> ----------------
>
>                 Key: MRESOLVER-700
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-700
>             Project: Maven Resolver
>          Issue Type: Task
>            Reporter: 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)