Hi,

Andrea reported that the 0.1.2 release (see [1]) contains the wrong version number (0.2.0).

This artifact was already pushed to maven central.

On IRC we had the following idea:

* update master to 0.1.2-SNAPSHOT

* perform the release again (that hopefully will result in 0.1.2 on maven central)

That still means we have a 0.2.0 on maven central. I will ask my contacts at Sonatype to remove the 0.2.0 bits;

If folks are OK w/ that, I am happy to perform these steps by Monday morning

Greetings,

Matthias