tP:
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).
Learn how to use Gradle
run: runs the project codeclean: deletes files generates from previous runscheck: runs the testscheckstyleMain: checks your Java functional code for compliance with some (but not all) rules specified in the coding standard, using a tool called checkstylecheckstyleTest: similar to above, but checks the test code insteadshadowJar: creates a JAR file for your projectcheck 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)Start implementing v1.0, by adding code in small steps, while working in parallel, aiming to produce a VERY simple working version after one week, and a bit more functional version at the end of iteration (i.e., after two weeks).
See the panel below for our recommendations on the project workflow.
We recommend that each person adds some JUnit tests to test their tP code.
Some examples from AddressBook-Level2:
seedu.addressbook.common.Utils.javaseedu.addressbook.common.UtilsTest.javaseedu.addressbook.parser.Parser.javaseedu.addressbook.parser.ParserTest.javaparse_emptyInput_returnsIncorrect(). Cross-check the coding standard to confirm if this naming convention is allowed.seedu.addressbook.data.AddressBook.javaseedu.addressbook.data.AddressBookTest.java