- Add Increment:
A-MoreOOP - Add Increments as PRs:
Level-8,Level-9,A-JavaDoc - Set up a product website
- Submit the final version Fri, Mar 6th 2359
1 Add Increment: A-MoreOOP
- As before, commit, tag, and push, after each increment.
2 Add Increments as PRs: Level-8, Level-9, A-JavaDoc
3 Set up a product website
- Add a brief User Guide (UG)
4 Submit the final version Fri, Mar 6th 2359
- Double-check to confirm your iP meets the criteria for full marks, as given in the panel below.
Create a new jar file
- Create the JAR file in one of these ways:
- If you have added a GUI or using third-party libraries: use Gradle.
- Else: you can use IntelliJ.
- The JAR file should be cross-platform and should work in a computer that has Java 17. To avoid version compatibility issues, we strongly recommend the following approach:
- Open a terminal window, and navigate to the root of your project folder.
- Run the
java -versioncommand to confirm the terminal is using Java 17. - Run the
./gradlew clean shadowJarcommand to create the JAR file.
- Create the JAR file in one of these ways:
Do the following smoke tests to ensure the jar file works (reason: a similar flow will be used when grading your iP).
- Copy the jar file to an empty folder and test it from there. This should surface issues with hard-coded file paths.
When running the jar file for smoke testing, instead of double-clicking the jar file, do the following: open a terminal -> navigate to the jar location -> run thejava -jar "JAR_FILE_NAME"command. - Pass the jar file to team members and ask them to do a test drive. Assuming some of your team members' OS differ from yours, this should verify if the app is cross-platform.
If you don't have ready access to a specific OS, you can ask others' help to smoke-test it by posting a smoke-testing request in the forum -- some of them will even appreciate the opportunity to help a classmate.
Note that concepts you encounter while doing course project tasks (e.g., smoke testing) are in the scope of the final exam.
- Copy the jar file to an empty folder and test it from there. This should surface issues with hard-coded file paths.
Create a new release on GitHub (e.g.,
v0.2) and upload the JAR file.- Recommended to refrain from uploading multiple JAR files as this can cause extra work for the evaluators.