Open olivercheok20 opened 5 years ago
Hi there, our team's decision is to reject this bug. There are a few reasons why this is so:
This is a very system-specific issue that most likely only happens on OSX for certain Mac users (do correct me if I'm wrong about the OS, but even with that, my point still stands). There are many Windows and Mac users that do not suffer from this issue. My team is comprised of 2 Macs and 3 Windows users. All of us can run it by double-clicking. We aren't penalized for system-specific issues for the PE, unless it is something grossly egregrious (eg. 99% of Windows users can't run it). I would advise that you try to diagnose this in the context of your system settings/ Java environment settings, or post more information here so we can help you with it. It is not feasible for us to list out every single alternative to every single system-specific issue in the UG.
More importantly, it was stated in the module that running from the terminal is perfectly fine and not penalizable. I believe you are aware of this, as I am when I first encountered this issue in Duke. I believe special instructions were even released to the entire module as well regarding this issue, so this wouldn't have been a problem even if it wasn't explicitly stated in the documentation.
Most importantly of all, the behaviour is inherited from AB3, which makes it an un-penalizable issue that we shouldn't be faulted on for not defending using our documentation. Our application MAMS has all the same environment and import dependencies as AB3. It is likely that if you cannot run our application using the double-click method, you most likely also cannot run AB3 through the double-click method as well. The original AB3 also does not mention anything about the java -jar
method as well. Furthermore, if you have been following along in the forums, it is also an unresolved issue. Just a reminder on bugs inherited from AB3:
We are hence rejecting this as a bug due to all the reasons above.
To emphasize again, it is not feasible for us to list out every single alternative to every single system-specific issue in the UG. If you notice, most open-source software usually relegate this to the issues section of their repo, or to a troubleshooting section (which we are not required to have in CS2103).
It may be that certain users of a famous unnamed brand of laptops with some specific system settings can only start their application by hammering on a precise corner of their screen, then pressing a unique 5-key combination of characters corresponding to their astrological zodiac signs while accessing their machines through ssh, but it would be too verbose for us to cover all these edge cases in the UG, which is meant to be a short and succint guide for the general user to run the app.
I hope you understand. To reiterate, we are rejecting this because it is both system-specific and inherited from AB3. Let us know if you have any futher issues. Nevertheless, thank you for your bug report!
Team chose [response.Rejected
]
Reason for disagreement: [replace this with your reason]
The User Guide specifies that to open the application, the user should double-click the jar file. However, this did not work for my system. Perhaps the User Guide can be updated to suggest opening the application from the Command Line (i.e. using
java -jar
).