Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug] gradle启动问题

Open
#1,162 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
java, typescript

Research direction

Start by reading the Gradle toolchain detection and bootRun launch paths; the report names no files or tests. Reproduce on macOS with JDK 21 when Gradle is installed outside the project wrapper, then trace how executable discovery is configured. Done means bootRun can use a configured local Gradle installation and the launch succeeds.

Written by the indexing model from the issue text.

Description

bug issue-form:bug review: low
Platform / 平台

macOS

Area / 模块

Run / 运行

Lithe version / Lithe 版本

v0.6.0

Priority / 优先级

P0 / 立即处理:已严重影响使用体验,核心流程受阻或无法正常使用

OS and architecture / 操作系统与架构

macOS 15.7.4 Apple M4

Environment / 环境信息

JDK 21
Gradle

Steps to reproduce / 复现步骤

1、lithe识别配置
2、启动bootRun 提示gradle was not found in the configured toolchain. Add its executable directory to PATH or configure a project-local toolchain.

Expected behavior / 预期行为

成功启动项目, 更希望能支持像idea那样 能配置本地的外部gradle目录 而不是只通过项目内的wrapper

Actual behavior / 实际行为

报错 gradle was not found in the configured toolchain. Add its executable directory to PATH or configure a project-local toolchain.

Logs or diagnostic output / 日志或诊断输出

Screenshots or recordings / 截图或录屏
Image Image Image
Checklist / 提交前检查
  • I searched existing issues for duplicates. / 我已搜索现有 Issue,确认没有重复报告。
  • I removed secrets and personal data from the report. / 我已从报告中移除敏感信息和个人数据。
Dominant language
TypeScript
Stars
1.8k
Forks
151
Avg merge
11h 45m
Merged PRs (30d)
293

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from 1lck/Lithe-IDEA

All issues in 1lck/Lithe-IDEA

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.