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

[Rob Stryker (JIRA)]

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

Rob Stryker updated JBIDE-14549:
--------------------------------

    Fix Version/s: 4.1.1.Final
                       (was: 4.1.0.Beta2)


Drag and drop will try either a simple publish if possible (ie, if the node is adaptable to both an IProject and has modules registered for it), and if not, it will attempt a run-on-server action, which involves a publish but also involves starting the server and trying to load a web browser or other relevant client to show to the user. 

So for example if you drag and drop a servlet file, it will attempt to run it on the server. 

In the case of a plain old java project containing project archives, the root itself is converible to a project and does have a module in it, so only a publish should be initiated. My tests demonstrate this to be correct. 


Can you be more specific what exactly you are dragging and dropping, what node, from what view? Please list the use-cases separately as I'm a little confused.

Either way, I'm marking this for 4.1.x. 
                
> 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. 
> 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.

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