[
https://issues.apache.org/jira/browse/COMMONSRDF-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16386584#comment-16386584
]
Kamila Molina commented on COMMONSRDF-75:
-----------------------------------------
To be honest I wasn't aware of [Multi-Release jar
files|http://openjdk.java.net/jeps/238]. And yes, let's do it. I am still
learning about some of the new functionalities of JDK9, so I will have to learn
some of the them on the way of the project. Would it be a problem? I can
include in my proposal three main tasks, and later try to extend some work
accord at the timeline of GSoC.
# Move commons to JPMS
# Include Multi-release jar files
# Use the new functionalities of JDK9
What do you think?
> 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)
