[DERBY-6944] tomcat, maven, derby jar file manifest, jar naming

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.5.3.0, 10.13.1.1
• Component/s: Localization
• Assignee: Unassigned
• Reporter: Martin Sillence
• Created: 30/Jun/17 15:02
• Updated: 04/Jul/17 18:43

Description

The main derby jar file has a manifest with a classpath entry e.g.

Class-Path: derbyLocale_cs.jar derbyLocale_de_DE.jar...

When using maven repository it downloads the files with the version numbers in it:

derbyLocale_cs-10.5.3.0_1.jar

if deployed on a recent version of tomcat the manifest it automatically interrogated and tomcat attempts to load the jar files as named. This fails as the names do not match.
Also the additional files are not specified as dependencies in the derby pom.xml file so they are not automatically retrieved.

Please would you consider adding in the dependencies to the published files and putting in the version in the names in the manifest when publishing to maven?

Workarounds:
fetch maven dependencies with "-Dmdep.stripVersion=true"
Turn off auto loading of manifest classpath for all files
add: <JarScanner scanManifest="false"/>
to tomcats context.xml

Issue Links

• is related to: DERBY-6945 Re-package Derby as a collection of jigsaw modules