This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Product Version: NetBeans IDE Dev (Build 200808041401) Java: 1.5.0_15; Java HotSpot(TM) Client VM 1.5.0_15-b04 System: Linux version 2.6.24-19-generic running on i386; UTF-8; en_US (nb) Userdir: /home/tester/.netbeans/dev I have created a new web application (and after that a new enterprise application) and I successfully deployed it on the JBoss 5.0.0.CR1 server. However, it is not possible to undeploy the application, as there is no popup menu for it. See the screenshot.
Created attachment 66615 [details] screenshot
Sorry for a little confusion - enterprise application was not deployed (#142959), here it is not possible to undeploy the war belonging to enterprise application. Which is still only a web application, so this issue concerns web applications only...
It is disabled - we can't get list of deployed apps so we can even reliably undeploy one.
Typo ...can't even reliably undeploy...
I doubt this can be fixed unless https://jira.jboss.org/jira/browse/JBAS-4078 is fixed. Afaik only option for 6.5 is to waive it or decrease priority.
Probably, the issue is P3 since there is no pop-um menu item and the workaround is delete the war on JBoss deployment directory. Also, I don't believe the JBoss issue will be resolved soon (the report was created on 07/Feb/07).
Ok, Petr is right. The issue is not preventing user from development work and the simple workaround exists.
I think it can be P3, but I think we could somehow notify user that "JBoss 5" and "JBoss 5 NB Suport" are in beta/experimental/disastrous/... stage and some important common actions won't be available through NB IDE for this reason... I think we could for example explicitly say (in "Add Server Instance" dialog) that we support "JBoss Application server 4 (and older?)" and then that we support "JBoss 5 AS (experimental)"... Just to let user know that there are some issues that might surprise him... ;)
I think that this bug doesn't degrade JBoss plugin to Beta Quality. I would suggest to mention the bug in know issues document for NB 6.5 and also provide the workaround there.
This can't be reliably fixed for 6.5, TM -> future.
The Jboss bug mentioned above which this issue depends on is still in OPEN state. Unless JBoss fixes the bug, this issue can not be resolved. Marking this issue LATER
NetBeans.org Migration: changing resolution from LATER to WONTFIX