chefhoobajoob

codegen does seem to be working from gradle with this setup:   I get an npm folder in `/src/main` with `package.json` and the other expected files. Just need to...

Yes, was referring to those examples - thank you. I setup the gradle equivalent as a separate build script (es4x-codegen.gradle) where the es4x codegen system properties for the build can...

sure - i'll try to get one up and post the repo link here

hello world example project here: https://github.com/chefhoobajoob/es4x-codegen-gradle

Separately from the webpack changes, it is not possible to run `npm install path-browserify` and expect this require statement to work: ```javascript var path = require('path') ``` ...because there is...

I can create a reproducer, but you can also see the effects in the public vertx API documentation, so there should be lots of examples in the existing code base....

Looking a little closer, it seems that the problem exhibits on class-level javadoc comments, but not on method-level comments. For example, for the [getRecord](https://github.com/vert-x3/vertx-service-discovery/blob/master/vertx-service-discovery/src/main/java/io/vertx/servicediscovery/ServiceDiscovery.java#L259-L272) comments, everything except for `{@link Function}`...

+5 I don't really care what the current case format for a given incoming string is, but whatever it is, I want to convert it to a specific case format....

Any ideas? Is this a bug or a build script problem?

@vietj @cescoffier : any ideas what I should even look for? Still seeing this after updating to use the gradle `java-library` plugin.