Bug 1579749
| Summary: | xmvn 3.0.0-14.fc28 not compatible with JDK 10 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Severin Gehwolf <sgehwolf> |
| Component: | xmvn | Assignee: | Mikolaj Izdebski <mizdebsk> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 28 | CC: | java-sig-commits, mat.booth, mizdebsk, msrb |
| Target Milestone: | --- | Keywords: | Upstream, VerifiedUpstream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | xmvn-3.0.0-15.fc28 xmvn-3.0.0-16.fc29 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-04-09 18:14:08 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: | |||
|
Description
Severin Gehwolf
2018-05-18 09:02:25 UTC
This is already fixed, but buildroot override was unexpectedly untagged. Upstream fix: https://github.com/fedora-java/xmvn/commit/620ef70119be6410c438a40e9ba5a30296975509 xmvn-3.0.0-17.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-00031e9c1c xmvn-3.0.0-17.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-00031e9c1c xmvn-3.0.0-17.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-00031e9c1c xmvn-3.0.0-17.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report. |