commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A. Soroka (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COMMONSRDF-75) Migrate to Java 9 using JPMS
Date Mon, 05 Mar 2018 20:11:00 GMT

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

A. Soroka commented on COMMONSRDF-75:
-------------------------------------

Having some project phases is a great idea. Let's unpack your first phase: "Move commons to
JPMS". I take it that would include:
 # Add {{module-info.java}}, by some automated means (e.g. Maven action).
 # Add an integration test to prove that the new modules can be used by JPMS on Java 9.

?

> 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)

Mime
View raw message