db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6160) Fixes needed to documentation topics on security policy permissions
Date Mon, 29 Apr 2013 15:04:16 GMT

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

Kim Haase updated DERBY-6160:

    Attachment: DERBY-6160-2.zip

Thanks to all -- I'm attaching DERBY-6160-2.diff, DERBY-6160-2.stat, and DERBY-6160-2.zip,
with the following changes:

M       src/adminguide/tadminnetservbasic.dita
M       src/adminguide/tadminnetservcustom.dita
M       src/devguide/rdevcsecure871422.dita
M       src/devguide/cdevbabejgjd.dita
M       src/devguide/rdevcsecure871406.dita
M       src/devguide/rdevcsecure871439.dita

I removed the derby.storage.jvmInstanceId permission from the files where it was mentioned
(and did some reformatting), on top of the previous changes.
> Fixes needed to documentation topics on security policy permissions
> -------------------------------------------------------------------
>                 Key: DERBY-6160
>                 URL: https://issues.apache.org/jira/browse/DERBY-6160
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions:,
>            Reporter: Kathey Marsden
>            Assignee: Kim Haase
>         Attachments: DERBY-6160-2.diff, DERBY-6160-2.stat, DERBY-6160-2.zip, DERBY-6160.diff,
DERBY-6160.stat, DERBY-6160.zip
> DERBY-5363 added a new required permission  RuntimePermission "accessUserInformation".
> This should be added to the developer guide information under granting permissions to
> https://builds.apache.org/job/Derby-docs/lastSuccessfulBuild/artifact/trunk/out/devguide/cdevbabejgjd.html
> I am not sure of the context under which it is required if it is just needed. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message