Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DEB75D80C for ; Fri, 14 Dec 2012 20:32:12 +0000 (UTC) Received: (qmail 93352 invoked by uid 500); 14 Dec 2012 20:32:12 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 93308 invoked by uid 500); 14 Dec 2012 20:32:12 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 93299 invoked by uid 99); 14 Dec 2012 20:32:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Dec 2012 20:32:12 +0000 Date: Fri, 14 Dec 2012 20:32:12 +0000 (UTC) From: "Lahiru Gunathilake (JIRA)" To: dev@airavata.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AIRAVATA-673) Create Security Test Tables on the fly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AIRAVATA-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake resolved AIRAVATA-673. ----------------------------------------- Resolution: Fixed Applied the patch and thanks Amila for the contribution. Lahiru > Create Security Test Tables on the fly > -------------------------------------- > > Key: AIRAVATA-673 > URL: https://issues.apache.org/jira/browse/AIRAVATA-673 > Project: Airavata > Issue Type: Bug > Reporter: Suresh Marru > Attachments: 673.diff > > > The database bundled with security tests throw exception. It will be nice if the derby tables are created on the fly as we do for messenger and registry. -- 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