You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2010/05/03 21:45:57 UTC

[jira] Updated: (DERBY-3269) Investigate issues with renaming jars for maven deployment

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

Rick Hillegas updated DERBY-3269:
---------------------------------

    Labels: releaseGeneration  (was: )

> 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: 10.3.2.1, 10.4.1.3
>            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.