Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 19 May 2014 17:18:38 +0000 (UTC)
From: "Kim Haase (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12646654.1368032631844.4147.1400519918554@arcas>
In-Reply-To: <JIRA.12646654.1368032631844@arcas>
References: <JIRA.12646654.1368032631844@arcas>
Subject: [jira] [Commented] (DERBY-6217) Put all of the security
 documentation in a single, separate user guide
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kim Haase commented on DERBY-6217:
----------------------------------

Thanks, Rick! I'm glad it's good enough to commit. We can of course make changes and additions.

I'm having trouble with the commit -- Subversion is choking on the 4 .eps files. The .gif and .jpg files all have the svn:mime-type property application/octet-stream, but the .eps files have no properties set (here or elsewhere), so they are assumed to be text. The graphics all date from time immemorial, so I've never had to add any before. 

Would it make sense to give them an svn:mime-type property of application/eps and revise the patch?

> 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.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)