Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Determine if itext is still used and remove it if it is not

未關閉
#289 2 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 2 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
48/100
Issue 類型
重構
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
java
領域
backend

研究方向

Start by searching the repository for iText dependencies and usages, especially the document writer and any direct user-code references mentioned in the issue. If it is unused, remove the dependency and update the release notes with the compatibility-version guidance and instructions link requested here. Done means confirming whether OIE uses iText and, if not, documenting its removal and how developers can acquire a compatible version with its transitive dependencies.

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

描述

licensing

Based on a discord chat . User edthri had a scanner suggest that iText may not have a compatible license. This was not an issue since OIE and Mirth use iText 2.1.7 which is MPL. tonygermano replied that the iText dependency may not even be needed.

I don't think the document writer depends on it anymore. I'm not sure why it's still included other than there was a log of old user code that called it directly.

The scope of work sound be:

  • Determine if iText is still in use in OIE
  • If iText is not in use, remove it as a dependency
  • Update release notes and clearly state iText is no longer present in Mirth and that developers will need to include it manually. Include a link to separate instructions for how to acquire a compatible version of iText and its transitive dependencies
主要語言
Java
星號
227
分支
81
平均合併
3 天 6 小時
30 天內合併 PR
15

環境準備

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

從這裡開始

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

OpenIntegrationEngine/engine 的其他 Issue

查看 OpenIntegrationEngine/engine 的全部 Issue

相似的 Issue

更多 Java Issue

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

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