aboutsummaryrefslogtreecommitdiff
path: root/website/features
diff options
context:
space:
mode:
authorReinier Zwitserloot <reinier@zwitserloot.com>2014-02-10 21:56:35 +0100
committerReinier Zwitserloot <reinier@zwitserloot.com>2014-02-10 21:56:35 +0100
commitd78135180c8f9e9f4c6c361679759d3eacb63be3 (patch)
tree6450085e10d9dfd9dc901d8cc837727d7372bf09 /website/features
parentdb24fd42c5732856a894dbdc5e1827ea31792757 (diff)
downloadlombok-d78135180c8f9e9f4c6c361679759d3eacb63be3.tar.gz
lombok-d78135180c8f9e9f4c6c361679759d3eacb63be3.tar.bz2
lombok-d78135180c8f9e9f4c6c361679759d3eacb63be3.zip
[deps] Updated eclipse deps to 3.9 tree. This also enables testing java7 features on ecj.
[Log] updated naming for @Log (topic= instead of mchmulder's 'value').
Diffstat (limited to 'website/features')
-rw-r--r--website/features/Log.html7
1 files changed, 2 insertions, 5 deletions
diff --git a/website/features/Log.html b/website/features/Log.html
index e6b3ece6..bc9e017e 100644
--- a/website/features/Log.html
+++ b/website/features/Log.html
@@ -34,7 +34,7 @@
<dd>Creates <code><span class="keyword">private&nbsp;static&nbsp;final&nbsp;</span><a href="http://www.slf4j.org/api/org/slf4j/ext/XLogger.html">org.slf4j.ext.XLogger</a>&nbsp;<span class="staticfield">log</span>&nbsp;=&nbsp;<a href="http://www.slf4j.org/apidocs/org/slf4j/ext/XLoggerFactory.html#getXLogger(java.lang.Class)">org.slf4j.ext.XLoggerFactory.getXLogger</a>(LogExample.<span class="keyword">class</span>);</code></dd>
</dl>
</p><p>
- By default, the category (or name) of the logger will be the type where the annotation was placed. This can be customised by specifying a value for the category.
+ By default, the topic (or name) of the logger will be the class name of the class annotated with the <code>@Log</code> annotation. This can be customised by specifying the <code>topic</code> parameter. For example: <code>@XSlf4j(topic="reporting")</code>.
</p>
</div>
<div class="snippets">
@@ -54,10 +54,7 @@
<p>
If a field called <code>log</code> already exists, a warning will be emitted and no code will be generated.
</p><p>
- A future feature of lombok's diverse log annotations is to find calls to the logger field and, if the chosen logging framework supports
- it and the log level can be compile-time determined from the log call, guard it with an <code>if</code> statement. This way if
- the log statement ends up being ignored, the potentially expensive calculation of the log string is avoided entirely. This does mean
- that you should <em>NOT</em> put any side-effects in the expression that you log.
+ A future feature of lombok's diverse log annotations is to find calls to the logger field and, if the chosen logging framework supports it and the log level can be compile-time determined from the log call, guard it with an <code>if</code> statement. This way if the log statement ends up being ignored, the potentially expensive calculation of the log string is avoided entirely. This does mean that you should <em>NOT</em> put any side-effects in the expression that you log.
</p>
</div>
</div>