judgeval instrumentation, package structure, add getters on base tracer

[abhishekg999]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @abhishekg999, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly reorganizes the project by implementing a multi-module Maven structure. This change improves modularity, clarifies dependency management, and streamlines build processes. It also introduces a new module for OpenAI instrumentation, complete with an example, and updates the build automation to support this new structure more effectively.

Highlights

• Project Structure Refactoring: The project has been refactored into a multi-module Maven project, introducing dedicated modules for the core judgeval-java SDK, OpenAI instrumentation, and examples.
• Build System Enhancements: The Makefile has been updated with more granular and modular commands for formatting, installing, and checking the status of individual modules, and the run command now supports dynamic example execution.
• OpenAI Instrumentation: A new module judgeval-instrumentation-openai has been added to provide OpenTelemetry instrumentation for OpenAI API calls, along with a SimpleChat example demonstrating its usage.
• Dependency Management: Dependencies are now managed at the module level, with the root pom.xml serving as a parent POM and submodules defining their specific dependencies and build configurations.
• Code Generation Updates: The client generation script (generate_client.py) has been updated to correctly place generated models and API clients within the new judgeval-java module structure.

Ignored Files

• Ignored by pattern: .github/workflows/** (3)
  • .github/workflows/publish-instrumentation-openai.yml
  • .github/workflows/publish-judgeval-java.yml
  • .github/workflows/test-install.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[delve-auditor]

✅ No security or compliance issues detected. Reviewed everything up to 673b86e.

Security Overview

• 🔎 Scanned files: 66 changed file(s)

Detected Code Changes

Change Type	Relevant files
Refactor	► .cursor/rules     Rename from .cursorrules
Enhancement	► .github/workflows/publish-instrumentation-openai.yml     Add workflow to publish judgeval-instrumentation-openai ► .github/workflows/publish-judgeval-java.yml     Add workflow to publish judgeval-java ► .github/workflows/test-instrumentation-openai.yml     Add workflow to test judgeval-instrumentation-openai
Refactor	► .github/workflows/test-judgeval-java.yml     Rename from test-install.yml   &

Reply to this PR with @delve-ai followed by a description of what change you want and we'll auto-submit a change to this PR to implement it.

[gemini-code-assist]

Code Review

This pull request refactors the project into a multi-module structure (judgeval-java, instrumentation, examples), adds instrumentation for OpenAI, and updates the build system (Makefile, pom.xml) accordingly. The changes are extensive and generally well-structured. My review focuses on a few key areas: dependency management consistency, build configuration correctness, and best practices in the new example code. I've identified a broken Javadoc link, inconsistent dependency versions that could cause runtime issues, a missing plugin configuration that will break parts of the build, and a couple of areas for improvement in the example code and Makefile for better robustness.

[abhishekg999]

@gemini review

[abhishekg999]

@propel review

[adivate2021]

lgtm