db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6944) tomcat, maven, derby jar file manifest, jar naming
Date Sun, 02 Jul 2017 16:03:02 GMT

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

Rick Hillegas commented on DERBY-6944:

We might be able to support legacy apps and more modern artifactory usage by scribbling a
longer classpath into the manifest. We could front-load the classpath with the artifactory
jar names (the ones which have a version number in them), followed by the old-style, unadorned
jar names. I think that the backward incompatibility issues would be minor enough and could
be handled with a release note.

What do people think?

> 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:,
>            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-
> 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

View raw message