I can confirm that this error still occurs now that 1.8 is no longer a snapshot... Are we allowed to report this as a bug now?
I can confirm that this error still occurs now that 1.8 is no longer a snapshot... Are we allowed to report this as a bug now?