-
## 環境
* Windows 10 Pro
* Visual Studio Code 1.56
* Java Extension Pack 0.14.0
* Java Test Runner 0.29.0
## 問題
JPMSの（module-info.javaを含む）テストを実行しようとすると、
TestEngineを探しに行くときにネットワークパスを探しに行ってエ…
-
None of the smallrye artefacts contain JPMS metadata making use of any libraries which depend upon smallrye exceedingly painful for Java versions > 8.
As JavaFX mandates Java 11 or later to use many …
-
**Describe the bug**
jakarta.activation/jakarta.activation-api/1.2.2 contains this OSGi header:
```
Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=9.0))"
```
**To Reproduce**
…
-
Assume a JPMS build which depends on Scala 3.
```
dependencies {
…
implementation 'org.scala-lang:scala3-library_3:3.2.1'
}
```
Such a build needs to patch the org.scala.lang.scala3…
-
To help users use Flow with Java 9 before we have had the chance to properly modularize everything, we should include a suitable `Automatic-Module-Name` entry in the manifest of each jar file.
-
when adding the exposed dependency, when the application starts, it starts giving an error (see below), trying to exclude nothing helps
```
Error occurred during initialization of boot layer
java.l…
-
So I want to use my JPMS modules as modulith modules. I looked at writing my own `ApplicationModuleDetectionStrategy` but it seems to hide the real class and thus I can't actually ask for the ask the …
-
https://jlbp.dev/JLBP-19 says
> If classes from the same package appear in Maven artifacts with different group IDs or different artifact IDs, it is easy to construct a classpath that splits packag…
-
Hi, here is my pom part:
```
org.simplejavamail
simple-java-mail
6.0.4
```
module-info:
```
requires org.simplejavamail;
requires org.simplejavamai…
-
# _Issue_title_
No Auto-Module-Name manifest attribute and split packages
## _Issue_description_
The lack of Auto-Module-Name manifest attribute and reusing packages across modules renders the li…