Hi Håvard,
This bug has been reported to us a few times and has been fixed for the 5.3.1 release. Hard-coding the dependency is the only workaround other than using Gradle instead of Maven, but that will only be necessary until 5.3.1.
Hi Håvard,
This bug has been reported to us a few times and has been fixed for the 5.3.1 release. Hard-coding the dependency is the only workaround other than using Gradle instead of Maven, but that will only be necessary until 5.3.1.