Welcome to the public discussion channel for the Ceylon programming language (https://ceylon-lang.org)
dependabot[bot] on maven
Bump json-smart from 1.3.1 to 1… (compare)
dependabot[bot] on maven
dependabot[bot] on maven
Bump httpclient from 4.3.2 to 4… (compare)
jnr-ffi
to define native bindings.
Folks, towards our goal of a 1.3.4 release that is basically 1.3.3 + fixes, I have automated development builds of the Ceylon distribution and Eclipse IDE. They are available at https://github.com/eclipse/ceylon/actions?query=workflow%3Aintegration-build.
Click on the latest successful build and download "ceylon-build-artifacts" which includes a zip file of the Ceylon distribution & IDE.
While these builds should be usable, they currently contain some unwanted new features and compatibility breaks, such as un-curried versions of fold(), etc. Over time, we will improve feature equivalence and compatibility with 1.3.3.
cannot find module source artifact 'ceylon.collection-1.3.3.osgi-5(.car|.jar|.src|.js)'
- dependency tree: 'peu.ceylon.tui/1.0.0' -> 'ceylon.test/1.3.3' -> 'ceylon.collection/1.3.3.osgi-5' module.ceylon /ceylon-tui/src/main/ceylon/peu/ceylon/tui line 5 Ceylon Module Dependency Error
cannot find module source artifact 'ceylon.file-1.3.3.osgi-5(.car|.jar|.src|.js)'
- dependency tree: 'peu.ceylon.tui/1.0.0' -> 'ceylon.test/1.3.3' -> 'ceylon.file/1.3.3.osgi-5' module.ceylon /ceylon-tui/src/main/ceylon/peu/ceylon/tui line 5 Ceylon Module Dependency Error
cannot find module source artifact 'ceylon.language-1.3.3.osgi-5(.car|.jar|.src|.js)'
- dependency tree: 'peu.ceylon.tui/1.0.0' -> 'ceylon.test/1.3.3' -> 'ceylon.language/1.3.3.osgi-5' module.ceylon /ceylon-tui/src/main/ceylon/peu/ceylon/tui line 5 Ceylon Module Dependency Error
cannot find module source artifact 'ceylon.runtime-1.3.3.osgi-5(.car|.jar|.src|.js)'
- dependency tree: 'peu.ceylon.tui/1.0.0' -> 'ceylon.test/1.3.3' -> 'ceylon.runtime/1.3.3.osgi-5' module.ceylon /ceylon-tui/src/main/ceylon/peu/ceylon/tui line 5 Ceylon Module Dependency Error
cannot find module source artifact 'com.redhat.ceylon.dist-1.3.3.osgi-5(.car|.jar|.src|.js)'
- dependency tree: 'peu.ceylon.tui/1.0.0' -> 'ceylon.test/1.3.3' -> 'com.redhat.ceylon.dist/1.3.3.osgi-5' module.ceylon /ceylon-tui/src/main/ceylon/peu/ceylon/tui line 5 Ceylon Module Dependency Error
1.3.4
and 1.3.4-SNAPSHOT
, but, these version were not found.
osgi-5
suffix is present on the module names? This happens at the cli as well. Perhaps there's a problem with my build script.
1.3.4-SNAPSHOT
modules, the Ceylon SDK ships separately from the dist, so you'll need to make the repository (directory) holding the sdk available to the compiler, or copy the modules to ~/.ceylon/repo
osgi-5
naming is not the cause of the error. It's more a confusing message related to the fact that the osgi dependency resolver is used at some point
./resource/com/example/thing/ROOT/META-INF/MANIFEST.MF
in https://ceylon-lang.org/documentation/1.3/reference/tool/project/
ServiceLoader
can't find it.
CeylonModuleClassLoader.getResources
returns an empty enumerator.
ServiceLoader.load(``Service``)
which delegates to ServiceLoader.load(Service.class, Service.class.getClassLoader())
which eventually calls CeylonModuleClassLoader.getResources
@kiti-nomad what John told is correct, but in short, AOT stands for “Ahead of Time” compilation and JIT stands for “Just in time compilation”.
The main difference is when the compiler generates specific machine code instructions and performs optimisations.
With AOT, the compiler generates architecture specific binary before a single line of code is executed—i.e. Ahead of (execution) Time. The optimizations that a compiler can do at that time are extensive, but can not accout for runtime characteristics of the particular program.
With JIT, the compiler starts out by interpreting the code when first executed and as it gets more info on the runtime characteristics of the code, it starts replacing bits of the interpreted runtime with architecture specific machine instructions, applying optimizations as it is running the code. Effectively, creating optimized set of instructions Just in the time (of execution).