[jira] [Commented] (DERBY-6944) tomcat, maven, derby jar file manifest, jar naming

["Rick Hillegas (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070902#comment-16070902 ] 

Rick Hillegas commented on DERBY-6944:
--------------------------------------

The workaround would for your product to bundle the Derby jar files with the names which are scribbled into the manifest. This is how my current company uses maven. Derby pre-dates the popularity of maven. The storing of Derby jars in the maven artifactories, using maven's versioning system, happened long after Derby had been integrated into many applications. A change like this would break many existing Derby-powered applications.

The approach you propose may be considered if we revamp the artifacts we release. We may consider such a revamping when we refactor Derby into jigsaw (Java 9) modules.

> 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)