build: upgrade lombok to 1.18.34

[javier-godoy]

Summary by CodeRabbit

• Chores
  • Updated the lombok dependency to a newer version for potential bug fixes and improvements.
  • Added new repositories for accessing Flowing Code artifacts while retaining existing Vaadin repositories.

[coderabbitai]

Walkthrough

The changes in this pull request primarily involve updates to the pom.xml file, specifically focusing on dependency version updates and the addition of new repositories. The lombok dependency version has been upgraded from 1.18.28 to 1.18.34. Additionally, new repositories for Flowing Code and existing repositories for Vaadin have been included to enhance artifact accessibility. The overall project structure and build configurations remain unchanged.

Changes

File	Change Summary
pom.xml	Updated lombok dependency version from 1.18.28 to 1.18.34. Added new repositories for Flowing Code (flowing-releases, flowing-snapshots) and retained existing Vaadin repositories.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between d7a4fcc and 8b911f9.

📒 Files selected for processing (1)

• pom.xml (1 hunks)

🔇 Additional comments (2)

pom.xml (2)

Line range hint 92-101: LGTM: Repository configuration is appropriate.

The addition of Flowing Code repositories (releases and snapshots) is well-structured and aligns with the project's organization. The repository configuration follows Maven best practices with unique IDs and proper URL patterns.

---

140-140: LGTM: Lombok version upgrade looks good.

The upgrade to Lombok 1.18.34 is appropriate as it's the latest stable version. The dependency is correctly configured with 'provided' scope.

Let's verify no other Lombok version references exist in the project:

✅ Verification successful

Lombok version upgrade is consistent across the codebase

The verification confirms that Lombok version 1.18.34 is referenced only once in the project, and there are no lingering references to the old version (1.18.28). This indicates a clean version upgrade.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for any other Lombok version references
rg "1\.18\.(28|34)" --type xml

Length of output: 70

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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