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
Since no module-info exists, nor does an Automatic-Module-Name exist in the MANIFEST.MF, the generated name of this library becomes "ergo.appkit.2.12" which is an invalid name because no part of it can start with a number.
Unfortunately, fixing that will not be enough because the dependencies of this library also do not come with a module name and result in invalid names being generated due to the strange library_2.12 format used by Scala.
However, that does not mean that appkit should not have an Automatic-Module-Name. For example, the scala standard library comes with one (scala.library).
The first step to rectifying this problem is to add an Automatic-Module-Name to appkit. It should be named org.ergoplatform.appkit in my opinion.
The text was updated successfully, but these errors were encountered:
Since no module-info exists, nor does an Automatic-Module-Name exist in the MANIFEST.MF, the generated name of this library becomes "ergo.appkit.2.12" which is an invalid name because no part of it can start with a number.
Unfortunately, fixing that will not be enough because the dependencies of this library also do not come with a module name and result in invalid names being generated due to the strange library_2.12 format used by Scala.
However, that does not mean that appkit should not have an Automatic-Module-Name. For example, the scala standard library comes with one (scala.library).
The first step to rectifying this problem is to add an Automatic-Module-Name to appkit. It should be named
org.ergoplatform.appkit
in my opinion.The text was updated successfully, but these errors were encountered: