Bug 575029

Summary:	--patch-module configuration not copied to project launch
Product:	[Eclipse Project] JDT	Reporter:	Christopher Lamb <christopher.lamb>
Component:	Debug	Assignee:	JDT-Debug-Inbox <jdt-debug-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	sarika.sinha
Version:	4.19
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X
Whiteboard:	stalebug

Description Christopher Lamb

2021-07-26 05:33:19 EDT

We have created a Java project that will patch classes in the JRE Module java.security.jgss using the JEP 261: Module System option --patch-module=

We have configured the project to do so using "Java Build Path / Module Dependencies / Patch with...".

We see the resulting config via Show JPMS Options..., and in the .classpath file.

However, equivalent runtime --patch-module= config is NOT automagically added to the project .launch file.

As a workaround we have manually added the command line config suggested by Show JPMS Options.. to a .launch VM Argument e.g.

--patch-module java.security.jgss=/Users/christopherlamb/Projects/JGSSDebug2/bin

This is with the following Eclipse and Java Versions:

Version: 2021-03 (4.19.0)
Build id: 20210312-0638

AzulOpenJDK Java 11.0.11

See also:
https://stackoverflow.com/questions/68501382/how-to-make-eclipse-run-patched-jre-modules-on-jdk9-with-the-patch-module-java

Comment 1 Sarika Sinha

2021-07-27 01:32:43 EDT

If you can attach a sample project it will be much faster to analyze and understand the problem.

Comment 2 Christopher Lamb

2021-07-28 10:42:13 EDT

See two sample projects here https://github.com/FlyingSheepOnSailfish/JGSSDebug

JGSSDebug is the project containing the classes that patch / over-ride classes in the JRE Module java.security.jgss

JGSSDebug-Test is a project calling / depending on JGSSDebug. I launch from the main of this project.

Comment 3 Eclipse Genie

2023-07-19 18:52:35 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.