[jbosstools-issues] [JBoss JIRA] Closed: (JBIDE-4365) Deployment in AS is failed, when server started.

[Yura Zhishko (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBIDE-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yura Zhishko closed JBIDE-4365.
-------------------------------



I've verified this issue on all later builds. I can't reproduce it too for now. Well I think that was a conflict of workspace from old Eclipse 3.5 M6 version with M7. So, closed.

> Deployment in AS is failed, when server started.
> ------------------------------------------------
>
>                 Key: JBIDE-4365
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4365
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.1.0.M1
>         Environment: jboss-eap 4.3
> jbdevstudio-eap-win32-2.1.0.M1-N200905190437-H189
>            Reporter: Yura Zhishko
>            Assignee: Rob Stryker
>            Priority: Critical
>         Attachments: screenshot-1.jpg
>
>
> 1) Run studio in new workspace
> 2) Create new JSF kickstart project with facelets using jboss-eap runtime
> 3) Run it on jboss-eap 4.3
> ASSERT: ALL is OK
> 4) Don't stop server
> 5) Create another new JSF kickstart project using jboss-eap runtime but do not add this project into server scope or delete it, if it happened.
> 6) Right mouse click on the project from point 4 in Package explorer -> Run on server -> jboss-eap -> Finish
> RESULT: Deployment is failed. Project didn't start. Publish function isn't available (see screenshot-1)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira