Build overhaul

[weisJ]

See #412

This time gradle is rewired to use the old source/resource locations.

The only thing which couldn't be avoided is to move the test resources into their own directory. This is due to the nature of the java-library package.

Github history is preserved this time: e.g. https://github.com/gurkenlabs/litiengine/commits/136a19900ca8d5a79b760d2c90ab6f9d0646be44/src/de/gurkenlabs/litiengine/Game.java

[weisJ]

This PR doesn’t include the automatic formatting through spotless. I can add it back in or create a separate PR.

[nightm4re94]

This PR doesn’t include the automatic formatting through spotless. I can add it back in or create a separate PR.

I think it's best to open another PR for that once everything else is back in order.
Thank you!

[nightm4re94]

Thanks for addressing the open issues :) Is this PR now ready for review?

[weisJ]

Yes it is :)

[nightm4re94]

This has been a huge improvement - we really appreciate the effort you've put into this PR! <3

[weisJ]

I’d suggest providing a new version for utiliti with the jpackage build. It seems like there have been more and more issues with people not getting it to run with their Java version. The jpackage build bundles it’s own jre, so this shouldn’t be a problem anymore.

Edit: I have just seen in discord that this is indeed planned :)

[nightm4re94]

Hi again @weisJ, we are currently trying to get a local clone of the engine imported as a Gradle dependency in a project.
Usually, we had used the following gradle configuration to make this work:

in build.gradle:

dependencies {
    implementation project(':litiengine')
}

in settings.gradle:

include ":litiengine"
project(":litiengine").projectDir = file("../litiengine")

As we have just found out, this setup is no longer working for our existing projects. What would the correct configuration be to use a local copy of the engine?

[weisJ]

Assuming the following project structure:

project/settings.gradle
litiengine/setting.gradle.kts

Then in project/settings.gradle:

includeBuild "../litiengine"

You'll be able to declare litiengine as a dependency as usual (i.e. as if you were consuming it from maven). Gradle will automatically replace any dependency with the version provided by includeBuild if it finds a matching module.
At first this will fail with the error message that two modules satisfy the requested dependency. Simply add the following line to
litiengine/setting.gradle.kts:

rootProject.name = "litiengine-root"

It will disambiguate the module names. (Its safe to permanently commit this change as it only affects the name of the root project which isn't published anyway)

[nightm4re94]

Thanks for clarifying!