Red Hat Bugzilla – Bug 996941
Product logo not present in Administration Console
Last modified: 2015-02-01 18:00:11 EST
Created attachment 786489 [details]
Admin console in EAP 6.1.1 ER5
Admin console in EAP 6.1.1 ER5 contains text "EAP" instead of logo "welcome-content/images/prod_name.png". This image is present in bits but is not referenced. See attached screenshot.
Created attachment 786493 [details]
Admin console in EAP 6.1.1 ER4 with prod_name image
Created attachment 786532 [details]
Header changed in ER5 since ER4
According to Header.java diff between ER5 and ER4 in hal/core, I believe this is an planed change.
So if we want to get the product logo image back, maybe need to create a feature request to upstream project.
It is a regression, not a feature.
Related upstream issue:
Expected branding and versioning solution:
"Red Hat JBoss Enterprise Application Platform" logo should be in the header. Note that we need a new logo image with "Red Hat" at the beginning of it. I will attached the current one I have from brand in both svg and eps format. I can create another format if needed, or we can get another logotype from brand if this one does not work for any reason.
There should be NO version in the header of the application. The version number should be removed.
The footer contains the version number, and this should accurately reflect the current version of the software.
There are several options to solve the issue
1. Stick with the current solution: The console header will render the text "EAP 6.1.1". This will require no new HAL console release.
2. Change the product name to a more meaningful name like "JBoss EAP". This needs a modification of the MANIFEST.MF in the module "org.jboss.as.product", slot "eap". However it's not sure if this will have any side effects. After the modification the header will show the text "JBoss EAP 6.1.1". This will require no new HAL release.
3. Go back to the old solution and display an image in the header (see attachment). This will require a new HAL release.
Some background: The reason why we replaced the image with a textual representation of the product name, is that HAL targets many different layered products. Providing a logo for every possible product, would be very difficult.
If we choose to use the old logo (option 3). We can supply a new HAL release early next week.
Created attachment 787232 [details]
I'm not understanding why we have the version number as part of this product name area. There is another version number in the footer that does not match. Can you please explain this more?
My preference would still be towards #3, but maybe I don't understand the 'problem' of having many product logos. How is having a list of product logo images and sourcing in the correct one during the productization process difficult exactly? Just trying to understand the problem more!
Prepared HAL 1.5.7.Final which restores the former logo. The version is not yet released but in the nexus staging area. I will finish the release once we agree to use it for EAP 6.1.1
Are we able to use the new product logo instead of the old one since it has the proper branding? I can turn it into a png file if that is what is required.
Until there is no well defined workflow who is gojng to provide these logo's and at what point, I am going to reject this request from a dev point of view (flagged appropriatly).
@Catherine Once the provisiong of product logo's (for each and every product that builds on EAP) is in place, we can revisit this requirement.
There are no changes allowed in branding for 6.1.1 release, thus missing logo is regression against 6.1.0.GA from QE point of view. As there is going to be ER7 build for 6.1.1 anyway we would like to have this fixed - as previously discussed with Mark and Harald.
Harald Pehl <email@example.com> updated the status of jira HAL-143 to Resolved
PR to revert to the old logo: https://github.com/jbossas/jboss-eap/pull/297
Verified for EAP 6.1.1 ER7
Heiko Braun <firstname.lastname@example.org> updated the status of jira HAL-143 to Closed