[
https://issues.apache.org/jira/browse/MRESOLVER-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17944362#comment-17944362
]
ASF GitHub Bot commented on MRESOLVER-700:
------------------------------------------
cstamas commented on PR #685:
URL: https://github.com/apache/maven-resolver/pull/685#issuecomment-2801677839
Just one remark (somewhat related to this PR): While I worked on [Njord
0.1.2](https://github.com/maveniverse/njord/releases/tag/release-0.1.2)
release, I figured that **even if we allow bundle creation with Resolver**
(like the above mentioned `?create=true` QP), the bundle would be usable for
central publishing **only**, which is I think still fine. But for more advanced
control and support, like bundle merging, validating for requirements,
managing, etc you'd need advanced tools like Njord is. Also, this way created
bundle would **not be usable with Njord** (lack of metadata). Still, this
functionality would provide one single building block needed for Central
Publishing: the ZIP bundle itself. But how user would publish it, etc, would
**NOT be solved**.
> 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)
