question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Problems with java 9

See original GitHub issue

I create hello world project:

"Default documentation for module `test`."

native("jvm")
module test "1.0.0" {
}
shared void run() {
    print("hello");
}

I compile it and run:

java -version
java version "9"
Java(TM) SE Runtime Environment (build 9+181)
Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode)
mmalutin@mm-sky-014 ~/src/1 $ ceylon compile
Note: Created module test/1.0.0
mmalutin@mm-sky-014 ~/src/1 $ ceylon run test/1.0.0
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jboss.modules.ClassLoaderLocalLoader$1 (file:/home/mmalutin/.sdkman/candidates/ceylon/1.3.3/repo/org/jboss/modules/1.4.4.Final/org.jboss.modules-1.4.4.Final.jar) to method java.lang.ClassLoader.getPackage(java.lang.String)
WARNING: Please consider reporting this to the maintainers of org.jboss.modules.ClassLoaderLocalLoader$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
org.jboss.modules.ModuleNotFoundException: javax.xml:7
        at org.jboss.modules.Module.addExportedPaths(Module.java:1193)
        at org.jboss.modules.Module.addExportedPaths(Module.java:1227)
        at org.jboss.modules.Module.addPaths(Module.java:1071)
        at org.jboss.modules.Module.link(Module.java:1398)
        at org.jboss.modules.Module.relinkIfNecessary(Module.java:1426)
        at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:238)
        at org.jboss.modules.Main.main(Main.java:384)
        at ceylon.modules.bootstrap.CeylonRunTool.run(CeylonRunTool.java:367)
        at com.redhat.ceylon.common.tools.CeylonTool.run(CeylonTool.java:547)
        at com.redhat.ceylon.common.tools.CeylonTool.execute(CeylonTool.java:423)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:564)
        at com.redhat.ceylon.launcher.Launcher.runInJava7Checked(Launcher.java:108)
        at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:38)
        at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:31)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:564)
        at com.redhat.ceylon.launcher.Bootstrap.runVersion(Bootstrap.java:162)
        at com.redhat.ceylon.launcher.Bootstrap.runInternal(Bootstrap.java:117)
        at com.redhat.ceylon.launcher.Bootstrap.run(Bootstrap.java:93)
        at com.redhat.ceylon.launcher.Bootstrap.main(Bootstrap.java:85)

Looks like ceylon 1.3.3 is incompatible with java 9

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:7
  • Comments:7 (6 by maintainers)

github_iconTop GitHub Comments

4reactions
FroMagecommented, Oct 2, 2018

Done.

1reaction
FroMagecommented, Sep 27, 2018

Down from 180 to 19 errors.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Java 9 Migration Issues and Resolutions - Baeldung
In this quick tutorial, we'll go through some of the issues related to modules that we may face when migrating an existing application...
Read more >
Java 9+ modularity: The difficulties and pitfalls of migrating ...
In Java 9, all programs are compiled and executed using the module system and the language strongly encapsulates types that are not exported...
Read more >
'Java 9, it did break some things,' Oracle bod admits to devs ...
So why have developers not upgraded? Simply, Java 9 introduced major changes, including internal restructuring, new modularity (known as " ...
Read more >
Java 9 Migration Guide: The Seven Most Common Challenges
Solutions to the seven most common challenges for a Java 9 migration. Each of them explained with background, symptoms, and fixes.
Read more >
Problems with Java modules still plague developers
The Java Platform Module System promised to standardize how Java apps modularized. But years later, the problems with Java modules remain.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found