db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3269) Investigate issues with renaming jars for maven deployment
Date Mon, 10 Dec 2007 19:01:55 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550152

Daniel John Debrunner commented on DERBY-3269:

I would guess that renaming the jars using a script is the wrong thing to do.

Maven has an install command that takes a version number, probably that should be used. No
idea though if it handles fixing up any manifest files.

> Investigate issues with renaming jars for maven deployment
> ----------------------------------------------------------
>                 Key: DERBY-3269
>                 URL: https://issues.apache.org/jira/browse/DERBY-3269
>             Project: Derby
>          Issue Type: Task
>          Components: Build tools
>    Affects Versions:,
>            Reporter: Kathey Marsden
> The instructions at http://wiki.apache.org/db-derby/DerbySnapshotOrRelease cover maven
deployment which includes renaming the derby jar files.  We know this causes an issue with
the default security manager DERBY-3120, but may cause other issues as well because of manifest
entries, for example with derbyrun, or automatic loading of localization files.
> We should at least document issues and at best fix our maven deployment to account for
the name change.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message