Closed dflemstr closed 8 years ago
Good idea! Looks a bit weird on my phone though:
In any case, I'm fine with merging it to get us started with something.
@@ master #42 diff @@
========================================
Files 4 4
Lines 61 51 -10
Methods 0 0
Messages 0 0
Branches 3 3
========================================
- Hits 61 51 -10
Misses 0 0
Partials 0 0
...pletableFutures.java
(not in diff) was modified. more
0
0
-10
Powered by Codecov. Last updated by ec9cba9...e89c86e
I see this is a static site - might I suggest you redirect http->https? we did it for the spotify.github.io site with this commit.
@econchick see https://github.com/spotify/completable-futures/pull/46
This creates a Maven site for the project and deploys it to http://spotify.github.io/completable-futures. I didn't add a lot of stuff there; maybe a next step could be to include the README in there too or something.
Maybe most importantly it makes Javadoc available at http://spotify.github.io/completable-futures/apidocs (or http://spotify.github.io/completable-futures/apidocs/com/spotify/futures/CompletableFutures.html) which makes it easier to give people links to the documentation.
I took the liberty to deploy the site from my local machine so that the links above actually work, and set up Travis so that everything should Just Work® when this is merged.
PS. I set this up for this repo in particular because I think we should have Maven sites for all of our Java projects, and this was the smallest project we have in the Spotify org that would let me field test the configuration.