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

ASF subversion and git services commented on DERBY-6217:
--------------------------------------------------------

Commit 1596037 from [~chaase3] in branch 'docs/trunk'
[ https://svn.apache.org/r1596037 ]

DERBY-6217  Put all of the security documentation in a single, separate user 
guide

Added files for new security guide, consisting of 98 topics, 12 graphics files 
(3 for each illustration), and a map file. Also modified build.xml to create 
targets for this manual.

Also modifies docs.properties, which seems not to have been updated yet for 
copyright year, release.id.short, and minimum.jdk.

Patches: DERBY-6217-2.diff (files for guide), DERBY-6217-3.diff (build.xml)

> Put all of the security documentation in a single, separate user guide
> ----------------------------------------------------------------------
>
>                 Key: DERBY-6217
>                 URL: https://issues.apache.org/jira/browse/DERBY-6217
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.11.0.0
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
>         Attachments: DERBY-6217-2.diff, DERBY-6217-3.diff, DERBY-6217.diff, 
> DERBY-6217.stat, DERBY-6217.zip
>
>
> Right now the security documentation is divided among our user guides. This 
> makes is hard for customers to understand Derby's defenses and how to 
> configure all relevant security mechanisms for an application. As 
> demonstrated by the discussion on DERBY-6160, some security mechanisms 
> involve multiple Derby jar files and multiple application tiers. Material for 
> these mechanisms is scattered across the existing user guides. It would be 
> less confusing if all of Derby's security documentation were separated out 
> into a new Security Guide.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to