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
This is because the jars share some (java class) code in the same packages. If they are used in conjunction (i.e. both) in java 11, there will be compile and/or runtime errors.
The new java 11 (or java 9) module system does not like this kind of 'split jars'. The agreed-upon long-term solution to split jars is to separate the package namespaces (i.e. each package name is only used in one distinct jar).
An alternative to separation would be merging the 2 jars into one (jingtrang.jar).
The text was updated successfully, but these errors were encountered:
This is because the jars share some (java class) code in the same packages. If they are used in conjunction (i.e. both) in java 11, there will be compile and/or runtime errors.
The new java 11 (or java 9) module system does not like this kind of 'split jars'. The agreed-upon long-term solution to split jars is to separate the package namespaces (i.e. each package name is only used in one distinct jar).
An alternative to separation would be merging the 2 jars into one (
jingtrang.jar
).The text was updated successfully, but these errors were encountered: