Skip to content

Rename polaris-quarkus-* projects as polaris-* and renaming quarkus folder as runtime #1695

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

Merged
merged 1 commit into from
Jun 17, 2025

Conversation

jbonofre
Copy link
Member

Quarkus is an implementation "detail", the end users should not be "bothered" by this.
I propose here to use "abstract" name in tasks (using direction polaris-* instead of polaris-quarkus-*) and rename quarkus folder as runtime.

If later we want/need to replace the runtime framework, it won't change the structure.

Copy link
Contributor

@dimas-b dimas-b left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This renaming proposal sounds good to me 👍

@flyrain
Copy link
Contributor

flyrain commented May 28, 2025

+1 to renaming. Thanks for doing this. Just a heads-up: sweeping changes like this hit many surfaces, including “getting started” pages and instructions, that CI never sees. We’ve been burned before, PR #1532 broke plenty of things without breaking a single test in CI. So let’s do extra manual verification before we merge.

@jbonofre jbonofre force-pushed the rename-quarkus-to-runtime branch from 6169365 to 8772513 Compare June 10, 2025 15:47
@jbonofre jbonofre requested a review from dimas-b June 10, 2025 15:48
@jbonofre jbonofre force-pushed the rename-quarkus-to-runtime branch from 8772513 to f5db872 Compare June 10, 2025 15:50
dimas-b
dimas-b previously approved these changes Jun 10, 2025
Copy link
Contributor

@dimas-b dimas-b left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This renaming LGTM 👍

@github-project-automation github-project-automation bot moved this from PRs In Progress to Ready to merge in Basic Kanban Board Jun 10, 2025
@jbonofre
Copy link
Member Author

FYI, any change on main means a rebase/conflict on this PR. If we don't have consensus here, let's do it later.

@jbonofre jbonofre dismissed stale reviews from dimas-b and adutra via efd34d5 June 16, 2025 17:09
@jbonofre jbonofre force-pushed the rename-quarkus-to-runtime branch from 515a493 to efd34d5 Compare June 16, 2025 17:09
@jbonofre
Copy link
Member Author

I did the rebase.

@flyrain can you please take a look ?

I would like to merge this if it works for you. Thanks for the review @adutra @dimas-b @snazy !

dimas-b
dimas-b previously approved these changes Jun 16, 2025
@dimas-b
Copy link
Contributor

dimas-b commented Jun 16, 2025

@jbonofre : Python CI failed with Cannot locate tasks that match ':polaris-quarkus-server:assemble' as project 'polaris-quarkus-server' not found in root project 'polaris'.

@flyrain
Copy link
Contributor

flyrain commented Jun 17, 2025

Hi @jbonofre — thanks for driving this. A few tidy-up ideas while we’re here:

  1. Rename polaris-runtime-distributionpolaris-distribution (keeps it aligned with polaris-admin and polaris-server). And we might move it out of directory runtime as it is just a packaging module.
  2. Rename polaris-runtime-test-commonspolaris-runtime-test-common for singular/plural consistency.
  3. Optional follow-up: merge polaris-server into polaris-service to simplify the module layout (not a blocker for this PR).

Thoughts?

@dimas-b
Copy link
Contributor

dimas-b commented Jun 17, 2025

Optional follow-up: merge polaris-server into polaris-service to simplify the module layout (not a blocker for this PR).

I'm strongly -1 on this. I'm pretty sure this is going to complicate the reuse of polaris-service code in downstream projects.

@jbonofre
Copy link
Member Author

@jbonofre : Python CI failed with Cannot locate tasks that match ':polaris-quarkus-server:assemble' as project 'polaris-quarkus-server' not found in root project 'polaris'.

I'm fixing, that's due to rebase.

@jbonofre
Copy link
Member Author

I updated the PR with:

  1. Fix python CI
  2. Rename polaris-runtime-distrtibution to polaris-distribution
  3. Rename polaris-runtime-test-commons to polaris-runtime-test-common

@flyrain @dimas-b mind to do a new pass ? Thanks !

@jbonofre jbonofre requested review from dimas-b and adutra June 17, 2025 05:42
@adutra
Copy link
Contributor

adutra commented Jun 17, 2025

Optional follow-up: merge polaris-server into polaris-service to simplify the module layout (not a blocker for this PR).

I'm strongly -1 on this. I'm pretty sure this is going to complicate the reuse of polaris-service code in downstream projects.

