Link raised issue.

Author: raphaelNguyen

README.md

@@ -1,6 +1,6 @@
 # query-bean-generator-issue
 
-This project illustrate an issue with the ebean query bean generator. Issue as of `ebean` version `15.8.2` can be reproduced by running `mvn compile` on this example project.
+This project illustrate an issue with the ebean query bean generator. Issue as of `ebean` version `15.8.2` can be reproduced by running `mvn compile` on this example project. Issue has been raised at ebean-orm/ebean#3582.
 
 When generating querybeans along side specific other annotation processors (in this case [manifold-exceptions](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-exceptions)), the `querybean-generator` logs an error while trying to write `embedded.example.EbeanEntityRegister` and fails the build (error details below).
 
@@ -47,4 +47,4 @@ With `manifol-exception` added to the path processors, the querybeans generation
 [INFO] ------------------------------------------------------------------------
 ```
 
-The stack trace suggests that this issue happens when the underlying `JavacFiler` is trying to log the exact same `[WARNING]` observed above when running `querybean-generator` version `15.8.2` without `manifold-exceptions` during `JavacFiler.createSourceOrClassFile`. When attempting this, the logging framework found that its `DeferredDiagnosticHandler`'s `deferred` queue is `null` and threw an `NPE` which was captured and formatted into the `[ERROR]` seen above. A quick look at the code suggests that `deferred` queue is only set to `null` when `DeferredDiagnosticHandler.reportDeferredDiagnostics` is called to prevent accidental ongoing use.
+The stack trace suggests that this issue happens when the underlying `JavacFiler` is trying to log the exact same `[WARNING]` observed above when running `querybean-generator` version `15.8.2` without `manifold-exceptions` during `JavacFiler.createSourceOrClassFile`. When attempting this, the logging framework found that its `DeferredDiagnosticHandler`'s `deferred` queue is `null` and threw an `NPE` which was captured and formatted into the `[ERROR]` seen above. A quick look at the code suggests that `deferred` queue is only set to `null` when `DeferredDiagnosticHandler.reportDeferredDiagnostics` is called to prevent accidental ongoing use.