Roadmap

For 0.3

Use ServiceProvider (DONE)

A good way for the library to provide a centralized way to register and access bundles.

Discussion here.

printf() support (DONE)

Provide methods .printf(String, Object, Object...) and .printf(Locale, String, Object, Object...) using String.format() to generate messages.

"Precondition" methods (DONE)

Provide .checkNotNull() and .checkArgument() for each bundle, just like Guava's Preconditions.*().

In the future

In order, and maybe/maybe not...

Find, use another site in addition for Maven for jar distribution

More and more people don't use Maven at all (think: Android). For them, obtaining this library is a pain.

Have a look at BinTray.

Dual gradle/maven build

Gradle is becoming more and more prevalent, especially since it is the officially recommended tool by the Android community.

Get head out of black hole and Just Do It(tm).

Legacy ResourceBundle support?

That is, provide a way to read property files using ISO-8859-1.

Not sure whether it is of any use. If this is provided, maybe also provide a conversion utility from these bundles to new bundles?

More generic: support for using "arbitrary" charsets to read property files?

That would be nice. But useful? Good question.

Loading/caching control?

Right now the loading and caching policy is fixed (except you can specify the timeout you want for loading). Give more control? Like, for instance, expiration (which currently doesn't happen)?

Salvage some functionality of ResourceBundle.Control?

Seen on Stack Overflow: you can use the class above to return a list of relevant locales for the locale of your choice. Right now, this logic is hardcoded. Is it worth it to provide an override in this library?

MessageFormat support?

This was in the initial plans. But why use a 20th century technology when you have printf() (which is actually even older, but works miles better)?

Bah. If requested, one day, maybe...