Like Alan, i hope you will re-compile the module, it's more safe. Otherwise, you can use javap to dump the actual module-info.java from the module-info.class, patch it, recompile it with javac and then do a jar --update to replace the module-info.class in the jar
cheers, Rémi ----- Mail original ----- > De: "Alan Bateman" <alan.bate...@oracle.com> > À: "Gunnar Morling" <gun...@hibernate.org> > Cc: "jigsaw-dev" <jigsaw-dev@openjdk.java.net> > Envoyé: Mercredi 11 Mai 2016 14:39:53 > Objet: Re: module-info.java just causes problems > > On 11/05/2016 08:45, Gunnar Morling wrote: > > : > > > > Assuming a developer needs to change the module requirements of one of the > > modules they use, this means - as far as I understand the current design - > > they need to get the source of the module's module-info.java, adapt it as > > needed and re-compile it. > Assuming there are actually good reasons for changing it then I would > hope you would recompile the module completely, not just module > declaration as otherwise it may not be in sync with the code in the module. > > -Alan >
