Archimedes Trajano

I was curious what was causing it so I did ``` final VertxOptions vertOptions = new VertxOptions(); vertOptions.setWarningExceptionTime(1); ``` Based on the output below, I sort of like this idea...

For the most part I would think just setting final VertxOptions vertOptions = new VertxOptions(); vertOptions.setMaxEventLoopExecuteTime(3000000000L); Should be more than sufficient and adjust accordingly to your environment. However, you have...

I think a more "proper" but less performant fix would be to have it start up in a blocking context so it is not initialized as part of the event...

Well for my case I put some of the larger initialization on a blocking queue and enable the route once it is fully initialized. In my case creating a Jersey...

The link ends up with a 404

There's no need to break backward compatibility. The annotations are add-ons. Basically you have the following as equivalent ``` /** * @opt foo * @opt bar */ public class Mine...

We can do it a hacky way by making it update the source to put in the "@opt" tags in the generated javadoc. However, this will not help with JDK9+....

Mind you the way UMLGraph has it now with UMLOptions adds code for the VM as well.

@kno10 can CLASS retention be usable for JavaDoc? Class retention makes the class size bigger but the data is not available in runtime so the VM memory shouldn't be impacted...

@ekaratarakis almost (I am talking about custom **annotations** not **tags**) I don't want to break compatibility by adding support for the Java Annotations that are UMLGraph specific.