Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 30477 invoked from network); 27 Nov 2004 00:55:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 27 Nov 2004 00:55:29 -0000 Received: (qmail 90319 invoked by uid 500); 27 Nov 2004 00:55:22 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 90284 invoked by uid 500); 27 Nov 2004 00:55:21 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@geronimo.apache.org Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 90270 invoked by uid 99); 27 Nov 2004 00:55:21 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from exchange.sun.com (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.28) with SMTP; Fri, 26 Nov 2004 16:55:20 -0800 Received: (qmail 20764 invoked from network); 27 Nov 2004 00:55:18 -0000 Received: from localhost (HELO nagoya) (127.0.0.1) by nagoya.betaversion.org with SMTP; 27 Nov 2004 00:55:18 -0000 Message-ID: <2047311484.1101516918759.JavaMail.apache@nagoya> Date: Fri, 26 Nov 2004 16:55:18 -0800 (PST) From: "Gianny DAMOUR (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Created: (GERONIMO-504) dependencies defined by plan are not "validated" Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N dependencies defined by plan are not "validated" ------------------------------------------------ Key: GERONIMO-504 URL: http://nagoya.apache.org/jira/browse/GERONIMO-504 Project: Apache Geronimo Type: Wish Components: deployment Versions: 1.0-M3, 1.0-M2, 1.0-M1 Reporter: Gianny DAMOUR Priority: Minor elements defined by the various deployment plans are not validated. It is possible to deploy successfully plans defining dependencies, which are not defined by the installed repositories. When such configurations are started, the Kernel throws as expected a MissingDependencyException identifying the missing dependency. This should be done upfront during deployment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira