microsoft / microsoft/vscode-java-debug
maven-jar-plugin use app-to-import setting make debug error
未关闭
还没有人认领这个 Issue。
ai-triaged
bug
launch
- 主要语言
- TypeScript
- 星标
- 591
- 派生
- 429
- 平均合并
- 1 天 9 小时
- 30 天内合并 PR
- 19
描述
[provide a description of the issue]
Environment
- Operating System:
Windows_NT x64 10.0.17763 - JDK version:
java version "1.8.0_202"
Java(TM) SE Runtime Environment (build 1.8.0_202-b08)
Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed mode) - Visual Studio Code version:
version: 1.48.1 (system setup)
commit: 3dd905126b34dcd4de81fa624eb3a8cbe7485f13 - Java extension version:
v0.10.0 - Java Debugger extension version:
v0.10.0
Steps To Reproduce
- [step 1]
I have two module in a project.They are all application.The gvt-bdp-stats-scheduler module dependent on gvt-bdp-app module.
the A module's setting like this.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>jar</goal>
</goals>
<phase>package</phase>
<configuration>
<!--to be imported on other projects-->
<classifier>app-to-import</classifier>
<includes>
<include>**/entity/*</include>
</includes>
</configuration>
</execution>
</executions>
</plugin>
the B module's setting like this.
<dependency>
<groupId>com.gvt.bdp</groupId>
<artifactId>gvt-bdp-app</artifactId>
<version>${revision}</version>
<classifier>app-to-import</classifier>
</dependency>
[attach a sample project reproducing the error]
attach logs
Current Result
It's normal when I run with jar.But in debug, it cause java.lang.TypeNotPresentException: Type com.entity.OrderStatsEntity not present
Expected Result
The project work in Idea is well.
Additional Informations
When I open the run jar file of temp, the MANIFEST.MF there is no gvt-bdp-app's class-path definition in the file when I debug gvt-bdp-stats-scheduler.


贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
先从 issue 中所示的 Maven 插件和依赖配置开始,然后使用所述的双模块项目重现调试启动。将调试生成的临时 JAR manifest 与正常运行进行比较;当依赖 class path 在调试期间存在且不再发生 TypeNotPresentException 时,即表示完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- java
- 领域
- devtools
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 20/100