Updated documentation for @NonNull (and the changelog).

doc/changelog.markdown

@@ -4,6 +4,7 @@ Lombok Changelog
 ### v0.8.4
 
 * All generated methods now make their parameters (if they have any) final. This should help avoid problems with the 'make all parameters final' save action in eclipse. [Issue #40](http://code.google.com/p/projectlombok/issues/detail?id=40)
+* Okay, this time _really_ added support for @NonNull and @NotNull annotations. It was reported for v0.8.3 but it wasn't actually in that release. @Nullable annotations are now also copied over to the getter's return type and the setter and constructor's parameters (but, obviously, no check is added).
 
 ### v0.8.3
 

src/lombok/NonNull.java

@@ -33,6 +33,10 @@ import java.lang.annotation.Target;
  * 
  * You can use this annotation for the purpose, though you can also use JSR305's annotation, findbugs's, pmd's, or IDEA's, or just
  * about anyone elses. As long as it is named <code>@NonNull</code> or <code>@NotNull</code>.
+ * 
+ * WARNING: If the java community ever does decide on supporting a single @NonNull annotation (for example via JSR305), then
+ * this annotation will <strong>be deleted</strong> from the lombok package. If the need to update an import statement scares
+ * you, you should use your own annotation named <code>@NonNull</code> instead of this one.
  */
 @Target({ElementType.FIELD, ElementType.METHOD, ElementType.PARAMETER, ElementType.LOCAL_VARIABLE})
 @Retention(RetentionPolicy.CLASS)