[
https://issues.apache.org/jira/browse/MRESOLVER-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17943958#comment-17943958
]
ASF GitHub Bot commented on MRESOLVER-700:
------------------------------------------
cstamas commented on PR #685:
URL: https://github.com/apache/maven-resolver/pull/685#issuecomment-2800149950
... aand after I commented, I think figured your point :smile: Yes,
ultimately Resolver 2 could be used to _create_ and _read_ ZIP bundles. But,
IMO we need to be very careful here, like we should allow "create from scratch"
(like ZIP file is created from scratch) or "read created bundle", where you
really just consume bundle for testing purposes. Existing ZIP bundle should not
be modified, or at least, would be risky business.
Njord enforces this: it does not allow you to "export" to already existing
ZIP files for example. But we should somewhere sit down and have a :beers: that
may be followed by a discussion about these things...
> 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)
