Skip to content

Conversation

@kumar-zlai
Copy link
Contributor

@kumar-zlai kumar-zlai commented Jan 17, 2025

Summary

Migrated hub module to Bazel from sbt.

Checklist

  • Added Unit Tests
  • Covered by existing CI
  • Integration tested
  • Documentation update

Summary by CodeRabbit

Release Notes

  • Dependency Management

    • Added new dependency lists for Flink, Vert.x, and Circe libraries
    • Consolidated and standardized dependency management across multiple projects
    • Introduced new Maven artifact dependencies for Circe and Vert.x
  • Build Configuration

    • Refactored dependency references in multiple BUILD.bazel files
    • Updated build rules to use centralized dependency variables
    • Simplified library and test suite configurations
  • Library Updates

    • Added Scala libraries for hub project
    • Updated service commons library dependencies

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 17, 2025

Walkthrough

This pull request introduces a comprehensive refactoring of dependency management across multiple Bazel build files. The changes focus on centralizing library dependencies, adding new Scala and Maven artifacts, and standardizing how dependencies are defined and referenced. The modifications span several projects, including hub, flink, service, and service_commons, with a consistent approach to dependency management.

Changes

File Change Summary
hub/BUILD.bazel Added three new Scala library definitions: lib, test-lib, and test with comprehensive dependencies
tools/build_rules/dependencies/maven_repository.bzl Added Circe dependencies and a duplicate Vertx unit dependency
flink/BUILD.bazel Replaced flink_deps and flink_test_deps with _FLINK_DEPS and _FLINK_TEST_DEPS
service/BUILD.bazel Replaced vertx_deps and vertx_test_deps with _VERTX_DEPS and _VERTX_TEST_DEPS
service_commons/BUILD.bazel Updated library dependencies to use consolidated _VERTX_DEPS and _VERTX_TEST_DEPS
tools/build_rules/prelude_bazel Added new dependency lists for Flink, Vertx, and Circe

Possibly related PRs

Suggested reviewers

  • tchow-zlai
  • nikhil-zlai
  • piyush-zlai

Poem

Bazel's dance of dependencies bright,
Libraries linked with architectural might,
Circe and Vertx in harmony sing,
Refactored code takes its elegant wing! 🚀📦

Warning

Review ran into problems

🔥 Problems

GitHub Actions: Resource not accessible by integration - https://docs.github.com/rest/actions/workflow-runs#list-workflow-runs-for-a-repository.

Please grant the required permissions to the CodeRabbit GitHub App under the organization or repository settings.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🧹 Nitpick comments (8)
tools/build_rules/dependencies/maven_repository.bzl (1)

86-94: Standardize Google Cloud dependency versions.

Different versions of Google Cloud libraries may cause compatibility issues.

Consider aligning versions:

  • google-cloud-bigquery: 2.42.0
  • google-cloud-bigtable: 2.41.0
  • google-cloud-pubsub: 1.131.0
  • google-cloud-dataproc: 4.52.0
flink/BUILD.bazel (1)

64-101: Reduce dependency duplication.

Consider extracting common test dependencies into a separate .bzl file to avoid duplication between test-lib and test targets.

hub/BUILD.bazel (1)

57-71: Clarify testing strategy.

Consider standardizing on either JUnit or ScalaTest to maintain consistency.

cloud_gcp/BUILD.bazel (2)

17-22: Optimize cloud dependencies.

Consider splitting cloud services into separate targets to reduce binary size for services that don't need all GCP features.


85-99: Review reflection usage.

Large number of --add-opens flags suggests heavy reflection. Consider reducing reflection usage for better maintainability.

service/src/test/java/ai/chronon/service/handlers/FetchHandlerTest.java (3)

78-82: Unnecessary HashMap wrapper around Map.of()

The new HashMap<>() wrapper is redundant since Map.of() already creates an immutable map.

-        Map<String, Object> featureMap = new HashMap<>(Map.of(
+        Map<String, Object> featureMap = Map.of(
             "feature_1", 12,
             "feature_2", 23.3,
             "feature_3", "USD"
-        ));
+        );

197-200: Unnecessary ArrayList wrapper around List.of()

The new ArrayList<>() wrapper is redundant since List.of() already creates an immutable list.

