The current testdata implementation is to write the testdata directory to the built jar if the ENVIRONMENT system veriable isn't production.
This isn't the most ideal way to do it as:
You cannot include anything other than data json.
There has to be a system variable set anywhere that the jar to be built for production.
We aren't using gradle's functionality for cases like this.
This PR moves the testdata directory's contents into src/test/resources/data, it additionally modifies the run configurations made by Loom in order to include the valid files within the src/test directory to only be used inside the developer run environment.
You are able to include assets (such as resource bars), as well as classes too (in the src/test/java directory)
The current testdata implementation is to write the
testdatadirectory to the built jar if the ENVIRONMENT system veriable isn'tproduction.This isn't the most ideal way to do it as:
This PR moves the
testdatadirectory's contents intosrc/test/resources/data, it additionally modifies the run configurations made by Loom in order to include the valid files within thesrc/testdirectory to only be used inside the developer run environment. You are able to include assets (such as resource bars), as well as classes too (in thesrc/test/javadirectory)