Ceylon JPMS split package conflict

Split package conflict when Ceylon module shares a package also used by a JPMS module

0 reputation · 23 Jun 2025, 01:17 UTC

19.8K views0

Goal: Determine if Ceylon modules can interoperate with JPMS without violating JPMS split-package prohibition, given Ceylon's shared package feature allows the same package to appear in multiple modules.

Constraints: Ceylon's module descriptors permit shared packages; JPMS forbids split packages; no official migration path exists; Ceylon reached end-of-life in 2018, leaving this alignment as an unresolved design question.

Can Ceylon's shared package mechanism be mapped to JPMS exported packages without causing split package violations? Is it necessary to refactor Ceylon modules to eliminate shared packages before using JPMS? Does the Ceylon runtime support JPMS module path when run on JDK 9+?

2,032 following

Keep exploring this topic

Coarse‑grained auto‑export vs. manual module‑info.java for Ceylon JPMS

Goal: enable fine‑grained control over which Ceylon packages are exported as JPMS modules when the module is consumed from Java 9+ without leaking internal APIs.

Limits of Ceylon 1.3.3 Module System for Transitive Dependency Version Conflicts

Investigating the documented limits of Ceylon 1.3.3’s module system for resolving transitive dependency version conflicts, including the lack of automatic mediation and the need for manual exclusion or alignment.

Ceylon 1.3.3 JVM Module to Java Interop: Resolving Module Versioning and Classloader Conflicts

When integrating Ceylon 1.3.3 modules into a Java project, developers face challenges with module versioning, classloader isolation, and runtime dependencies. What strategies can mitigate these issues?

Module resolution failure in JVM production environments

Investigating potential module resolution failures when moving Ceylon JVM targets from local development to production environments.

Split package conflict when Ceylon module shares a package also used by a JPMS module

0 answers

Your perspective belongs here.

0 question comments