Feature Request: Make Jinjava Dependencies Easily Upgradeable

未關閉
#1,343 0 則留言 8 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
12/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
java
領域
build-system

研究方向

The issue asks for a Java artifact that declares Jsoup and similar libraries as ordinary Maven dependencies instead of bundling them, so consumers can override versions in their own pom.xml. Start by finding where the build packages Jsoup into the Jinjava artifact, then decide how a distribution without it would be published. Done means a consumer can pin a patched Jsoup version through Maven with no Jinjava release, and the maintainers have agreed on the packaging approach.

由索引模型根據 Issue 內容生成。

描述

Context

A security vulnerability has been identified in the version of Jsoup used by Jinjava. Since Jsoup is bundled directly into Jinjava, upgrading it through the consuming project's pom.xml is not straightforward.

This creates a dependency on a new Jinjava release to benefit from security fixes, potentially delaying remediation.

Proposed Improvement

Provide a Java distribution of Jinjava that exposes dependencies such as Jsoup as external Maven dependencies, with versions that can be overridden or upgraded independently through the consuming project's pom.xml.

Ideally, these dependencies should be declared as regular Maven dependencies rather than being shaded or embedded directly into the Jinjava artifact.

Benefits
  • Faster security remediation: Upgrade vulnerable dependencies without waiting for a new Jinjava release.
  • Improved dependency management: Let consuming projects control dependency versions through Maven.
  • Reduced security exposure: Minimize the time applications remain vulnerable to known security issues.
  • Greater flexibility: Make it easier to keep Jinjava-based applications aligned with dependency security policies.
Expected Outcome

A Jinjava Java artifact with externally managed, independently upgradeable dependencies, allowing consumers to apply security fixes as soon as patched dependency versions become available.

主要語言
Java
星號
789
分支
185
平均合併
1 小時 33 分鐘
30 天內合併 PR
10

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

HubSpot/jinjava 的其他 Issue

查看 HubSpot/jinjava 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。