[
https://jira.jboss.org/browse/JBIDE-7024?page=com.atlassian.jira.plugin.s...
]
Andre Dietisheim commented on JBIDE-7024:
-----------------------------------------
as you can see by the icon of the log entries, the informations are logged as info (not as
errors).
here's what the javadoc says:
/** Status type severity (bit mask, value 1) indicating this status is informational
only.
* @see #getSeverity()
* @see #matches(int)
*/
public static final int INFO = 0x01;
IMHO it is a matter of the setup to decide whether info-level shall be showed to the
console or not. In other words not creating log entries is wrong (which is always good to
my eyes, the more the better) but showing them in the console is not what users wished.
Verbose messages in Error log after clean JBT installation
----------------------------------------------------------
Key: JBIDE-7024
URL:
https://jira.jboss.org/browse/JBIDE-7024
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: usage
Affects Versions: 3.2.0.M2
Environment: JBT 3.2.0.v20100903-2012-H11-M2, Linux 64
Reporter: Jiri Peterka
Assignee: Andre Dietisheim
Fix For: 3.2.0.Beta
Attachments: verbose-messages.png
Install and start JBT 3.2.m2 on new workspace
See verbose message:(screenshot)
ASSERT: Error log should be empty after clean installation
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira