geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shiva Kumar H R (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMODEVTOOLS-322) Undeploying an EAR doesn't actually remove it from server
Date Fri, 04 Apr 2008 18:17:24 GMT

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

Shiva Kumar H R commented on GERONIMODEVTOOLS-322:
--------------------------------------------------

Completed: At revision: 644807  

> 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.


Mime
View raw message