[
https://issues.apache.org/jira/browse/GERONIMO-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xiezhi updated GERONIMO-6112:
-----------------------------
Attachment: Deployer.java.patch
Have post another solution. I think it's better to solve this issue. Before
check the sum file, we can do some check if the deploy file is a car. If it is
a car, we should stop the deploy process, and tell the user the correct action.
> Sum file already exists
> -----------------------
>
> Key: GERONIMO-6112
> URL: https://issues.apache.org/jira/browse/GERONIMO-6112
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 3.0
> Reporter: Jarek Gawor
> Assignee: xiezhi
> Fix For: 3.0-beta-2
>
> Attachments: ConfigurationStoreUtil.java.patch, Deployer.java.patch
>
>
> Deploying a "car" module or module with the .ser and .sha1 files causes
> "Unable to deploy: java.io.IOException: Sum file already exists" error. Such
> modules shouldn't be deployed in the first place but some users do by mistake
> or whatever. Unfortunately, the error doesn't help in determining what's
> wrong. So I think we should either throw a nicer exception when this happens
> or suppress this error altogether and redeploy the module.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
