[DERBY-6945] Re-package Derby as a collection of jigsaw modules

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.15.1.3
• Fix Version/s: 10.15.1.3
• Component/s: Build tools
• Urgency: Blocker
• Issue & fix info: Release Note Needed
• Assignee: Richard N. Hillegas
• Reporter: Richard N. Hillegas
• Created: 02/Jul/17 16:39
• Updated: 25/Aug/21 14:27
• Resolved: 11/Dec/18 18:09

Description

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.

Issue Links

• is related to: DERBY-7039 DataSource classes removed from derby.jar
• is related to: DERBY-7097 Update documentation to allow users to properly use EmbeddedDriver
• is related to: DERBY-7016 Adjust the set*CP scripts to include derbyshared.jar and to set a MODULEPATH variable as well
• is related to: DERBY-7019 Failure in XMLBindingTest
• is related to: DERBY-7020 Fix release targets to account for modularization changes
• is related to: DERBY-6645 Switch to Maven for building Apache Derby
• is related to: DERBY-6995 Revamp the demo programs so that they can be run from the module path
• is related to: DERBY-7006 Investigate putting generated classes under the engine module loader
• is related to: DERBY-7012 Reduce the attack surface of the engine packages exposed by generated classes
• is related to: DERBY-7026 Update sysinfo example in the Tools Guide
• is related to: DERBY-7038 Upgrade ant version and re-write javadoc build targets to use improved <javadoc>task
• is related to: DERBY-7040 Add dependency stanzas to maven poms
• is related to: DERBY-7056 Make Derby modules usable by OSGi-aware applications
• is related to: DERBY-6980 Documentation changes to accompany jigsaw-modularization of derby
• is related to: DERBY-7021 Run the modulepath tests on Linux and Windows
• is related to: DERBY-7125 Dead link in BUILDING.html
• relates to: DERBY-6944 tomcat, maven, derby jar file manifest, jar naming
• relates to: DERBY-6856 Make it possible to build Derby using JDK 9
• relates to: DERBY-6980 Documentation changes to accompany jigsaw-modularization of derby
• relates to: DERBY-7018 Test the demo programs after the changes made by DERBY-6945