tP week 8: mid-v1.0

You may i.e., copy-paste, not clone/forkre-purpose/adopt code from any of the below to be used in your tP, provided you give credit to the source (and do not claim such code as yours).

• The iP code of any of your team members, or of any other person in the module.
• Code from AddressBook-Level2 or any code used in module activities

Learn how to use Gradle

• The tP project template given to you is already configured to use Gradle (a build automation and dependency management tool).
• If you haven't encountered Gradle before, learn more about Gradle from the Gradle tutorial @SE-EDU/guides
• Some useful Gradle tasks you can try (to familiarize yourself with using Gradle):
  • run: runs the project code
  • clean: deletes files generates from previous runs
  • check: runs the tests
  • checkstyleMain: checks your Java functional code for compliance with some (but not all) rules specified in the coding standard, using a tool called checkstyle
  • checkstyleTest: similar to above, but checks the test code instead
  • shadowJar: creates a JAR file for your project
• Note that GitHub Actions too is using Gradle to check the code you push to GitHub. Specifically, it runs the check task and then it uses the shadowJar task to build the JAR file which is then used to do I/O redirection tests (as per the files in your text-ui-text folder)