[
https://issues.apache.org/jira/browse/DERBY-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16073524#comment-16073524
]
Martin Sillence commented on DERBY-6944:
----------------------------------------
What about just taking them all out - leaving it the the person that packages
it to add them in if they want them?
And yes the problem is tomcat won't load my application if the manifest
includes files that are not present - a touch more problematic than grumbling
I raised this mainly as I expect others will have this problem.
> 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)
