geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim McConnell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMODEVTOOLS-337) Configuration already exists exception
Date Sun, 04 May 2008 14:50:55 GMT

    [ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594096#action_12594096
] 

Tim McConnell commented on GERONIMODEVTOOLS-337:
------------------------------------------------

Part of a larger problem where the server and Eclipse get out of sync, and is most prevalent
when exceptions occur, although not exclusively. Need a good use case for replicating the
problem, and a better solution for keeping the GEP and the server in sync.

> Configuration already exists exception
> --------------------------------------
>
>                 Key: GERONIMODEVTOOLS-337
>                 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-337
>             Project: Geronimo-Devtools
>          Issue Type: Bug
>          Components: eclipse-plugin
>    Affects Versions: 2.1.0
>            Reporter: Tim McConnell
>            Assignee: Tim McConnell
>             Fix For: 2.1.1
>
>
> Periodically the tooling will receive a deployment exception (configuration already exists)
when publishing updates. The user must remove the projects, manually delete from the repository,
and then re-add/re-publish. Occasionally, you must restart both the tooling and the runtime
in order to delete from repository.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message