-        List<JavaResponse> mockResponseList = new ArrayList<>(List.of(
+        List<JavaResponse> mockResponseList = List.of(
             mockResponse1,
             mockResponse2
-        ));
+        );

285-285: Remove duplicate semicolon

There's a duplicate semicolon at the end of async.complete();;.

-            async.complete();;
+            async.complete();
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between 847bb3a and 5d4ad00.

📒 Files selected for processing (9)
  • WORKSPACE (1 hunks)
  • cloud_gcp/BUILD.bazel (1 hunks)
  • flink/BUILD.bazel (1 hunks)
  • hub/BUILD.bazel (1 hunks)
  • service/BUILD.bazel (1 hunks)
  • service/src/test/java/ai/chronon/service/handlers/FetchHandlerTest.java (5 hunks)
  • spark/BUILD.bazel (2 hunks)
  • tools/build_rules/dependencies/maven_repository.bzl (2 hunks)
  • tools/build_rules/dependencies/spark_repository.bzl (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: table_utils_delta_format_spark_tests
  • GitHub Check: mutation_spark_tests
  • GitHub Check: join_spark_tests
  • GitHub Check: fetcher_spark_tests
  • GitHub Check: no_spark_scala_tests
  • GitHub Check: other_spark_tests
🔇 Additional comments (7)
WORKSPACE (1)

35-37: Verify compatibility with downgraded rules_jvm_external.

Downgrading from 6.6 to 4.5 might impact newer dependencies.

✅ Verification successful

Downgrade to rules_jvm_external 4.5 appears safe.

The codebase uses standard Java/Scala dependencies without complex version constraints or custom configurations. Version 4.5 is stable and supports all observed usage patterns.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for any dependency resolution errors in Bazel build
find . -name "*.bazel" -o -name "BUILD" | while read -r file; do
  echo "Checking dependencies in $file"
  grep -A 5 "maven_artifact" "$file"
done

Length of output: 24033


Script:

#!/bin/bash
# Check for maven dependency version constraints
fd "maven_install.json|maven.lock|dependencies.yaml|pom.xml" --type f --exec cat {}

Length of output: 87

tools/build_rules/dependencies/maven_repository.bzl (1)

63-69: LGTM! Flink dependencies are consistently versioned.

All Flink dependencies use version 1.17.0.

flink/BUILD.bazel (1)

11-12: Verify Flink dependency versions.

Ensure all Flink dependencies use consistent versions to prevent runtime conflicts.

✅ Verification successful

All Flink dependencies use consistent version 1.17.0

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for mixed Flink versions
rg "org.apache.flink:[^:]+:[^:]+" | sort | uniq -c

Length of output: 845


Script:

#!/bin/bash
# Check scala artifacts
rg "scala_artifact.*org.apache.flink:" -A 1

Length of output: 786

hub/BUILD.bazel (1)

11-15: Verify Vert.x dependency versions.

Check compatibility between Vert.x modules to prevent runtime issues.

✅ Verification successful

All Vert.x dependencies are aligned at version 4.5.10

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for mixed Vert.x versions
rg "io.vertx:[^:]+:[^:]+" | sort | uniq -c

Length of output: 753

spark/BUILD.bazel (1)

24-25: Verify logging configuration.

Adding log4j dependencies without configuration file might cause logging issues.

✅ Verification successful

Logging is properly configured programmatically

The log4j configuration is handled in SparkSessionBuilder using ConfigurationBuilder, which is a better approach than static configuration files.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for log4j configuration files
fd -g "*log4j*.properties" -g "*log4j*.xml"

Length of output: 144


Script:

#!/bin/bash
# Find log4j config files
fd -e properties -e xml -e yml -e yaml -e json | grep -i "log4j"

# Check for programmatic configuration
rg -i "LogManager|ConfigurationBuilder|XmlConfiguration|PropertiesConfiguration" -A 2

Length of output: 900

service/src/test/java/ai/chronon/service/handlers/FetchHandlerTest.java (2)

180-184: Same redundant HashMap wrapper in multiple maps

Similar to the previous comment, remove redundant HashMap wrappers.

Also applies to: 186-190


222-225: Same redundant ArrayList wrapper in multiple lists

Similar to the previous comment, remove redundant ArrayList wrappers.

Also applies to: 256-259, 280-283

Comment on lines 16 to 17

"org.apache.curator:apache-curator:5.5.0",
Copy link
Contributor

Choose a reason for hiding this comment

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

💡 Codebase verification

Remove unused Curator dependency

The Apache Curator dependency appears unnecessary as:

  • No direct Curator API usage in codebase
  • Existing ZooKeeper usage is managed by Kafka
🔗 Analysis chain

LGTM! Verify ZooKeeper compatibility.

Apache Curator 5.5.0 is compatible with Spark 3.5.1.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if any Spark configurations use ZooKeeper
rg -l "zookeeper" --type scala --type java --type properties

Length of output: 95


Script:

#!/bin/bash
# Find ZooKeeper/Curator usage
rg -l -i "zookeeper|curator" 

# Search for Curator API patterns
ast-grep --pattern 'new CuratorFramework$_'
ast-grep --pattern 'CuratorFrameworkFactory.$_'

Length of output: 197


Script:

#!/bin/bash
# Check docker-compose ZooKeeper config
cat docker-compose.yml

Length of output: 2038

Comment on lines 26 to 45
java_library(
name = "test-lib",
srcs = glob(["src/test/**/*.java"]),
visibility = ["//visibility:public"],
deps = [
":lib",
"//online:lib",
"//service_commons:lib",
# Libraries
maven_artifact("io.vertx:vertx-core"),
maven_artifact("io.vertx:vertx-web"),
maven_artifact("io.vertx:vertx-web-client"),
# Testing
maven_artifact("io.vertx:vertx-junit5"),
maven_artifact("io.vertx:vertx-unit"),
maven_artifact("org.mockito:mockito-core"),
maven_artifact("org.junit.jupiter:junit-jupiter-api"),
maven_artifact("junit:junit"),
],
)
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Consolidate duplicate test dependencies.

Move common dependencies to test-lib and reference only test-lib in test target.

 java_test_suite(
     name = "test",
     srcs = glob(["src/test/**/*.java"]),
     visibility = ["//visibility:public"],
     runner = "junit5",
     deps = [
         ":lib",
         ":test-lib",
-        "//online:lib",
-        # Libraries
-        maven_artifact("io.vertx:vertx-core"),
-        maven_artifact("io.vertx:vertx-web"),
-        maven_artifact("io.vertx:vertx-web-client"),
-        # Testing
-        maven_artifact("io.vertx:vertx-junit5"),
-        maven_artifact("io.vertx:vertx-unit"),
-        maven_artifact("org.mockito:mockito-core"),
-        maven_artifact("org.junit.jupiter:junit-jupiter-api"),
-        maven_artifact("junit:junit"),
         maven_artifact("org.junit.platform:junit-platform-launcher"),
         maven_artifact("org.junit.platform:junit-platform-reporting"),
     ],
 )

Also applies to: 47-69

WORKSPACE Outdated
strip_prefix = "rules_jvm_external-6.6",
sha256 = "3afe5195069bd379373528899c03a3072f568d33bd96fe037bd43b1f590535e7",
url = "https://github.com/bazel-contrib/rules_jvm_external/releases/download/6.6/rules_jvm_external-6.6.tar.gz"
strip_prefix = "rules_jvm_external-4.5",
Copy link
Contributor

Choose a reason for hiding this comment

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

why downgrade?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Not needed. Removed after rebase.

"//spark:lib",
"//tools/build_rules/spark:spark-exec",
# Libraries
scala_artifact("org.scala-lang.modules:scala-java8-compat"),
Copy link
Contributor

Choose a reason for hiding this comment

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

factor out common deps and re-use

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

Copy link
Contributor

@nikhil-zlai nikhil-zlai left a comment

Choose a reason for hiding this comment

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

Factor out common deps and re-use them across targets - atleast within the same build file.

"//aggregator:lib",
"//tools/build_rules/spark:spark-exec",
# Libraries
scala_artifact("org.apache.flink:flink-streaming-scala"),
Copy link
Contributor

Choose a reason for hiding this comment

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

same as above

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

Copy link
Contributor

@piyush-zlai piyush-zlai left a comment

Choose a reason for hiding this comment

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

Couple of minor nits

"//online:lib",
"//spark:lib",
"//tools/build_rules/spark:spark-exec",
# Libraries
Copy link
Contributor

Choose a reason for hiding this comment

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

like Nikhil mentioned earlier, probably worth creating a scala lib with some deps and re-using them..

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

put("feature_2", 23.3);
put("feature_3", "USD");
}};
Map<String, Object> featureMap = new HashMap<>(Map.of(
Copy link
Contributor

Choose a reason for hiding this comment

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

nit - the HashMap(Map.of) might be redundant. You can just do the Map.of

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

put("feature_2", 23.3);
put("feature_3", "USD");
}};
Map<String, Object> featureMap1 = new HashMap<>(Map.of(
Copy link
Contributor

Choose a reason for hiding this comment

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

here too

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between 5d4ad00 and 90cc291.

📒 Files selected for processing (1)
  • tools/build_rules/dependencies/maven_repository.bzl (1 hunks)
🔇 Additional comments (1)
tools/build_rules/dependencies/maven_repository.bzl (1)

95-98: LGTM!

Circe dependencies are properly versioned and include all necessary components.

"io.vertx:vertx-micrometer-metrics:4.5.10",
"io.vertx:vertx-junit5:4.5.10",
"io.vertx:vertx-unit:4.5.10",
"io.vertx:vertx-unit:4.5.10",
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Remove duplicate dependency.

io.vertx:vertx-unit:4.5.10 is already declared on line 92.

-        "io.vertx:vertx-unit:4.5.10",

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
tools/build_rules/prelude_bazel (1)

43-53: Optimize test dependencies to avoid duplication

Consider creating a base dependency list that's shared between main and test configurations.

+_FLINK_BASE_DEPS = [
+    scala_artifact("org.apache.flink:flink-streaming-scala"),
+    scala_artifact("org.apache.flink:flink-scala"),
+    maven_artifact("org.apache.flink:flink-streaming-java"),
+    maven_artifact("org.apache.flink:flink-core"),
+]

 _FLINK_DEPS = _FLINK_BASE_DEPS + [
     maven_artifact("org.apache.flink:flink-metrics-dropwizard"),
     maven_artifact("org.apache.flink:flink-metrics-core"),
     maven_artifact("org.apache.flink:flink-clients"),
     maven_artifact("org.apache.flink:flink-yarn"),
 ]

-_FLINK_TEST_DEPS = [
-    # Libraries
-    scala_artifact("org.apache.flink:flink-streaming-scala"),
-    scala_artifact("org.apache.flink:flink-scala"),
-    maven_artifact("org.apache.flink:flink-streaming-java"),
-    maven_artifact("org.apache.flink:flink-core"),
+_FLINK_TEST_DEPS = _FLINK_BASE_DEPS + [
     maven_artifact("org.apache.flink:flink-runtime"),
     # Testing
     maven_artifact("org.apache.flink:flink-test-utils"),
     maven_artifact("org.apache.flink:flink-runtime-tests"),
 ]
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between 90cc291 and b5d2216.

📒 Files selected for processing (5)
  • flink/BUILD.bazel (2 hunks)
  • hub/BUILD.bazel (1 hunks)
  • service/BUILD.bazel (2 hunks)
  • service_commons/BUILD.bazel (2 hunks)
  • tools/build_rules/prelude_bazel (2 hunks)
✅ Files skipped from review due to trivial changes (1)
  • service/BUILD.bazel
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: no_spark_scala_tests
🔇 Additional comments (7)
service_commons/BUILD.bazel (2)

Line range hint 5-15: Clean dependency consolidation using _VERTX_DEPS


18-18: Clean test dependency consolidation using _VERTX_TEST_DEPS

flink/BUILD.bazel (2)

Line range hint 5-15: Clean dependency consolidation using _FLINK_DEPS


Line range hint 18-45: Clean test dependency consolidation using _FLINK_TEST_DEPS

tools/build_rules/prelude_bazel (1)

63-71: Similar optimization needed for Vertx test dependencies

hub/BUILD.bazel (2)

1-24: Clean dependency organization using centralized lists


61-66: Add unit tests as mentioned in PR objectives

PR indicates unit tests haven't been added yet. Please implement tests for the hub module functionality.

@kumar-zlai kumar-zlai merged commit c89f6c0 into main Jan 22, 2025
4 checks passed
@kumar-zlai kumar-zlai deleted the kumarteja/hub-bazel-migration branch January 22, 2025 01:18
kumar-zlai added a commit that referenced this pull request Apr 25, 2025
## Summary
Migrated `hub` module to Bazel from sbt.

## Checklist
- [ ] Added Unit Tests
- [x] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

## Release Notes

- **Dependency Management**
  - Added new dependency lists for Flink, Vert.x, and Circe libraries
- Consolidated and standardized dependency management across multiple
projects
  - Introduced new Maven artifact dependencies for Circe and Vert.x

- **Build Configuration**
  - Refactored dependency references in multiple `BUILD.bazel` files
  - Updated build rules to use centralized dependency variables
  - Simplified library and test suite configurations

- **Library Updates**
  - Added Scala libraries for hub project
  - Updated service commons library dependencies
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: nikhil-zlai <[email protected]>
Co-authored-by: Kumar Teja Chippala <[email protected]>
kumar-zlai added a commit that referenced this pull request Apr 29, 2025
## Summary
Migrated `hub` module to Bazel from sbt.

## Checklist
- [ ] Added Unit Tests
- [x] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

## Release Notes

- **Dependency Management**
  - Added new dependency lists for Flink, Vert.x, and Circe libraries
- Consolidated and standardized dependency management across multiple
projects
  - Introduced new Maven artifact dependencies for Circe and Vert.x

- **Build Configuration**
  - Refactored dependency references in multiple `BUILD.bazel` files
  - Updated build rules to use centralized dependency variables
  - Simplified library and test suite configurations

- **Library Updates**
  - Added Scala libraries for hub project
  - Updated service commons library dependencies
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: nikhil-zlai <[email protected]>
Co-authored-by: Kumar Teja Chippala <[email protected]>
chewy-zlai pushed a commit that referenced this pull request May 15, 2025
## Summary
Migrated `hub` module to Bazel from sbt.

## Checklist
- [ ] Added Unit Tests
- [x] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

## Release Notes

- **Dependency Management**
  - Added new dependency lists for Flink, Vert.x, and Circe libraries
- Consolidated and standardized dependency management across multiple
projects
  - Introduced new Maven artifact dependencies for Circe and Vert.x

- **Build Configuration**
  - Refactored dependency references in multiple `BUILD.bazel` files
  - Updated build rules to use centralized dependency variables
  - Simplified library and test suite configurations

- **Library Updates**
  - Added Scala libraries for hub project
  - Updated service commons library dependencies
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: nikhil-zlai <[email protected]>
Co-authored-by: Kumar Teja Chippala <[email protected]>
chewy-zlai pushed a commit that referenced this pull request May 15, 2025
## Summary
Migrated `hub` module to Bazel from sbt.

## Checklist
- [ ] Added Unit Tests
- [x] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

## Release Notes

- **Dependency Management**
  - Added new dependency lists for Flink, Vert.x, and Circe libraries
- Consolidated and standardized dependency management across multiple
projects
  - Introduced new Maven artifact dependencies for Circe and Vert.x

- **Build Configuration**
  - Refactored dependency references in multiple `BUILD.bazel` files
  - Updated build rules to use centralized dependency variables
  - Simplified library and test suite configurations

- **Library Updates**
  - Added Scala libraries for hub project
  - Updated service commons library dependencies
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: nikhil-zlai <[email protected]>
Co-authored-by: Kumar Teja Chippala <[email protected]>
chewy-zlai pushed a commit that referenced this pull request May 16, 2025
## Summary
Migrated `hub` module to Bazel from sbt.

## Cheour clientslist
- [ ] Added Unit Tests
- [x] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

## Release Notes

- **Dependency Management**
  - Added new dependency lists for Flink, Vert.x, and Circe libraries
- Consolidated and standardized dependency management across multiple
projects
  - Introduced new Maven artifact dependencies for Circe and Vert.x

- **Build Configuration**
  - Refactored dependency references in multiple `BUILD.bazel` files
  - Updated build rules to use centralized dependency variables
  - Simplified library and test suite configurations

- **Library Updates**
  - Added Scala libraries for hub project
  - Updated service commons library dependencies
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: nikhil-zlai <[email protected]>
Co-authored-by: Kumar Teja Chippala <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants