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

Review naming and packaging in ...testutil... modules and corresponding published artifacts #1535

Open
armiol opened this issue Sep 7, 2023 · 0 comments
Milestone

Comments

@armiol
Copy link
Contributor

armiol commented Sep 7, 2023

Right now there is a discrepancy between testutil modules in core-java and those is time, web, and (now) logging.

Their root package names are different by their composition idea. Some of them are io.spine.testing.<foobar>, while others are io.spine.<foobar>.testing.

Also, all of the artifacts names are built by <group-ID>:spine-testutil-<module-name> pattern. It is somewhat weird given that there is no testutil nowhere near in the package name.

A good time to revise these things is 2.0 release.

To do in scope of this issue:

  • Decide on consistent naming of packages across testutil modules.
  • Decide whether we want to name the published artifact somewhat differently. E.g.
    • Switch to testing instead of testutil (and rename modules as well).
    • Swap the module name and testutil: have <group-ID>:spine-<module-name>-testing or <group-ID>:spine-<module-name>-testutil.
@armiol armiol added this to v2.0 Sep 7, 2023
@armiol armiol added this to the M1 milestone Sep 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant