Consider releasing a new major Ares Version #54
Labels
code quality
The quality of the source code needs to be improved [no change of functionality]
enhancement
New feature or request
help wanted
Extra attention is needed
question
Further information is requested
security
Related to security problems
Milestone
Comments
MaisiKoleni
added
code quality
MaisiKoleni
changed the title
|
A new Security Manager would be a bad idea, considering #113. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Consider releasing a new major Ares version 2.0.0 that introduces some breaking changes:
Possibly, a better solution is to merge both Hidden/Public annotations into one, which both support JUnit Jupiter and jqwik because one ignores the other's extensions.
Originally posted by @MaisiKoleni in Consideration: split AJTS into seperate jqwik part #17 (comment)
Those would be on the
api-level thenExpose the ArtemisSecurityManager methods via TestUtils #53 Renaming
TestUtilsintoAresMake Ares a Java 9+ Module #10 maybe as well, and not export some packages (e.g. security).
New Security Manager #11 Might also be easier.
Consistent naming, and choosing alternatives to black-/whitelist
The text was updated successfully, but these errors were encountered: