[
https://issues.apache.org/jira/browse/DERBY-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13568737#comment-13568737
]
Rick Hillegas commented on DERBY-5955:
--------------------------------------
Thanks, Dag. These changes look good. One additional refinement might be
possible:
In the overview page for the JDBC4 version of org.apache.derby.jdbc, the
summaries for the old datasources are formatted oddly and contain too much
information. I believe this is caused by the fact that the summary table is
generated by the javadoc tool. For each class it makes a summary comment
consisting of everything in the class header comment up to the first period. I
think the summaries for these classes would look more like the summaries for
the other classes if the first period were put after the phrase "full Java SE
8". Then there's the odd formatting of the list which is included in the
summary comment: the two lines of the list are appended and it's hard to parse
sense out of the result. I don't know how to get a readable summary line and
preserve the original list. You might consider collapsing the list into the
preceding sentence in order to make the summary more readable. Thanks.
> Prepare Derby to run with Compact Profiles (JEP 161)
> ----------------------------------------------------
>
> Key: DERBY-5955
> URL: https://issues.apache.org/jira/browse/DERBY-5955
> Project: Derby
> Issue Type: Improvement
> Components: JDBC, Services, SQL
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Fix For: 10.10.0.0
>
> Attachments: apidiff.zip, client-graph.png,
> derby-5955-add-cp2-to-jars.diff, derby-5955-client-restructure-01.diff,
> derby-5955-client-restructure-01.stat,
> derby-5955-client-restructure-02-delta.diff,
> derby-5955-client-restructure-02.diff, derby-5955-client-restructure-02.stat,
> derby-5955-embed-restructure-01.diff, derby-5955-embed-restructure-01.stat,
> derby-5955-embed-restructure-02.diff, derby-5955-embed-restructure-02.stat,
> derby-5955-embed-restructure-03.diff, derby-5955-embed-restructure-03.stat,
> derby-5955-embed-restructure-04.diff, derby-5955-embed-restructure-04.stat,
> derby-5955-embed-restructure-followup.diff,
> derby-5955-embed-restructure-followup.stat, derby-5955-javadoc.diff,
> derby-5955-javadoc-followup.diff, derby-5955-javadoc.status,
> derby-5955-make-tests-run-01.diff, derby-5955-make-tests-run-01.stat,
> derby-5955-make-tests-run-02.diff, derby-5955-make-tests-run-02.stat,
> derby-5955-make-tests-run-03.diff, derby-5955-new-non-jndi-ds-01.diff,
> derby-5955-new-non-jndi-ds-01.stat, derby-5955-new-non-jndi-ds-02.diff,
> derby-5955-new-non-jndi-ds-02.stat, derby-5955-proof-of-concept-2.diff,
> derby-5955-proof-of-concept-2.stat, derby-5955-proof-of-concept.diff,
> derby-5955-proof-of-concept.stat, derby-5955-rename.diff,
> derby-5955-ser-b.zip, derby-5955-ser.zip, embedded-graph.png,
> old-client-graph.png, old-embedded-graph.png, publishedapi.zip,
> publishedapi.zip
>
>
> While waiting for a Java module system (aka project Jigsaw), it has been
> decided to define a few subsets of the Java SE Platform Specification, cf JEP
> 161 ( http://openjdk.java.net/jeps/161).
> A quote from the JEP: "More broadly, this feature is intended to enable the
> migration of applications currently built on top of the Java ME Connected
> Device Configuration (CDC) to appropriate Profiles of the Java SE Platform,
> part of the long-term effort to converge CDC with Java SE."
> It would be good if we make Derby to run on such limited profiles. The
> current proposal places JDBC in Compact Profile 2 (cf. link above), while
> other libraries used by Derby, e.g. javax.naming (JNDI) are in Profile 3
> (larger).
> It would be good if Derby could run on the smallest posible platform, i.e.
> Profile 2, but that will probably involve some changes to make Derby
> gracefully limit functionality when some libraries are missing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
