Remove Java's Security Manager deprecation message from Checker-Outputs. #19
Conversation
add some documentation information into java.policy and junit.policy see KITPraktomatTeam/Praktomat#350 see KITPraktomatTeam/Praktomat#307 closes KITPraktomatTeam/Praktomat#307
just to fix a merge conflict
…ation-security-manager Conflicts resoved for: README.md
There was a problem hiding this comment.
I wonder if we should actually introduce these workarounds. The security manager is already deprecated and will be removed at some point in the future. We need to remove it anyway, why not now? When running with Docker, the environment is encapsulated anyway. When using a local "tester" account, the operating system can restrict the access for reading/writing files. Spontaneously, I don't see another restriction that the JVM needs to have.
remove links which Markdown doesn't render
Comment out an example configuration block
comment out an example configuration block
fix a typo
No, I didn't solve that problem. However, I believe there's no such restriction for the other (non-Java) checkers, right? They suffer from the same problem. But practically, printing out test cases by exploiting the Praktomat in such a way would probably take more time than solving the actual task. At least, this is probably going to apply in most cases. So there's the question of how realistic this scenario is. Nevertheless, I'll merge this. When the Security Manager is finally removed, we'll just remove those workarounds again, and we'll see what is necessary then. |
close KITPraktomatTeam/Praktomat#307