this was something I brought up several weeks ago - I think on this mailing list (so there should be a thread on it somewhere).
By using the OBF mode, we obfuscate as well as shrink the size of the JavaScript code. It makes loading and running the client app faster at the expense of these obfuscated stack traces.
If you are in development mode, you can turn off the OBF mode and go back to the regular mode we were used to building with and get those meaningful stack traces.
IIRC, we talked about building two apps in the distro - one (the default) build with OBF and thus faster, and another build in "debug" mode so we can get stacks. Users can switch if they are debugging an issue. If we can't ship in the distro, we'd at least have the "debug" app squirreled away somewhere for people to install and use if debugging is necessary.
Again, this was all discussed somewhere- I just can't remember where :)
----- Original Message -----
Am 11.04.2012 um 20:31 schrieb Charles Crouch:
I thought the change in stacktrace came from the "optimize" javascript option MikeT added a few weeks ago, which vastly reduced the size of the initial
THis may be the cause - I have not heard of that before and saw it for the first time in the UI after I did a non-draft compile.
If we have those abbreviated stack trace classes, then we should filter them out in messages, as they are only annoying to the end user and do not even deliver us any value when a user copy&pastes them in a BZ (or support ticket).
Heiko
-- Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, Werner-von-Siemens-Ring 14, D-85630 Grasbrunn Handelsregister: Amtsgericht München HRB 153243 Geschaeftsführer: Mark Hegarty, Charlie Peters, Michael Cunningham, Charles Cachera
rhq-devel mailing list rhq-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/rhq-devel