Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Support Java module system

Abierto
#585 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
java, ruby
Área
build-system

Línea de trabajo

The payload names no source files. Start by finding where Warbler assembles the fat jar with its nested JRuby, JRuby stdlib and gem jars, and how those jars are loaded at runtime through custom classloaders. The open question is how a module-compatible (JPMS) layout can carry nested jars, and that needs a design decision before any code. Done would be an agreed design plus a build that runs without the restricted-method and Unsafe warnings quoted in the issue.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Warbler currently generates a single fat jar with nested jars for JRuby, JRuby's stdlib, and any other libraries needed. Those jars then get unpacked or loaded into custom classloaders at runtime.

This system will definitely need tweaks to support JPMS, the Java module system, and I do not know how to handle nested jars with a module-compatible package. We'll need to figure that out.

Modularizing will also get us closer to eliminating JVM warnings and errors related to native access and reflective access to JDK classes needed by JRuby proper, such as the following two warnings from JDK 25:

WARNING: A restricted method in java.lang.System has been called
WARNING: java.lang.System::load has been called by com.kenai.jffi.internal.StubLoader in an unnamed module (file:/var/folders/5n/y5_kd6x94rndnyjh4519bp2w0000gn/T/jruby9794538498169631325extract/jruby-core-10.0.2.0-complete.jar)
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module
WARNING: Restricted methods will be blocked in a future release unless native access is enabled

WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
WARNING: sun.misc.Unsafe::putLong has been called by com.kenai.jffi.UnsafeMemoryIO$UnsafeMemoryIO64 (file:/var/folders/5n/y5_kd6x94rndnyjh4519bp2w0000gn/T/jruby9794538498169631325extract/jruby-core-10.0.2.0-complete.jar)
WARNING: Please consider reporting this to the maintainers of class com.kenai.jffi.UnsafeMemoryIO$UnsafeMemoryIO64
WARNING: sun.misc.Unsafe::putLong will be removed in a future release

Without modules, there's no way for us to configure the generated jar with necessary permissions.

Lenguaje dominante
Ruby
Estrellas
901
Forks
206
Merge medio
1 d 10 h
PR fusionados (30 d)
3

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de jruby/warbler

Todos los issues de jruby/warbler

Issues similares

Más issues de Ruby

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.