[ 
https://issues.apache.org/jira/browse/COMMONSRDF-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388951#comment-16388951
 ] 

Kamila Molina commented on COMMONSRDF-75:
-----------------------------------------

Hi [~ajs6f], [~erans],

I agree that this thread needs further discussion. The main task I will be 
interested is moving commons-rdf to JDK 9 (point 1), which can help to have a 
ground base for other modules (point 4), maybe in a wiki format.  We can 
absolutely work on some tests (point 3). I was looking at coomns-rng; the 
examples doesn't look as scary as thought :). Finally, we can leave the 
possibility to have a multi-release JARs (point 2) in the last phases of GSoC 
while we decide something in the ML. I will open a thread there in order to see 
what comments come up. 

_Disclaimer:_ I am still moving to JDK 9, and learning new Maven 
functionalities. So, some things I will to learn on the way. Sorry if I ask 
some things that might be obvious, but I hope you can point me out to some 
resources.

> 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
(v7.6.3#76005)

Reply via email to