[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16307285#comment-16307285
]
Bryan Pendleton commented on DERBY-6945:
----------------------------------------
Thank you Rick, for the detailed and very useful progress report.
I really appreciate your time and effort, not just in doing the work, but in
helping us understand where we are and where we're going.
I think the source tree structure and jar layout, as you describe them, are
very clear and match my expectations precisely.
I think it's fundamentally hard for Derby to achieve all its goals
simultaneously, as they are very challenging goals and require a lot of very
careful design and implementation. I think it's one of the wonders of Derby
that it can fit so many needs so well.
>From my point of view, the primary aspects of Derby which appeal to me are:
- 100% pure Java implementation
- Rich and powerful, well-documented and well-tested database implementation
- Extraordinarily high-quality code, mature and reliable, and near-zero
administration
I've never once wanted to run Derby on a resource-constrained platform (e.g., a
mobile device or embedded system).
And since I use Derby for my own personal database projects, not for
applications that I deliver or publish, the new packaging and deployment model
is of little interest to me.
But I completely understand the appeal of these features to others, and I think
it's wonderful that Derby continues to work to achieve those goals.
So, thanks again for the as-always clear and comprehensible updates about your
work.
> 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: derby-6945-01-aa-remove_derbyPreBuild_dep.diff,
> derby-6945-02-ab-newDerbySharedJar.diff,
> derby-6945-02-ac-newDerbySharedJar.diff, derby-6945-03-aa-partitionTest.diff,
> derby-6945-04-aa-moveRunClass.diff,
> derby-6945-05-aa-removeRedundant_Attribute_SQLState.diff,
> derby-6945-06-aa-removeOtherSharedDuplicates.diff,
> derby-6945-07-aa-net_client_overlap.diff,
> derby-6945-08-aa-move_shared_iapi_under_shared.diff,
> derby-6945-08-ab-move_shared_iapi_under_shared.diff,
> derby-6945-08-ad-move_shared_iapi_under_shared.diff, 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)
