Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 26 Nov 2012 17:48:58 +0000 (UTC)
From: "Mamta A. Satoor (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <1200717037.23578.1353952138632.JavaMail.jiratomcat@arcas>
In-Reply-To: <310737968.117173.1352941932538.JavaMail.jiratomcat@arcas>
Subject: [jira] [Resolved] (DERBY-5995) Add a test case to check the 3
 readme files get created even when log directory has been changed with jdbc
 url attribute logDevice
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mamta A. Satoor resolved DERBY-5995.
------------------------------------

          Resolution: Fixed
       Fix Version/s: 10.10.0.0
    Issue & fix info:   (was: Patch Available)
    
> Add a test case to check the 3 readme files get created even when log directory has been changed with jdbc url attribute logDevice
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5995
>                 URL: https://issues.apache.org/jira/browse/DERBY-5995
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 10.10.0.0
>            Reporter: Mamta A. Satoor
>            Assignee: Mamta A. Satoor
>             Fix For: 10.10.0.0
>
>         Attachments: DERBY5995_patch1_diff.txt, DERBY5995_patch1_stat.txt
>
>
> DERBY-5322 added three 3 readme files to database which warn users against touching any files in the database directory. In this jira, test that the three readme files still get properly created even when log directory has been set to a non-default location using logDevice attribute on jdbc url.

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