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

ProcessorTests are currently unable to reload Mapper implementation class

未关闭
#4,132 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
java

调研方向

Start by locating the ProcessorTests infrastructure and the @ProcessorTest handling around Mappers.getMapper(MyMapper.class). Reproduce the issue by comparing the mapper's code-source location across test runs, then trace the class-loading behavior. Done means each test run can load the mapper implementation generated for that run rather than reusing the first-loaded class.

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

描述

bug test
Expected behavior

When a Mapper implementation is loaded in a test like

@ProcessorTest
void someTest() {
    MyMapper mapper = Mappers.getMapper( MyMapper.class );
}

the loaded Mapper should be the one generated by the test. For example the one generated by Eclipse or JDK compiler.

Actual behavior

Currently a Mapper implementation is only loaded once from whatever test run loads it first.
This a limitation of the used class loading.

Steps to reproduce the problem
@ProcessorTest
void someTest() {
    MyMapper mapper = Mappers.getMapper( MyMapper.class );
    System.out.println( mapper.getClass().getProtectionDomain().getCodeSource().getLocation() );
}

You will see that the source code location does not change

MapStruct Version

All versions

主要语言
Java
星标
7.7k
派生
1.1k
PR 合并指标
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

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

mapstruct/mapstruct 的其他 Issue

查看 mapstruct/mapstruct 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

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