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 摘要。