Better Algorithm to select a provider

[johnluetke]

At present, the first provider that can fulfill the request is used, even if multiple providers can do so. Is this acceptable? Or should a second algorithm be implemented for when > 1 providers can fulfill a request?

[alexanderdean]

I like the algo you have in master - checking if the provider is configured before attempting a lookup. Any chance of getting this published as a 0.9.4 any time soon?

[johnluetke]

I'm trying to get the build moved to Travis-CI per #7. That's blocking any new releases at the moment

[alexanderdean]

If I can help I will! I am really motivated to help as I just included WeatherAPI in a book chapter that is due in this evening and if I can't get this working, I will have to spend ages removing it and going straight to the WUnderground API...

[johnluetke]

I'm all ears. I have the PGP key file and passphrase, but have been able to integrate them into travis.yml securely

[alexanderdean]

Awesome, thanks for getting 0.9.4 released. BTW my book code using WeatherAPI is here: https://github.com/alexanderdean/Mastering-Event-Streams/blob/master/ch03/3.5/weatherenrich/src/main/java/weatherenrich/WeatherEnrich.java