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
In order to play nicely with programs/libraries that have been modularized, it would be good if Automatic-Module-Name properties could be added to the protobuf-java jar files. This would give a stable name that can be used in the requires directives of modules.
Do not release to Maven Central a modular jar file that depends on an automatic module, unless the automatic module has an "Automatic-Module-Name" MANIFEST.MF entry.
I'd submit a PR, but I'm not sure what module names you'd want to use. Presumably something like com.google.protobuf.core and com.google.protobuf.lite.
The text was updated successfully, but these errors were encountered:
Adding Automatic-Module-Name is a step in the right direction. Fully modularize protobuf-java would be the next step.
A drastic shift was recently done for C++ when it moved to C++11, why not also shift Java towards Java LTS 11.
Hello.
In order to play nicely with programs/libraries that have been modularized, it would be good if
Automatic-Module-Name
properties could be added to theprotobuf-java
jar files. This would give a stable name that can be used in therequires
directives of modules.http://blog.joda.org/2017/05/java-se-9-jpms-automatic-modules.html
I'd submit a PR, but I'm not sure what module names you'd want to use. Presumably something like
com.google.protobuf.core
andcom.google.protobuf.lite
.The text was updated successfully, but these errors were encountered: