- | Maven or Ivy |
+
| Maven or Ivy |
Lombok is in maven central. More… |
| Javac |
@@ -53,10 +53,10 @@
| NetBeans |
Just put lombok.jar on the classpath and enable annotation processing. More… |
- | Eclipse and STS |
- Run lombok.jar as a java app (i.e. doubleclick it, usually) to install. Also add lombok.jar to your project. |
+ | Eclipse and variants |
+ Run lombok.jar as a java app (i.e. doubleclick it, usually) to install. Also add lombok.jar to your project. Supported variants: Springsource Tool Suite, JBoss Developer Studio |
- | IDEA IntelliJ |
+
| IDEA IntelliJ |
lombok doesn't (yet) work under IntelliJ. We're working on it though! |
| Javadoc |
@@ -68,7 +68,7 @@
| GWT |
Lombok works with GWT. More… |
- | Play! Framework |
+
| Play! Framework |
Use Aaron Freeman's lombok play plugin. |
| ecj |
diff --git a/website/features/Log.html b/website/features/Log.html
index fb529426..2fb91956 100644
--- a/website/features/Log.html
+++ b/website/features/Log.html
@@ -16,9 +16,9 @@
Overview
NEW in lombok 0.10: You can annotate any class with a log annotation to let lombok generate a logger field.
- The logger is named log and field's type depends on which logger you have selected.
+ The logger is named log and the field's type depends on which logger you have selected.
- There are four choices available:
+ There are six choices available:
@CommonsLog
- Creates
private static final org.apache.commons.logging.Log log = org.apache.commons.logging.LogFactory.getLog(LogExample.class);
@@ -26,6 +26,8 @@
- Creates
private static final java.util.logging.Logger log = java.util.logging.Logger.getLogger(LogExample.class.getName());
@Log4j
- Creates
private static final org.apache.log4j.Logger log = org.apache.log4j.Logger.getLogger(LogExample.class);
+ @Log4j2
+ - Creates
private static final org.apache.logging.log4j.Logger log = org.apache.logging.log4j.LogManager.getLogger(LogExample.class);
@Slf4j
- Creates
private static final org.slf4j.Logger log = org.slf4j.LoggerFactory.getLogger(LogExample.class);
@XSlf4j
diff --git a/website/features/SneakyThrows.html b/website/features/SneakyThrows.html
index 0f04b7d9..808a7879 100644
--- a/website/features/SneakyThrows.html
+++ b/website/features/SneakyThrows.html
@@ -64,7 +64,11 @@
statement in a try/catch block with just e.printStackTrace() in the catch block. This is so spectacularly non-productive
compared to just sneakily throwing the exception onwards, that Roel and Reinier feel more than justified in claiming that the
checked exception system is far from perfect, and thus an opt-out mechanism is warranted.
-
+
+ If you put @SneakyThrows on a constructor, any call to a sibling or super constructor is excluded from the @SneakyThrows treatment. This is a
+ java restriction we cannot work around: Calls to sibling/super constructors MUST be the first statement in the constructor; they cannot be placed inside try/catch blocks.
+
+ @SneakyThrows on an empty method, or a constructor that is empty or only has a call to a sibling / super constructor results in no try/catch block and a warning.