Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Refactor] package naming scheme #328

Open
ferpasri opened this issue Feb 7, 2023 · 0 comments
Open

[Refactor] package naming scheme #328

ferpasri opened this issue Feb 7, 2023 · 0 comments

Comments

@ferpasri
Copy link
Member

ferpasri commented Feb 7, 2023

  • The historical naming convention "monkey.alayer" does not make sense anymore.
    Refactor package naming from "org.testar.monkey.alayer" to "org.testar"

  • Also, rename historical "fruit" naming:

  1. FruitException to TestarException.
  2. public static File createTempDir() {
    return createTempDir("org.fruit.", Long.toString(System.nanoTime()));
    }
  • "org.testar.action.priorization" to "org.testar.actionselection" because extra layer makes no sense

For example, PrioritizeNewActionsSelector should go to this new org.testar.actionselection

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants