ModelEngine-Group / ModelEngine-Group/fit-framework

fit可执行文件的路径及运行问题

Open
#152 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

in: fit status: feedback-provided type: documentation
Dominant language
Java
Stars
2.1k
Forks
335
PR merge metrics
No merged PRs in 30d

Description

1 文档路径问题

我执行了fitframework-parent的maven clean install后,提示构建成功:

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for FIT Framework Parent 3.6.0-SNAPSHOT:
[INFO] 
[INFO] FIT Framework Parent ............................... SUCCESS [  1.252 s]
[INFO] FIT Protocol Nestable Jar .......................... SUCCESS [  8.175 s]
...
[INFO] FIT Mybatis ........................................ SUCCESS [  6.505 s]
[INFO] FIT Jacoco Aggregator .............................. SUCCESS [  5.629 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  06:09 min
[INFO] Finished at: 2025-06-03T23:05:45+08:00
[INFO] ------------------------------------------------------------------------

构建后产生的fitfit.bat文件位于%FIT_HOME%\build\bin中。而文档03. 使用插件的热插拔能力.md写道,“在变量PATH中新增一个值,为%FIT_HOME%\bin”。

文档中%FIT_HOME%\bin是否应该改为%FIT_HOME%\build\bin

2 Windows下执行报错

在Windows PowerShell中执行fit或fit.bat(全路径或仅输入fit),均报错:

# fit
C:\Users\64245>fit
/bin/bash: D:SyncCodes6-2025fit-frameworkbuildbinfit: No such file or directory
# fit.bat
C:\Users\64245>fit.bat
/bin/bash: D:SyncCodes6-2025fit-frameworkbuildbinfit: No such file or directory
# 全路径
C:\Users\64245>D:\Sync\Codes\6-2025\fit-framework\build\bin\fit.bat
/bin/bash: D:SyncCodes6-2025fit-frameworkbuildbinfit: No such file or directory

报错信息中有Linux环境路径/bin/bash。请问fit能否在Windows下运行?我看到文档中给出了Windows下的环境变量配置方法。

Contributor guide

Open the contributing guide

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.

Research direction

Start by reading docs/framework/fit/java/quick-start-guide/03. 使用插件的热插拔能力.md and inspecting the generated files under build/bin, especially fit and fit.bat. Reproduce the reported commands in Windows PowerShell and check how the paths are passed to /bin/bash. Done means the documented PATH and Windows execution behavior match the actual build output, or the limitation is documented clearly.

Written by the indexing model from the issue text.

Assessment

Tech stack
bash, java, shell
Domain
build-system, cli, documentation, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.