What's brewing in gwt-log trunk- Stay tuned. More to come.
What's new in gwt-log-3.0.1.jarVisible changes- Reintroduction of server side implementations such as Log.isDebugEnabled(). Thanks vruiz.jurado!
Changes under the hood- Project refactoring and simplification
- Introduction of new LogRecord class in preparation for new features
- Improved ant build. Thanks amichail!
What's new in gwt-log-3.0.0.jarNew features- Additional pattern specifiers now supported (%C, %F, %L or %M and %l) in Development Mode (Hosted Mode). See http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html to get an idea of how these work. Thanks omsrobert!
- RemoteLogger sends multiple messages in a single RPC when they are logged within a short period of time
- RemoteLogger more resilient in the face of client server communication failures
- RemoteLogger only uses a single network connection at any given time
- Fix for issue 22 - RemoteLogger now sends messages from a single client to the server in order (although the server does no ordering across multiple clients, so out of order logging is strictly speaking still possible). Thanks terciofilho!
- Server side logging (via RemoteLogger) is no longer hard coded via setCurrentLogLevel(LOG_LEVEL_DEBUG). Thanks Bob Cunius!
General changes in this release- gwt-log.css is now injected via ClientBundle: minification benefits and avoid an extra HTTP roundtrip
- gwt-log.css is no longer injected when logging is turned off
Other changes in this release- Build script fix. Thanks Evely!
- No longer use deprecated PropertyOracle methods which avoid compiler warnings
- Fix for issue 10 in r423 ability to programmatically hide DivLogger. Calling Log.getDivLogger().getWidget().setVisible(false) keeps DivLogger hidden, even when new messages appear. Call Log.getDivLogger().getWidget().setVisible(true) to make DivLogger reappear. Thanks pohl.longsine!
- Remove workaround for GWT issue 1934 WindowResizeListener#onWindowResized fires too often in IE
What's new in gwt-log-2.6.2.jarGeneral changes in this release- Support for GWT's new user-agent value ie8
What's new in gwt-log-2.6.1.jarBug Fixes- Workaround for GWT issue 3791 affecting anyone using logging code inside of GWTTestCase. Thanks praveen.kumar.jayaram, dwself, pcniatic, dgantenbein (Dorothy)!
What's new in gwt-log-2.6.0.jarNew features- Control the format of your log messages
<!--
Inspired by Apache log4j PatternLayout:
http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html
-->
<set-configuration-property name="log_pattern" value="%d [%-5p] %m%n" />General changes in this release- Allow logging to work easily on Google App Engine
- Got rid of explicit call outs to ConsoleHandler so that application developers can better control their own log output when using java.util.logging on the server, i.e.
replaced: logger = Logger.getLogger("gwt-log");
logger.setUseParentHandlers(false);
ConsoleHandler consoleHandler = new ConsoleHandler();
consoleHandler.setLevel(Level.ALL);
logger.addHandler(consoleHandler);with: logger = Logger.getLogger("gwt-log");- Updated code base to use new GWT 1.6 features
- Listeners -> Handlers
- Use new war directory structure
Eclipse project related changes- Update Log Eclipse project to use new Eclipse plugin
- Merged separate LogClientServerDemo Eclipse project into main Log project
- Project uses super-src mechanism to pull in client side versions of *.java classes
What's new in gwt-log-2.5.3.jarBug Fixes- Prevent extraneous 'null' messages logged by RemoteLogger when no exception is passed. Thanks Thomas Vidal!
What's new in gwt-log-2.5.2.jarBug Fixes- Fix broken ant build file causing UnsupportedOperationException: ERROR: GWT.create() is only usable in client code! in server code. Thanks Vicente J. Ruiz Jurado!
What's new in gwt-log-2.5.1.jarBug Fixes- Fix for issue 15 , DivLogger failing to auto scroll in Firefox and Mozilla 1.5 (Linux hosted mode). Thanks borice!
New Functionality- Add ability to catch exceptions in code called from JSNI setTimeout() or setInterval(). This feature is available in Firefox and IE only. However, Safari and Opera will allow you access to the same information from their native JavaScript (debug) consoles
- Support for TRACE level logging (in addition to existing levels DEBUG, INFO, WARN, ERROR, FATAL, OFF)
- New log level specific modules to inherit from so that a default other than OFF can be selected for your application, e.g.
<inherits name="com.allen_sauer.gwt.log.gwt-log-WARN" /> Other Changes- Reduced RemoteLogger noise, especially when multiple clients are involved. No longer output the log delimiter message during initialization (for each client). Thanks Rafal!
What's new in gwt-log-2.5.0.jarNew Functionality- New experimental WindowLogger which can be enabled in your application's *.gwt.xml by adding:
<!--
Enable experimental WindowLogger, which logs messages to a separate
popup window. There are currently a couple of restrictions:
1. When Firefox is configured to open new Windows as new tabs,
WindowLogger does not work
2. In hosted mode, the windows are not automatically closed,
although you can easily close them manually in the usual way
-->
<set-property name="log_WindowLogger" value="ENABLED" />
<!--
You probably will want to disable the default `DivLogger` as well:
-->
<set-property name="log_DivLogger" value="DISABLED" />General changes in this release- Wrap/unwrap client thrown exceptions to:
- Reduce RPC surface area (reduction in size of compiled code)
- Prevent RPC errors when non-Serializable exceptions are logged client-side
Bug Fixes- gwt-log issue 13: Logging a null message results in NPE. Thanks rintcius!
Other updates- Javadoc updates
- Minor updates to online demo, including new log null message button
- Ant build changes
What's new in gwt-log-1.5.6.jarNew Functionality- Improved code completion for IDEs
What's new in gwt-log-1.5.5.jarBug Fixes- Improved DivLogger resizing
What's new in gwt-log-1.5.3.jarBug Fixes- Disable ConsoleLogger when FirebugLogger is available, to prevent duplicate messages for Firebug users
- issue 9 Disabling and re-enabling Firebug causes the FirebugLogger to be removed, rather than begin throwing JavaScript exceptions.
New Functionality- DivLogger user interface updates:
- Control runtime log level
- Clear the log (issue 5)
- Resize log panel
- Show 'About' information
- Emit a message when runtime log level is changed, to prevent developers from believing they have eliminated overhead caused by logging
- Loggers which throw exceptions are now automatically removed; Previously there was a special case for RemoteLogger RPC failures
Other Changes- Javadoc updates
- Eclipse project changes
- New internal diagnostic logging method
- Various internal changes
What's new in gwt-log-1.5.2.jarNew Functionality- Remote logging, i.e. sending a copy of messages logged on the client to the server, via
<set-property name="log_RemoteLogger" value="ENABLED" /> Ability to configure loggers from your module, with these defaults: <!-- Enabled by default -->
<set-property name="log_ConsoleLogger" value="ENABLED" />
<set-property name="log_DivLogger" value="ENABLED" />
<set-property name="log_FirebugLogger" value="ENABLED" />
<set-property name="log_GWTLogger" value="ENABLED" />
<set-property name="log_SystemLogger" value="ENABLED" />
<!-- Disabled by default -->
<set-property name="log_RemoteLogger" value="DISABLED" /> Other Changes- Removed Log#removeLogger method in favor of deferred binding properties
- Updated JDK 1.4 gwt-log logger to be configured with a ConsoleHandler at the ALL level as the JDK implementation default is SEVERE and would unexpectedly hide debug/info/warn messages
- Various minor implementation changes
What's new in gwt-log-1.5.1.jarNew Functionality- Serializable classes (domain objects, POJOs, etc.) can utilize the same logging code on client and server via inclusion of a single, common, gwt-log jar on both tiers
- Server side logging automatically detects Apache log4j, falling back to JDK 1.4 logging
Other Changes- Removed ability to extend existing log levels for reduced complexity; please file an issue if you absolutely must have this ability
- Class LoggerSystem renamed to SystemLogger for consistency
- Public Logger#log changed accessibility to package default
- Updated project and ant build file
What's new in gwt-log-1.4.5.jarBug Fixes- Issue 6 Throwable with null message, e.g. throw new NullPointerException(), would fail to get logged; instead an exception would be logged in the hosted mode tree logger regarding the gwt-log failure. Thanks dwyah!
What's new in gwt-log-1.4.4.jarChanges in this version- DivLogger text area now resizes itself with the browser window to roughly 80% of the client window width and 20% of the height, but always at least 300px x 100px. To set an explicit size in your application use something like:
.log-panel .log-scroll-panel {
width: 800px !important;
height: 150px !important;
}Hovering over log messages and stack traces shows a tool tip with the most essential portion of the error message, which should greatly reduce the amount of scrolling required in the log panel 
In the DivLogger, all messages, except for stack traces, wrap, rather than scroll off the right hand side, which again, this should reduce the amount of log panel scrolling Logger#removeLogger is now static. Thanks steven.marcus! ant build file, checkstyle and other Eclipse project changes
What's new in gwt-log-1.4.3.jarChanges in this version- Compile time log_level parameter is now set to a single value (OFF) by default instead of generating all six (DEBUG, INFO, WARN, ERROR, FATAL, OFF) deferred binding combinations.
- Additional compile time values can of course be added via extend-property, typically:
<extend-property name="log_level" values="DEBUG,OFF"/> The default value may be overridden via set-property, typically: <set-property name='log_level' value='DEBUG'/> See gwt-log.xml for additional documentation on how to control the compile time and runtime log levels of your application.
What's new in gwt-log-1.4.1.jarChanges in this version- Implemented deferred binding to allow for client and library related logging code to be compiled out by the GWT Compiler dead code elimination when log_level=OFF.
- Changed module name from com.allen_sauer.gwt.log.Log to com.allen_sauer.gwt.log.gwt-log.
- Please see the updated GettingStarted wiki for additional details.
What's new in gwt-log-1.3.1.jar- Release 1.3.1 is not new. It's old :).
|
