Ah okay, then that's the fault.
The engine does not distribute every dependency as a jar anymore (due to maven central policies and such), but the SDK needs them.
So you have to call
build_engine.sh in your git shell or manually downloading the engine and run
gradlew install on the engine source code, so it is built and placed in your "
local maven server" (The
Keep an eye on the engine version though, e.g. when you don't checkout the v3.1.0-stable tag, you might need to change the used engine version in the sdk's
build.gradle, but you will quickly notice that
Edit: If step 2 (cd to the sdk directory) means that you opened cmd in the sdk directory then it's fine. Just note that if you have some code with an actual sdk folder, it's 3.1-alpha1 or older.