nus-pe-script
commented
1 year ago Team's Response
We were unable to reproduce this bug. However, this seems like an issue in your computer settings, from what we have seen, potentially because you need administrative rights to open the file in your terminal directly, or maybe you opened it in OneDrive and there were some security issues. Nonetheless, we could not account for all scenarios in our UserGuide apart from the direct way of accessing jar file.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: If you were unable to reproduce this bug, it should be labelled as response.CannotReproduce. Besides, the UG should have mentioned that the command is as such only assuming that the user saved the jar file as climods.jar. As the filename in PE was different, I was unable to run the file using the command given in the UG. I would like to change this to a Documentation Bug as this assumption was missing in the UG and led to confusion as to how to open the file using command terminal. The assumption to be stated in the UG is important as different filenames can lead to different commands to run the JAR file and the command stated in your UG only works if the filename is saved as climods. The user should be told to key in the command with the respective filename of the JAR file instead of just using "climods", which may not be the case always.
After trying to open the application in various empty folders, I was still unable to open the jar file using the jar command and I could only double click to open it.
This also goes against the user guide as it mentions that using the java -jar climods.jar command works.
This can be a bug of higher severity, "Medium", if the user is unable to open the application using the command.