A. Soroka commented on COMMONSRDF-75:

Absolutely we need to consider impacts on/from the rest of Commons, but this 
_is_ about Commons RDF only ("Well it would be the task to move commons-rdf 
only to Java 9…"), except in those circumstances in which we can't make it so.

[~kamila.molina97], with that in mind, let' s talk about what you would like to 
write to the ML to offer to do for further discussion there. So far we have:
 # Move Commons RDF to JPMS (each impl in a separate JPMS module, as well as in 
a separate Maven module). My remark about Maven was just to suggest that to the 
extent possible, we want to have necessary metadata created automatically and 
not manually. This task needs to happen in such a way as to continue to provide 
Java 8 -appropriate artifacts.
 # Possibly create multi-release JARs (needs further discussion on the ML).
 # Possibly write a test that shows a correct linkage being made between the 
API and an impl-- this could just fork a test process and do some simple RDF 
calculations, just to demonstrate that the runtime is correctly assembled. This 
may not be needed, if people are willing to trust the work on the first task. 
We can discuss it further on the ML.
 # Per [~erans]'s suggestion, develop some guidelines (a report from the field, 
as it were) for how other components in Commons might make the shift to JPMS.

Does this sound like work you would be interested in and ready to take on? If 
so, you are welcome to write to the dev@ mailing list to get the conversation 
started there. Otherwise, we can cut it down or substitute some things.

> Migrate to Java 9 using JPMS
> ----------------------------
>                 Key: COMMONSRDF-75
>                 URL: https://issues.apache.org/jira/browse/COMMONSRDF-75
>             Project: Apache Commons RDF
>          Issue Type: New Feature
>          Components: api, build, jena, jsonld-java, parser, rdf4j, simple
>            Reporter: Kamila Molina
>            Priority: Minor
>              Labels: gsoc2018, library
> Add module-info.java for each module. JPMS allows to create libraries with 
> strong encapsulation; however, this migration will bring with many effects 
> that can potentially break code. For example, JDK 9 doesn't gives access for 
> internal types such as {{sun.misc.BASE64Encoder.}}

This message was sent by Atlassian JIRA

Reply via email to