Description of problem: EAP Patch Deploy failure messages could be more user friendly / easier to read. In this example, the even elimination of the "java.lang..." text would make the failure message easier to read: Failed to schedule deployment: java.lang.RuntimeException:[1410283498846] javax.ejb.EJBException:java.lang.IllegalArgumentException: Destination [BundleDestination[id=10042, bundle=EAP, group=EAP-Standalone-2, name=ServerBase6.2.0]] group has no members. Invalid deployment destination -> java.lang.IllegalArgumentException:Destination [BundleDestination[id=10042, bundle=EAP, group=EAP-Standalone-2, name=ServerBase6.2.0]] group has no members. Invalid deployment destination Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Deploy an EAP patch that purposely fails. Note the failure message. 2. 3. Actual results: Expected results: Make the deploy EAP patch deploy failure message easier for the user to read. Additional info:
Moving into ER05 as didn't make the ER04 cut.
I talked about the issue with the rest of the team on our call, and there's a reason to keep those exceptionClassnames there (it is easier to assist the customer). Cleaning up all of them would require some changes to every error message we currently do, so I only removed the first "RuntimeException", as it provides no extra value to us. In master: commit 6ad2b57830862470b22afc52c7ab34d3c3226752 Author: Michael Burman <miburman> Date: Fri Oct 3 16:49:16 2014 +0300 [BZ 1139820] Remove one useless exception className from the error message from all Bundle related exceptions
branch: release/jon3.3.x link: https://github.com/rhq-project/rhq/commit/719d7a7af time: 2014-10-08 11:50:25 +0200 commit: 719d7a7afe8e6b5c9119c5e18c55dbe164e5f9a8 author: Michael Burman - miburman message: [BZ 1139820] Remove one useless exception className from the error message from all Bundle related exceptions (cherry picked from commit 6ad2b57830862470b22afc52c7ab34d3c3226752) Signed-off-by: Libor Zoubek <lzoubek>
Moving to ON_QA as available to test with the latest brew build: https://brewweb.devel.redhat.com//buildinfo?buildID=394734