Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Jandex extended path

未关闭 适合新手
  • 哪里不对？
#8,451 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
74/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
冷清
领域
documentation

调研方向

从 issue 中链接的现有 applicationManager 和应用程序配置参考主题开始。将 readWebInfJandex 属性、其默认值、支持的值、与 useJandex 的关系、优先级以及提供的示例添加到这两个主题中。完成标准是两个已渲染的参考页面都准确记录 opt-in 行为以及 WEB-INF/classes/META-INF/jandex.idx 位置。

由索引模型根据 Issue 内容生成。

描述

Feature epic details
Operating systems

Does the documentation apply to all operating systems?

  • Yes
  • No; specify operating systems: ______
Summary

Provide a concise summary of your feature. What is the update, why does it matter, and to whom? What do 80% of target users need to know to be most easily productive using your runtime update?

Configuration:

Elements: applicationManager, application
Attribute: readWebInfJandex
Description: When performing class scans, when "useJandex" is true, also look for a jandex index under "/WEB-INF/classes/META-INF/jandex.idx".
Possible values: true | false
Default value: false

Examples

 <applicationManager useJandex="true" readWebInfJandex="true"/>
 <application location="TestServlet40.ear" useJandex="true" readWebInfJandex="true"/>

Discussion

Initial Liberty support for jandex looks for jandex indices at "/META-INF/jandex.idx" relative to module roots. That is correct for EJB modules, but is incorrect for web modules. The industry standard location for jandex indices within web modules is relative to the web module class path root: "/WEB-INF/classes/META-INF/jandex.idx".

The new attribute readWebInfJandex enables support for the industry standard location, "/WEB-INF/classes/META-INF/jandex.idx". When the new attribute is enabled, when processing web modules, Liberty looks for jandex indices in both the original location relative to the module root, and at the industry standard location relative to the web module class path root. (If indices are present at both locations, the "/META-INF/jandex.idx" location has precedence.)

The new attribute may be used in the applicationManager element and in the application element. When used in the applicationManager element, the attribute value applies to all applications. When used in an application element, the attribute value applies to that one application. (A value supplied in the application element overrides a value supplied in the applicationManager element, for that one application.)

To reduce migration risks, the new attribute is an opt-in attribute. The default value is false. A true value must be explicitly set to enable support for the new location.

Support for jandex is not enabled by default. The useJandex option must be explicitly set to true to enable jandex support. The new readWebInfJandex option is meaningful only when useJandex is true.

Updates to existing topics

The attribute is being added to two existing configuration elements, application and applicationManager.

https://openliberty.io/docs/latest/reference/config/applicationManager.html
https://openliberty.io/docs/latest/reference/config/application.html

Create a new topic

N/A

主要语言
没有语言数据
星标
14
派生
58
平均合并
1 小时 4 分钟
30 天内合并 PR
21

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

OpenLiberty/docs 的其他 Issue

查看 OpenLiberty/docs 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。