[MTA-4033] Put gradle task in a better place

[jmle]

https://issues.redhat.com/browse/MTA-4033
konveyor/analyzer-lsp#869

Summary by CodeRabbit

• Chores
  • Updated the destination path for a Gradle build file within the container environment. No impact on application features or user experience.

[coderabbitai]

Walkthrough

The Dockerfile was updated to change the destination path where the Gradle build file is copied during the image build process. The file is now placed in /usr/local/etc/task.gradle instead of /root/.gradle/task.gradle. No other modifications were made.

Changes

Cohort / File(s)	Change Summary
Dockerfile Path Update Dockerfile	Changed the destination path for copying the Gradle build file from /root/.gradle/task.gradle to /usr/local/etc/task.gradle.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

In Docker’s warren, files do hop,
From root to local, they flip and flop.
A build file’s journey, short and sweet,
Now lives where system paths and configs meet.
With every tweak, the image grows neat—
A rabbit’s work is never complete! 🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • Explain this complex logic.
  • 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 explain this code block.
• 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 explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests 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: 0

🧹 Nitpick comments (2)

Dockerfile (2)

39-42: Minor: align the explanatory comment with the new destination

The comment at Line 39 still implies the file is copied into the Gradle user-home. Consider updating it so future readers don’t wonder why we create /root/.gradle but write the task elsewhere.

-# Copy "download sources" gradle task. This is needed to download project sources.
+# Copy the "download sources" Gradle task (used by the analyzer) into a
+# shared location inside the image.

---

40-41: Clean-up: remove the now-unused /root/.gradle directory if not required

If the sole purpose of /root/.gradle was to host task.gradle, the RUN mkdir /root/.gradle line can be dropped.
Keeping it is harmless but increases layer size and may confuse maintainers. Verify whether Gradle actually needs a pre-created user-home in this image.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 85ebf85 and c7d94ed.

📒 Files selected for processing (1)

• Dockerfile (1 hunks)

🔇 Additional comments (1)

Dockerfile (1)

39-42: No stale references to the old task.gradle path found

I searched the entire repository for any hard-coded references to the old /root/.gradle/task.gradle location—including both “.gradle/task.gradle” and explicit -b task.gradle flags—and none were found. No further changes are needed.