Fix target platform build dependencies

[PMarinov1994]

The latest version of jdtls requires version 0.23.0 of lsp4j. Changing the a snapshot of jdtls instead of latest will prevent version mismatch in future releases.

• Use jdtls from https://download.eclipse.org/jdtls/milestones/1.40.0/ in target platform
• Use lsp4j from https://download.eclipse.org/lsp4j/updates/releases/0.23.1/ in target platform
• Use lsp4j from https://download.eclipse.org/lsp4j/updates/releases/0.23.1/ in pom.xml

Summary by CodeRabbit

• New Features

  • Updated dependencies for improved performance and stability of the JDT Language Server.

• Bug Fixes

  • Resolved issues related to outdated repository links, ensuring smoother integration and access to the latest features.

• Chores

  • Standard formatting improvements in configuration files.

[coderabbitai]

Walkthrough

The changes involve updates to the pom.xml and target.target files for the JDT Language Server (JDTLS). The pom.xml file's repository URL for lsp4j has been upgraded from version 0.22.0 to 0.23.1. Similarly, the target.target file reflects this version update for lsp4j and changes the repository for org.eclipse.jdt.ls.core from a snapshot to a milestone repository. Additionally, a newline was added at the end of the pom.xml for formatting consistency.

Changes

File(s)	Change Summary
pde/pom.xml	Updated lsp4j repository URL from 0.22.0 to 0.23.1; added newline at end of file.
pde/target.target	Updated lsp4j repository location from 0.22.0 to 0.23.1; changed jdt.ls.core repository from snapshot to milestone.

Poem

In the garden where code does bloom,
Versions rise and old ones zoom.
From 0.22 to 0.23,
A leap for JDT, oh so free!
With a newline added, neat and bright,
Our code hops forward, pure delight! 🐇✨

---

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

pde/target.target (1)

45-45: LGTM: JDTLS repository update is correct with a minor suggestion.

The update to the JDTLS repository URL from a snapshot to a specific milestone version (1.40.0) is correct and aligns with the PR objectives. This change addresses the goal of mitigating potential version conflicts in future releases. The switch from HTTP to HTTPS is also a good security improvement.

Consider adding a comment above this line explaining why we're using this specific version, to help future maintainers understand the rationale behind this choice. For example:

<!-- Using JDTLS 1.40.0 to ensure compatibility with LSP4J 0.23.1 -->
<repository location="https://download.eclipse.org/jdtls/milestones/1.40.0/" />

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 795f866 and eb044c9.

📒 Files selected for processing (2)

• pde/pom.xml (2 hunks)
• pde/target.target (1 hunks)

🧰 Additional context used

🔇 Additional comments (3)

pde/target.target (2)

40-40: LGTM: LSP4J repository update is correct.

The update to LSP4J repository URL from version 0.22.0 to 0.23.1 is correct and aligns with the PR objectives. This change addresses the version mismatch issue and uses HTTPS, which is a good security practice.

---

48-48: LGTM: New line at end of file.

The addition of a new line at the end of the file is a good practice. It follows many coding standards and can help prevent issues with some version control systems and text processing tools.

pde/pom.xml (1)

60-60: LGTM! Verify project compatibility with updated lsp4j version.

The URL update for the lsp4j repository from version 0.22.0 to 0.23.1 aligns with the PR objectives. This change correctly implements the intended version upgrade.

To ensure this change doesn't introduce any compatibility issues, please run the following verification steps:

1. Rebuild the project and check for any compilation errors.
2. Run the project's test suite to catch any potential runtime issues.
3. Verify that any components directly using lsp4j are compatible with version 0.23.1.