[jbosstools-issues] [JBoss JIRA] (JBIDE-14549) Deploying archive via drag&drop triggers server start

[Jaroslav Jankovič (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-14549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778079#comment-12778079 ] 

Jaroslav Jankovič commented on JBIDE-14549:
-------------------------------------------

I added steps for both use cases. Hope it's sufficient
                
> Deploying archive via drag&drop triggers server start
> -----------------------------------------------------
>
>                 Key: JBIDE-14549
>                 URL: https://issues.jboss.org/browse/JBIDE-14549
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: archives
>    Affects Versions: 4.1.0.Beta1
>            Reporter: Jaroslav Jankovič
>            Assignee: Rob Stryker
>             Fix For: 4.1.1.Final
>
>
> If archive is deployed with Publish dialog, server is (correctly) not started. However, drag&drop archive under server in servers view cause server starting. 
> STEP: create a simple java project
> STEP: create an archive in it (via explorer/view)
> STEP: in Project Explorer view, expand Project Archives explorer, select the created archive and drag & drop into server in server's view
> ASSERT: archive is deployed on the server
> FAIL: server start is initiated but I think it should be not, because archive deploy via Publish Archive dialog doesn't trigger server's start
> There is another bug. When user wants to drag&drop whole project into the server, server's starting process is also initiated, but should be not.
> STEP: create a simple java project
> STEP: open Project Explorer view and drag & drop the project into a server
> ASSERT: project is deployed
> ASSERT: server is not started
> STEP: undeploy the project from a server
> STEP: create an archive in the project
> STEP: drag & drop the project into a server
> ASSERT: project is deployed
> FAIL: server's start is triggered

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira