Bug 1705758
Summary: | maven packages not updateable/installable | ||
---|---|---|---|
Product: | [Fedora] Fedora Modules | Reporter: | Mattias Ellert <mattias.ellert> |
Component: | maven | Assignee: | Mikolaj Izdebski <mizdebsk> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | jan.public, mizdebsk, per.arnold |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-05-04 17:39:14 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1700323 |
Description
Mattias Ellert
2019-05-02 21:53:33 UTC
As I understand this, the modular version of maven (or the modularity terminology) is hurting the non-modular version of maven. Is there anything the non modular maven package can do to prevent this from happening? Should this be recategorized as modularity bug? > or the modularity terminology
s/terminology/technology
I am aware of the situation and I am working on a fix. Future versions of maven modules will be parallel-installable with ursine maven. This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component. This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component. According to current modules policy [1] modular packages can only exist as alternative versions. Since Maven 3.6 exists as non-modular package in Fedora, modular Maven 3.6 is not allowed according to the policy. [1] https://docs.fedoraproject.org/en-US/modularity/policies/ |