chore: configure dependency propagation

[cuioss-oliver]

Summary

• Add consumers and dependency-propagation config to project.yml
• On release, propagates version to cuioss-parent-pom (property version.cui.java.tools) and nifi-extensions

Test plan

• CI build passes (config-only change to project.yml)

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello @cuioss-oliver, 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 introduces configuration for automated dependency propagation within the project's CI/CD pipeline. By defining consumers and propagation rules in .github/project.yml, it ensures that when the cui-java-tools artifact is released, its version is automatically updated in specified dependent projects. This change aims to streamline the release process and maintain version consistency across interconnected repositories, reducing manual intervention and potential errors.

Highlights

• Dependency Propagation Configuration: Added new consumers and dependency-propagation sections to the .github/project.yml file.
• Version Synchronization: Configured the cui-java-tools project to automatically propagate its version to cuioss-parent-pom and nifi-extensions upon release, specifically updating the version.cui.java.tools property in these consumer projects.

Changelog

• .github/project.yml
  • Added consumers configuration to specify projects that depend on cui-java-tools and the properties to update.
  • Added dependency-propagation configuration to define the group-id, artifact-id, and scope for the cui-java-tools dependency.

Activity

• The pull request was authored by cuioss-oliver.
• The change is a configuration-only update to project.yml, with the test plan indicating that CI build passes.
• The pull request description states it was generated with Claude Code.

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. ↩

[gemini-code-assist]

Code Review

This pull request adds configuration for dependency propagation in .github/project.yml. The configuration for consumers appears correct. However, I've identified a potential issue in the dependency-propagation section regarding the scope value, which is not a standard Maven scope. I've left a specific comment with a suggestion to address this potential issue.

[gemini-code-assist]

The value dependency for scope is not a standard Maven dependency scope. Valid scopes are compile, provided, runtime, test, system, and import. Using a non-standard scope might cause issues with the dependency propagation tooling if it expects a valid Maven scope. If the intention is for this to be a compile-time dependency for consumers, compile would be the correct value.

  scope: compile

[cuioss-oliver]

The scope: dependency field here is not a Maven dependency scope. It's a custom configuration value for the cuioss dependency-propagation automation (see cuioss-organization v0.4.0). It distinguishes between scope: parent (update parent version in consumer POM) and scope: dependency (update a version property in consumer POM). Working as intended.