Agreed. However, in a follow-up PR, imho we could merge polaris-service-common into polaris-runtime-service.

@jbonofre
Copy link
Member Author

Optional follow-up: merge polaris-server into polaris-service to simplify the module layout (not a blocker for this PR).

I'm strongly -1 on this. I'm pretty sure this is going to complicate the reuse of polaris-service code in downstream projects.

Agreed. However, in a follow-up PR, imho we could merge polaris-service-common into polaris-runtime-service.

I agree to have a follow-up PR and happy to do that. I think the most important for 1.0 release is about the Maven coordinates and names "visible" to users.

Copy link
Contributor

@flyrain flyrain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks @jbonofre !

@flyrain
Copy link
Contributor

flyrain commented Jun 17, 2025

Minor: we might change the dir test-commons to test-common to be consistent

@jbonofre jbonofre merged commit ab228af into apache:main Jun 17, 2025
9 checks passed
@github-project-automation github-project-automation bot moved this from Ready to merge to Done in Basic Kanban Board Jun 17, 2025
@jbonofre
Copy link
Member Author

@flyrain sorry I missed your comment, let me do another PR about test-commons rename.

@adutra
Copy link
Contributor

adutra commented Jun 19, 2025

Optional follow-up: merge polaris-server into polaris-service to simplify the module layout (not a blocker for this PR).

I'm strongly -1 on this. I'm pretty sure this is going to complicate the reuse of polaris-service code in downstream projects.

Agreed. However, in a follow-up PR, imho we could merge polaris-service-common into polaris-runtime-service.

I agree to have a follow-up PR and happy to do that. I think the most important for 1.0 release is about the Maven coordinates and names "visible" to users.

@jbonofre do you plan to work on this? Otherwise I can look into it.

While it's not so critical, it's still a user-facing change since the polaris-service-common artifact would disappear.

fabio-rizzo-01 pushed a commit to fabio-rizzo-01/polaris that referenced this pull request Jun 20, 2025
# This is the 1st commit message:

 apache#772 fixed integration tests and synched with main

Mypy did a new release 1.16.1 and it cause our CI to fail for about 20 minutes due to missing wheel (upload not completed)
```
 | Unable to find installation candidates for mypy (1.16.1)
    |
    | This is likely not a Poetry issue.
    |
    |   - 14 candidate(s) were identified for the package
    |   - 14 wheel(s) were skipped as your project's environment does not support the identified abi tags
    |
    | Solutions:
    | Make sure the lockfile is up-to-date. You can try one of the following;
    |
    |     1. Regenerate lockfile: poetry lock --no-cache --regenerate
    |     2. Update package     : poetry update --no-cache mypy
    |
    | If neither works, please first check to verify that the mypy has published wheels available from your configured source that are compatible with your environment- ie. operating system, architecture (x86_64, arm64 etc.), python interpreter.
    |

```
This PR temporarily restrict the mypy version to avoid the similar issue.

We may consider bring poetry.lock back to git tracking so we won't automatically update test dependencies all the time

# This is the commit message apache#48:

Remove `.github/CODEOWNERS` (apache#1902)

As per this [dev-ML discussion](https://lists.apache.org/thread/jjr5w3hslk755yvxy8b3z45c7094cxdn)
# This is the commit message apache#49:

Rename quarkus as runtime (apache#1695)

# This is the commit message apache#50:

parent 3185adf
author Mend Renovate <bot@renovateapp.com> 1749165686 +0200
committer Rizzo Cascio, Fabio <fabio.rizzocascio@jpmorgan.com> 1749646499 +0100

# This is a combination of 2 commits.
# This is the 1st commit message:

Mutable objects used for immutable values apache#772: resolved conflicts

# This is the commit message apache#51:

Mutable objects used for immutable values apache#772: fixed integration tests

# This is the commit message apache#52:

parent 3185adf
author Mend Renovate <bot@renovateapp.com> 1749165686 +0200
committer Rizzo Cascio, Fabio <fabio.rizzocascio@jpmorgan.com> 1749646499 +0100

# This is a combination of 2 commits.
# This is the 1st commit message:

Mutable objects used for immutable values apache#772: resolved conflicts

Mutable objects used for immutable values apache#772: added final to base and core fields

Mutable objects used for immutable values apache#772: fixed tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants