You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Shiva Kumar H R (JIRA)" <ji...@apache.org> on 2008/04/04 20:35:24 UTC
[jira] Closed: (GERONIMODEVTOOLS-322) Undeploying an EAR doesn't
actually remove it from server
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shiva Kumar H R closed GERONIMODEVTOOLS-322.
--------------------------------------------
Resolution: Fixed
> Undeploying an EAR doesn't actually remove it from server
> ---------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-322
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-322
> Project: Geronimo-Devtools
> Issue Type: Bug
> Components: eclipse-plugin
> Affects Versions: 2.1.0
> Reporter: Shiva Kumar H R
> Assignee: Shiva Kumar H R
> Priority: Critical
> Fix For: 2.1.0
>
>
> Steps to recreate:
> 1) Create a Dynamic Web Project and an EJB project. Then create an Enterprise Application Project (EAR) with the web & ejb projects added as its modules.
> 2) Now deploy the EAR from within GEP. Observe from Admin Console that EAR is in fact deployed onto server.
> 3) Now undeploy the EAR from within GEP. Although GEP shows the EAR as removed from server, observing from Admin Console shows that EAR is not at all undeployed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.