Make sure the Menas uses only one source of project version information
- 主要语言
- Scala
- 星标
- 33
- 派生
- 16
- PR 合并指标
- 30 天内没有已合并 PR
描述
## Background
Project version used in Spring (Menas UI) in different parts of code can theoretically diverge, which would break the UI
## Feature
`"/${enceladusVersion()}/**"` is supposed to be a root path to our sources. Which is set using `spring.resources.chain.strategy.fixed.version` from app properties. But here we "enable" it using `ProjectMetadata.enceladusVersion`. And in some other places of our project (`index.html`), we again use `ProjectMetadata.enceladusVersion`. If these two versions ever become different, Menas becomes unusable.
贡献指南
调研方向
Trace the uses of ProjectMetadata.enceladusVersion, enceladusVersion(), spring.resources.chain.strategy.fixed.version, and the version reference in index.html. Determine where the project version is defined and how the Spring resource path and Menas UI consume it. Done means these consumers use one consistent source so the UI cannot break when versions diverge.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- scala, spring
- 领域
- full-stack
- Issue 类型
- 重构
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 35/100