You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Kevan Miller (JIRA)" <de...@geronimo.apache.org> on 2006/06/11 01:50:30 UTC

[jira] Resolved: (GERONIMO-2101) Deployment failures prevent future deployments

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

    Resolution: Fixed

Repository directory was created, but not deleted if an error occurred during deployment. 

Fix applied to branches/1.1 (413386) and trunk (413387).

> 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