Welcome to the public discussion channel for the Ceylon programming language (https://ceylon-lang.org)
Anyway, when I instruct Ceylon IDE to consider a certain directory as "resources", the actual files inside don't appear inside the .car module.
Maybe this is about layout: the resources I'm trying to get in are not located in the resources root.
For example "META-INF/services/some.file"
or "some/package/hierarchy/Messages.properties"
take close look to the docs
Suppose the following code occurs in a module named
`com.redhat.example`:
assert (exists resource
= `module`.resourceByPath("file.txt"));
print(resource.textContent());
Then the resource named `file.text` should be placed in
the subdirectory `com/redhat/example/` of the resource
directory.
In your resources folder You must recreate fully qualified path with the name of the module so If You have module named
com.redhat.example All files (resources) which will be embed into this module must be placed in resources/com/redhat/example or other resources folder included into classpath
then You can query them like
in doc above
if You query from other module You would use metamodel call
`module your.module.name`
here is settings xml which works
And then in Your Ceylon project in IDE
Your project -> properties -> ceylon build -> module repositories -> Add maven repository and from file explorer select settings.xml
<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
<profiles>
<profile>
<id>central</id>
<repositories>
<repository>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
<id>Maven Central</id>
<name>Maven Central</name>
<url>https://repo1.maven.org/maven2/</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
<id>central</id>
<url>http://repo1.maven.org/maven2</url>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>central</activeProfile>
</activeProfiles>
</settings>
This is my setup:
Ceylon IDE > Project Properties > Ceylon Build > Build Paths > Resources =
ceylon-tui/src/main/resources
Inside
ceylon-tui/src/main/resources there is this subtree : peu/ceylon/tui/Messages.properties
Wait, something changed since yesterday.
The
The
.car archive now has the resources inside and in the proper place.
Hmmmmmmmm.
Does the module import notation for maven imports allows specifying the classifier?
Does the module import notation for maven imports allows specifying the classifier?
But I think this is will simply not work out of the box.
JNR native libraries are distributed in a separate artifact.
Apparently, Ceylon considers it a separate module.
Module isolation makes it not find its own resources.
JNR native libraries are distributed in a separate artifact.
Apparently, Ceylon considers it a separate module.
Module isolation makes it not find its own resources.
Java ecosystem is not yet prepared for module isolation.
Is there a way to hack the module system so that resources inside
jffi.native are exposed to jffi?
But as you've noted, the module system can cause a lot of problems when using Maven modules, since it creates unwanted isolation that the Maven modules were not designed for
This is especially a problem when your Ceylon module imports multiple Maven modules that you expect to cooperate with each other, but are instead isolated.
Ceylon is much more enjoyable to use when not attempting to use big maven frameworks with lots of dependencies
I don't see a problem with dependencies.
Dependencies are fine.
But, yes, the market is still not ready for modules.
In the particular case of JNR, OSGi works because
It probably doesn't work with java 9 modules (which I intend verify soon).
Dependencies are fine.
But, yes, the market is still not ready for modules.
In the particular case of JNR, OSGi works because
jffi.native is a fragment of jffi.It probably doesn't work with java 9 modules (which I intend verify soon).
About log4j2, Ceylon IDE fails the maven style import saying "cannot find module source artifact etc."
My objective in this case is just to demonstrate an application of
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.