moditect | Tooling for the Java Module System

by moditect Java Version: 1.0.0.Final License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | moditect Summary

moditect is a Java library. moditect has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has high support. You can download it from GitHub.

Version 1.0.0.RC1 - 2020-03-24. The ModiTect project aims at providing productivity tools for working with the Java module system ("Jigsaw").

Support

Quality

Security

License

Reuse

Support

moditect has a highly active ecosystem.

It has 466 star(s) with 61 fork(s). There are 29 watchers for this library.

It had no major release in the last 12 months.

There are 65 open issues and 68 have been closed. On average issues are closed in 92 days. There are 4 open pull requests and 0 closed requests.

It has a negative sentiment in the developer community.

The latest version of moditect is 1.0.0.Final

Quality

moditect has 0 bugs and 0 code smells.

Security

moditect has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

moditect code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

moditect is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

moditect releases are available to install and integrate.

Build file is available. You can build the component from source.

Installation instructions are not available. Examples and code snippets are available.

It has 4412 lines of code, 256 functions and 52 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed moditect and discovered the below as its top functions. This is intended to give you an instant insight into moditect implemented functionality, and help decide if they suit your requirements.

Creates the runtime image
Returns the directory that contains the jmod files to be used
Run jlink
Runs a command with the specified arguments
Executes the add - module - info command
Generate module - info command
Runs the module
Updates the module requires information according to the options defined in the moduleDeclaration
Generate the module list
Runs the jdeps command
Determines the jvm version
Generate the module info
Creates a module configuration based on the overrides
Create a copy of the META - INF directory with the given module name and module name header
Copy the contents of a jar to a temporary directory
Starts the downloader
Downloads a file from an URL
Parses the given string into a package name pattern
Returns a hashCode of this artifact
Parses a string into a dependency pattern
Compares two dependency descriptors
Create a hash code
Checks if this object equals another

Get all kandi verified functions for this library.

moditect Key Features

No Key Features are available at this moment for moditect.

moditect Examples and Code Snippets

No Code Snippets are available at this moment for moditect.

Community Discussions

Trending Discussions on moditect

Maven javafx:jlink. How to specifiy the module-path used?

Distributing JavaFX Applications that use automodules

jlink not using automatic modules

Keycloak-Admin-Client in a JPMS/Jigsaw Java 11 Maven application - Dependency Problems

QUESTION

Maven javafx:jlink. How to specifiy the module-path used?

Asked 2021-Dec-07 at 01:46

I'm currently working on a modular JavaFX application and I'm using maven to compile/deploy it.

One of the dependencies of my application is JBibTex which doesn't have a module-info file so it's used as an automodule. In order for my javafx:jlink to work (because javafx:jlink cannot work on automodules), I had to convert JBibTex to an explicit module. I used the maven's ModiTect plugin for that.

I used ModiTect to generate the module-info file for the JBibTex library and I added it to the JBibTex's jar file (I used moditect:add-module-infos for that).

Now the problem is that javafx:jlink uses the JBibTex.jar file that is located in my ".m2" folder (where maven automatically downloads all your projects' dependencies). The JBibTex.jar file located in my .m2 folder is not the file to which I added the module-info file.

So I still get the error:

Error: automatic module cannot be used with jlink: jbibtex

The explicit JBibtex module that I have generated through the use of ModiTect is automatically put in target/modules by my ModiTect plugin configuration.

How can I get javafx:jlink to use the target/modules/JBibTex.jar file that contains the module-info.class file and not the JBibTex.jar of my .m2 folder?

Here is my pom.xml just in case:

...

ANSWER

Answered 2021-Dec-07 at 01:46

Specifically to answer your question:

How to specify the module-path used?

You could run jlink from the command-line instead of via Maven.

That way you can specify any module path you wish.

From the man page for jlink:

Source https://stackoverflow.com/questions/70250564

QUESTION

Distributing JavaFX Applications that use automodules

Asked 2021-Apr-22 at 13:11

I have created a JavaFX application. It runs perfectly in my Intellij IDE. Now I want to distribute the application - i.e. I want to obtain an installer that users could download and then it would install the application for them.

I found a very interesting article about this here. This blog article basically describes what I want to achieve. There are two differences though:

I am using Maven and not Gradle
I have dependencies which use automodules such as iText7 and apache.commons.lang3

The usage of automodules is making things very complicated. There is a GitHub project called ModiTect (here) that has been written to solve these issues. I have no experience in using ModiTect though and even my Maven knowledge is barely existent (meaning: I don't really know what I am doing in the pom.xml).

What I am looking for is an explanation (step-by-step) as on how to integrate ModiTect (and if necessary jpackage) into my pom.xml in order to obtain an installer for my JavaFX application that uses automodules (and also a sqlite database, which shouldn't be a problem though).

Can somebody provide this explanation or refer me to a tutorial?

I provide a MWE at the end of this question. The MWE ist a TestApp. To illustrate the problem, run the application and press the "Print PDF" button. A pdf is created in resources --> pdf

The MWE will compile and run when executing javafx:run There will be an error related to the usage of automodules when executing javafx:jlink

I don't know how to fix this. ModiTect appears to be a promising addon. Another possible way can be found in this GitHub repo. But as I said before: My Maven knowledge is not sufficient to really grasp what is going on here. Any help would mean a lot to me!

MWE:

pom.xml:

...

ANSWER

Answered 2021-Apr-22 at 13:11

Instead of the javafx maven plugin you could use the moditect plugin to create missing module-info to auto module dependencies and then build the image with moditect.

Such a pom for you could be something like:

Source https://stackoverflow.com/questions/67035353

QUESTION

jlink not using automatic modules

Asked 2020-Sep-26 at 12:11

I created a '.exe' file for a JavaFX application on Windows 10 using jpackage. Afterward, by double-clicking on the application's icon, the app did not start. I realized that I mistakenly used this command, which is tailored for none modular application:

...

ANSWER

Answered 2020-Sep-11 at 08:21

You might want to follow this tutorial: https://github.com/dlemmermann/JPackageScriptFX It also uses jpackage and jlink but in a way that makes it usable for non-modular projects. You can't use jlink directly because it does not support automatic modules but this problem can be avoided by just not using the module system at all.

Source https://stackoverflow.com/questions/63836130

QUESTION

Keycloak-Admin-Client in a JPMS/Jigsaw Java 11 Maven application - Dependency Problems

Asked 2020-Mar-31 at 10:26

maybe someone has already figured that out or has some tips, I would be really thankful.

I'm trying to use the Keycloak-Admin-Client maven dependency in a modularized Java 11 application. The Application is modularized via JPMS/Jigsaw.

I'm using the version 9.0.2 of the Keycloak-Admin-Client.

...

ANSWER

Answered 2020-Mar-31 at 10:26

The problem was that the javax.ws.rs-api artifact Version 2.1 has a different artifact-id "java.ws.rs-api" not "javax.ws.rs-api".

In Version 2.0.1. are packages missing. Version 2.1-m08 works.

Source https://stackoverflow.com/questions/60939868

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install moditect

You can download it from GitHub.
You can use moditect like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the moditect component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: