db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6945) Re-package Derby as a collection of jigsaw modules
Date Fri, 01 Dec 2017 03:41:00 GMT

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

Rick Hillegas commented on DERBY-6945:
--------------------------------------

Alex Buckley in the Oracle Java group makes the following recommendations via private email:

1) Avoid generic-sounding names for the modules. Be specific and descriptive.

2) Try to remove the engine's dependency on java.management.

3) Consider adding some aggregator modules, and in particular, a master aggregator module
called derby, which would be akin to java.se.

4) Give some thought to writing concise one-line descriptions of the modules similar to those
at https://docs.oracle.com/javase/9/docs/api/overview-summary.html.


> Re-package Derby as a collection of jigsaw modules
> --------------------------------------------------
>
>                 Key: DERBY-6945
>                 URL: https://issues.apache.org/jira/browse/DERBY-6945
>             Project: Derby
>          Issue Type: Improvement
>    Affects Versions: 10.13.1.2
>            Reporter: Rick Hillegas
>         Attachments: jdeps.out.tar
>
>
> Once we commit to building with Java 9 (see DERBY-6856), we should consider re-packaging
Derby as a set of jigsaw modules. This would result in a different set of release artifacts.
This might be a good opportunity to address the Tomcat artifactory issues raised by issue
DERBY-6944.



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

Mime
View raw message