[
https://issues.apache.org/jira/browse/DERBY-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071708#comment-16071708
]
Rick Hillegas commented on DERBY-6944:
--------------------------------------
Hey Bryan,
Yes, I agree that this would widen the problem of jar file misconfiguration.
> tomcat, maven, derby jar file manifest, jar naming
> --------------------------------------------------
>
> Key: DERBY-6944
> URL: https://issues.apache.org/jira/browse/DERBY-6944
> Project: Derby
> Issue Type: Improvement
> Components: Localization
> Affects Versions: 10.5.3.0, 10.13.1.1
> Reporter: Martin Sillence
> Priority: Minor
>
> 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
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
