You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,9 +32,6 @@ You compile the project and you see this warning:
32
32
... and then when you run your program, it crashes when it tries to access the given Scala dependency.
33
33
Paraphrasing [this answer on Stack Overflow](https://stackoverflow.com/questions/48714633/automatic-module-name-containing-number/48714979#48714979), since Java 9, Java does not recognize suffixes in modules names like `_2.13` as version numbers and treat them as integral parts of modules names. So, when your project tries to use a class from the Scala dependency, it will look for `your.scala.dependency.2.13` instead of just `your.scala.dependency`, it will fail to do it, and it will crash.
34
34
35
-
### Installation
36
-
37
-
TBD. (I need some time to upload the plugin to Maven Central. Until then you would have to download the source code and compile the plugin manually, and I would prefer to spare you this).
38
35
39
36
### Usage
40
37
@@ -43,7 +40,7 @@ Add this to the `<plugins>` section of your `pom.xml`:
If the property `Automatic-Module-Name` already exists, the plugin does nothing - we assume that in that case the dependency should already work. This prevents the plugin from modifying the same JAR file more than once.
68
65
66
+
If you find any problems or if you think some kind of an extended functionality would be valuable, feel free to open a ticket under the **Issues** tab here on GitHub. I will se what I can do.
67
+
68
+
### Tests
69
+
70
+
Here's [a small Scala+JavaFX project, built with Maven](https://github.com/makingthematrix/scalaonandroid/tree/main/HelloFxml2), which you can use to test how the plugin works.
71
+
69
72
### Potential problems
70
73
71
74
1. If `Automatic-Module-Name` already exists but is set to a value that is still invalid for Java 9+, the plugin won't fix this.
0 commit comments