[00:10:50] <jtruelove> okay cool, no wonder stuff was blowing up
[00:11:12] <jtruelove> i was looking at the published dates on the artifacts and was like why is that so far behind
[00:11:28] <jtruelove> vertx3 the renaming nightmare :)
[08:29:49] *** ChanServ sets mode: +o temporalfox
[12:42:26] <purplefox_> temporalfox: pmlopes cescoffier do you guys have a link to the google doc 3.1 roadmap we discussed?
[15:09:26] <Pratapn> Hi
[15:12:49] <Pratapn> Had a question about the Routing context … is it a good practice to pass the routing context between the verticals ? What i am trying to achieve is a flow where i dont use message relpy instead pass routingContext (has httpresponse inside ) around and the last vertical which will flush out the output using the http response and close the context
[15:13:10] <Pratapn> Is this a good practice ??
[16:06:17] <pmlopes> purplefox_ temporalfox cescoffier: i've got vert.x3 to work with npm as we discussed today
[16:06:40] <cescoffier> pmlopes: you mean a NPM to deploy vert.x ?
[16:08:47] <pmlopes> https://gist.github.com/pmlopes/e7ec5d0d2499577d1512
[16:09:03] <cescoffier> oh cool !
[16:09:26] <cescoffier> well, tricky question… windows ?
[16:09:27] <pmlopes> i mean that for JS devs they can just use npm to code, it should feel more familiar than having maven
[16:10:25] <pmlopes> i haven't tested it yet but i also ship the bat file so it might work i need to revive my windows laptop, probably it will take years to start due to windows updates ;P
[16:11:31] <cescoffier> don't worry can test it
[16:12:31] <cescoffier> just for info http://dev.modern.ie/tools/vms/
[16:12:38] <cescoffier> they provide windows VM to test internet explorer
[16:13:08] <cescoffier> you just need virtual box
[16:13:42] <cescoffier> so, if I understand correctly we just need the package.json file in the stack directory
[16:13:51] <cescoffier> and do a npm install; npm publish
[16:14:31] <cescoffier> you would need a README.md file too (don't do like me, I messed up this part in my vertxbus.js npm)
[16:15:04] <cescoffier> could you post on the gist your package.json ?
[16:21:07] <pmlopes> this is what i did: https://gist.github.com/pmlopes/9f18f63b35dc58fe786a
[16:21:17] <pmlopes> the readme files are different per stack
[16:22:56] <purplefox_> pmlopes: cool!
[16:38:59] <tsegismont> Hey guys. Hope you're all doing well.
[16:39:34] <tsegismont> I've added a few lines of doc for reading unsigned numbers in io/vertx/core/buffer/package-info.java
[16:39:45] <tsegismont> How can I check the result in the docs?
[16:40:24] <cescoffier> pmlopes: That's really cool
[16:40:33] <cescoffier> pmlopes: I'm going to automate that in our build process
[16:41:08] <cescoffier> tsegismont: `mvn clean install` - then open target/docs/vertx-core/java/index.html
[16:41:15] <cescoffier> (let me check the right path)
[16:41:23] <pmlopes> cescoffier: yes it should be part of it but i was just finding a way to get it to work
[16:41:48] <tsegismont> cescoffier, simple as that, cool :)
[16:42:14] <tsegismont> cescoffier, does it generate the doc for all languages?
[16:42:19] <cescoffier> tsegismont: it uses the default asciidoctor theme, but it gives you a good diea
[16:42:22] <cescoffier> idea
[16:43:01] <cescoffier> tsegismont: nope, for core, each language generates the documentation.
[16:43:16] <tsegismont> ha
[16:44:20] <tsegismont> Ok, thanks!
[16:44:26] <cescoffier> pmlopes: look how I did the NPM for vertxbus (in web) - I use the maven-frontend-plugin to download node and do the work
[16:44:43] <cescoffier> tsegismont: you may want to skip the tests
[16:44:50] <tsegismont> cescoffier, I did :)
[17:06:17] <tsegismont> So comments in example files are kept in Java lang doc only
[23:32:56] <TheSteve0> any docker containers for Vert.x 3 yet?