Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <12058531.1149972930604.JavaMail.jira@brutus>
Date: Sat, 10 Jun 2006 20:55:30 +0000 (GMT+00:00)
From: "Kevan Miller (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Assigned: (GERONIMO-2101) Deployment failures prevent future
 deployments
In-Reply-To: <19009950.1149909629775.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/GERONIMO-2101?page=all ]

Kevan Miller reassigned GERONIMO-2101:
--------------------------------------

    Assign To: Kevan Miller

> Deployment failures prevent future deployments
> ----------------------------------------------
>
>          Key: GERONIMO-2101
>          URL: http://issues.apache.org/jira/browse/GERONIMO-2101
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: deployment
>     Versions: 1.1
>     Reporter: Aaron Mulder
>     Assignee: Kevan Miller
>     Priority: Blocker
>      Fix For: 1.1
>  Attachments: 2101-deployer-cleanup.patch
>
> If you deploy and there's an error, the next deploy attempt invariably gets:
>     Error: Unable to distribute foo-1.0.jar:
>     org.apache.geronimo.kernel.config.ConfigurationAlreadyExistsException:
>     Configuration already exists: bar/foo/1.0/car
> In other words, the bad deployment was written into the repository but not deleted when the deployment failed, and is now blocking future deployments.  The only solution seems to be to manually delete the offending directory from the repository.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira