commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Coburn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COMMONSRDF-64) Add Automatic-Module-Name to bundle manifest
Date Fri, 29 Sep 2017 13:28:00 GMT

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

Aaron Coburn commented on COMMONSRDF-64:
----------------------------------------

The JDK9 module names are the same as the java package names: org.apache.commons.rdf.api for
org.apache.commons.rdf.api, etc, which is the general practice for doing this. So, it's debatable
whether this needs to be specially documented. That is, one can see the package names just
by looking at the current javadocs. I've seen other projects document this change in release
notes, but do you think that the main website should also document the module names?

> Add Automatic-Module-Name to bundle manifest
> --------------------------------------------
>
>                 Key: COMMONSRDF-64
>                 URL: https://issues.apache.org/jira/browse/COMMONSRDF-64
>             Project: Apache Commons RDF
>          Issue Type: Improvement
>          Components: api, jena, jsonld-java, rdf4j, simple
>    Affects Versions: 0.3.0
>            Reporter: Aaron Coburn
>            Assignee: Stian Soiland-Reyes
>             Fix For: 1.0.0
>
>
> The JDK 9 module system will honor an Automatic-Module-Name manifest header when importing
modules. It would be nice if the Commons RDF modules provided this.
> In the absence of this header, the modules can still be imported, but the {{requires}}
statement will look different. Adding the header proactively will make the transition to Java9
easier for code that uses the Commons RDF library.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message