Eclipse Community Forums: Java Development Tools (JDT) » module path jars not included on runtime by default

Home » Language IDEs » Java Development Tools (JDT) » module path jars not included on runtime by default

module path jars not included on runtime by default [message #1863627]

Fri, 16 February 2024 17:48

Eclipse User

it should be by default that everything in the build module path section also loads fully during the run button press. currently you have to twice configure the same library to run from the runtime settings (why these are even separate at all) by setting dependencies -> the "add modules" setting from "---" to "MODULE PATH".

Also run time settings dont update with project file structure changes and fail to run -> manual editing of the run configuration.

ps. someone broke variable high-lighting for large .java files during some last update.

ps. when making a javafx runnable jar with packaged jar libraries, the jar will not run in oracle jdk 21 (in java-17 compatibility mode).

[Updated on: Fri, 16 February 2024 18:15] by Moderator

Re: module path jars not included on runtime by default [message #1863629 is a reply to message #1863627]

Sat, 17 February 2024 00:56

Eclipse User

Tapio Palomäki wrote on Fri, 16 February 2024 22:48

ps. when making a javafx runnable jar with packaged jar libraries, the jar will not run in oracle jdk 21 (in java-17 compatibility mode).

Hello there,

I have:
eclipse-SDK-4.30-win32-x86_64.zip
openjdk-21_windows-x64_bin.zip
JavaFX 21
Windows 10

The project is Maven.

<properties>
<maven.compiler.target>17</maven.compiler.target>
<maven.compiler.source>17</maven.compiler.source>
</properties>

I am getting those messages:
- Build path specifies execution environment JavaSE-17. There are no JREs installed in the workspace that are strictly compatible with this environment.
- The compiler compliance specified is 17 but a JRE 21 is used

The project is working with no problems when using a JavaFX runnable jar with packaged jar libraries.

The only difference we have is the JDK. So it's worth a try.

Re: module path jars not included on runtime by default [message #1863632 is a reply to message #1863629]

Sat, 17 February 2024 06:34

Eclipse User

I dont want to use maven, only IDE. I'm not using any build tool other than IDE. I upgraded to java-21, why did not eclipse find it out automatically even if it was installed on the system.

eclipse does not package native dlls into the runnable jar by default, even if they are specified as native directory in the user library.

ps. run configurations do not match what they are configured for, I had to delete every configuration and make a new one to make things work again.

[Updated on: Sat, 17 February 2024 06:38] by Moderator

Re: module path jars not included on runtime by default [message #1863633 is a reply to message #1863632]

Sat, 17 February 2024 07:19

Eclipse User

Hi,

Maven is not a MUST in eclipse. (I myself start to use it quite late in life and I must admit that I work harder before that...)

You can add other JDKs using this:
index.php/fa/43982/0/

You might have multiple JDK on the system, and you can select the one you want for your project.

Attachment: 2024-02-17_14-11-11.png
(Size: 41.82KB, Downloaded 394 times)

Re: module path jars not included on runtime by default [message #1863810 is a reply to message #1863633]

Wed, 28 February 2024 00:27

Eclipse User

yeah the jdk should have been there by default and I added it already before coming here. no assistance needed there. just wondering why its not automatic. I think the helping proposal computer is broken.

I just wanted to point out what would be the better ui solution. not asking for help how to do it. thats simple. making ui have automated essential and otherwise nice seems to be hard for most. minimum tutorials and help from forums please thanks. the better the ui and otherwise the less questions have to be asked or road blocks to be dodged while using a program.

this is just basic ui design principles to make all things better. no "learn to use" excuses please thanks.

another issue is with org.eclipse.mylyn.ava.ui.javaAllCompletionProposalComputer and org.eclipse.jdt.ui.TemplateProposalComputer that throw runtime exception when trying adding period after dim in the following:
javafx.scene.shape.Cylinder linecylinder = new javafx.scene.shape.Cylinder(vlinecyl.dim., double height, int divisions);

in the statement the vlinecyl variable is of same named but different package class than then javafx Cylinder class. just reporting the error.

edit: ps, what is the use of IDE if you still have to do things manually by hand. beats me. I then just confess I do things by hand and not use an IDE at all.

[Updated on: Wed, 28 February 2024 02:51] by Moderator

Re: module path jars not included on runtime by default [message #1863812 is a reply to message #1863810]

Wed, 28 February 2024 00:47

Eclipse User

Also when the completion proposal computer broke, it broke home key cursor alignment to tab writing start, now it aligns mostly to the start of the line (left-most position of the line) not start of the tab text.

[Updated on: Wed, 28 February 2024 00:48] by Moderator

Re: module path jars not included on runtime by default [message #1863860 is a reply to message #1863812]

Fri, 01 March 2024 08:45

Eclipse User

also why does eclipse/jre java have trouble locating external native libraries when running even if native libraries are added to module path, and are properly added to the native location of the main library jars of the user library.

[Updated on: Fri, 01 March 2024 08:46] by Moderator

Previous Topic:	Exploring CRUD Operations with Mongoose and MongoDB in JDT
Next Topic:	Any insights or suggestions?

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Aug 31 02:46:14 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter