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 DDE60D45D for ; Tue, 15 Jan 2013 21:18:14 +0000 (UTC) Received: (qmail 70785 invoked by uid 500); 15 Jan 2013 21:18:13 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 70724 invoked by uid 500); 15 Jan 2013 21:18:13 -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 70588 invoked by uid 99); 15 Jan 2013 21:18:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Jan 2013 21:18:13 +0000 Date: Tue, 15 Jan 2013 21:18:13 +0000 (UTC) From: "Saminda Wijeratne (JIRA)" To: dev@airavata.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AIRAVATA-726) Generate a WAR distribution for Airavata Server at build time MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Saminda Wijeratne created AIRAVATA-726: ------------------------------------------ Summary: Generate a WAR distribution for Airavata Server at build time Key: AIRAVATA-726 URL: https://issues.apache.org/jira/browse/AIRAVATA-726 Project: Airavata Issue Type: Task Reporter: Saminda Wijeratne Assignee: Saminda Wijeratne One of the most common use cases of Airavata Server is to run it inside a web container of a existing tomcat. Currently users have to manually copy content from the airavata-server binary distribution to create a web app for airavata server that can be deployed inside an existing tomcat. We should simplify this process by distributing a WAR file... -- 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