Fix .java-version, add plugins for successful build

[drtechie]

📋 Description

JIRA ID: NA

Please provide a summary of the change and the motivation behind it. Include relevant context and details.

• Updated .java-version
• Added plugins for building

---

✅ Type of Change

• 🐞 Bug fix (non-breaking change which resolves an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 🔥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 🛠 Refactor (change that is neither a fix nor a new feature)
• ⚙️ Config change (configuration file or build script updates)
• 📚 Documentation (updates to docs or readme)
• 🧪 Tests (adding new or updating existing tests)
• 🎨 UI/UX (changes that affect the user interface)
• 🚀 Performance (improves performance)
• 🧹 Chore (miscellaneous changes that don't modify src or test files)

Summary by CodeRabbit

• Chores
  • Upgraded the Java platform to version 17.0, ensuring enhanced performance and security.
  • Optimized build configurations for improved annotation processing during compilation.
• New Features
  • Enhanced JWT user ID validation filter to allow requests for API documentation to bypass validation, streamlining access to resources.

[coderabbitai]

Walkthrough

This pull request updates the Java version configuration and build setup. The .java-version file now specifies Java 17.0 instead of 1.8, and the pom.xml file has been modified to update the org.projectlombok.version from 1.16.18 to 1.18.36 and the maven-compiler-plugin version to 3.14.0, adding annotation processor paths for Lombok and MapStruct. Additionally, the JwtUserIdValidationFilter.java file has been updated to allow requests to /swagger-ui and /v3/api-docs to bypass JWT validation. No changes were made to exported or public entity declarations.

Changes

Files	Change Summary
.java-version	Updated the Java version from 1.8 to 17.0.
pom.xml	Updated org.projectlombok.version from 1.16.18 to 1.18.36 and modified maven-compiler-plugin to version 3.14.0, adding annotationProcessorPaths for Lombok and MapStruct.
src/main/java/com/iemr/common/utils/JwtUserIdValidationFilter.java	Added conditions to skip JWT validation for requests starting with /swagger-ui and /v3/api-docs.

Poem

In the field of code, I softly tread,
Java 17 leads the way ahead.
Pom.xml sings a new bright tune,
With processors set, it’s over the moon!
Hop along, dear coder, with CodeRabbit’s cheer,
A leap of joy in every line we engineer!
🥕🐰

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 920de5c and 31b65e3.

📒 Files selected for processing (1)

• pom.xml (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• pom.xml

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: Build
• GitHub Check: Analyze (java)
• GitHub Check: style-check / checkstyle
• GitHub Check: Package-test

---

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

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

.java-version (1)

1-2: Ensure .java-version contains only the intended Java version.
The file now sets the Java version to “17.0”, which aligns with the updated configuration. However, the extra line displaying “2” appears unexpected. Please verify if this additional content is intentional or should be removed.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5ccc278 and d444dfc.

📒 Files selected for processing (2)

• .java-version (1 hunks)
• pom.xml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Analyze (java)
• GitHub Check: Build
• GitHub Check: Package-test

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[ravishanigarapu]

looks fine to me