Bug 927936
| Summary: | RPM: Different content of jansi.jar | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Pavel Janousek <pjanouse> |
| Component: | RPMs | Assignee: | Vaclav Tunka <vtunka> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1.0 | CC: | fnasser, myarboro |
| Target Milestone: | ER4 | ||
| Target Release: | EAP 6.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 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
Pavel Janousek
2013-03-26 14:30:22 UTC
There is no way to get the todo ones into the RPMs, and on the other hand, the jansi in the RPMs (which is not used except to satisfy a module dependency at boot) does not have the Windows binaries, so using that would make the CLI not operational on windows (and probably break QE tests). The only solution for this is to get jansi productized. Lest use this JIRA to track that down. Hi Pavel, thank you for letting us know about RPMxZIP differences, in this isolated use case it's expected difference and it will be absolutely fixed for CR bits. Like Fernando said, this is a limitation of the -todo tag setup for RPMs. RPMs should not contain todos in any case. Cheers, Vaclav Guys, I don't fully understand why we can't use the same 'store of JARs' during building any install bits (like RPM, Installer, ZIP etc.), but in that case it absolutely doesn't make sense for me to build any other distro bits than ZIP before every artifact is productized. It is only time wasting for QE and produces blockers, especially testing RPM and anything on RPM dependent - like AMI images. Why we can't import a todo artifact to the 'store of JARs' and use it for RPM (via MEAD layer of Brew) build as well? ACK with a note that the RPM one is just a placeholder so the server can boot. You could have an empty JAR there, it is not used. jansi is just used on Windows, which means only ZIPs. Verified during EAP-6.1.0-ER4 test cycle, fixed. |