[jbosstools-issues] [JBoss JIRA] (JBIDE-17118) Errors when deploying to local servers using management api using Run on Server on project

[Rob Stryker (JIRA)]

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

Rob Stryker resolved JBIDE-17118.
---------------------------------

    Resolution: Done


This has been fixed. Simply switching the API used to one that simply gets the output name, rather than an entire output location and then it's last segment, worked. 

Servers in management publish mode cannot have a full deploy path; only a name. 
                
> Errors when deploying to local servers using management api using Run on Server on project
> ------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-17118
>                 URL: https://issues.jboss.org/browse/JBIDE-17118
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.0.Beta1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>            Priority: Critical
>             Fix For: 4.2.0.Beta2
>
>
> When you try to deploy an app to as7/wf8/eap6 using a server with management enabled, the app deploys, but you get some errors in the error log:
> {code}
> !ENTRY org.jboss.ide.eclipse.as.wtp.core 4 0 2014-04-15 17:35:59.050
> !MESSAGE Unable to choose a subsystem. Multiple subsystems found for servertype org.jboss.ide.eclipse.as.71 and system type deploymentOptions
> !ENTRY org.jboss.ide.eclipse.as.wtp.core 4 0 2014-04-15 17:35:59.050
> !MESSAGE Unable to choose a subsystem. Multiple subsystems found for servertype org.jboss.ide.eclipse.as.71 and system type deploymentOptions
> {code}
> When you then remove the deployment from the server view, it stays deployed. So you cannot get rid of it from Eclipse anymore - you have to either use web console, or jboss cli.

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