[jbosstools-issues] [JBoss JIRA] (JBIDE-2899) Allow export of server definitions without resetting launch config

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen resolved JBIDE-2899.
----------------------------------------

    Resolution: Out of Date


Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).

If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.

Thank you!


                
> Allow export of server definitions without resetting launch config
> ------------------------------------------------------------------
>
>                 Key: JBIDE-2899
>                 URL: https://issues.jboss.org/browse/JBIDE-2899
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: server
>    Affects Versions: 3.0.0.alpha
>            Reporter: Gabriele Garuglieri
>            Assignee: Rob Stryker
>            Priority: Minor
>             Fix For: LATER
>
>
> Currently we can export a JBoss Tools server definition using the default WTP server panel. 
> There right clicking on the server opens a context menu whose last item is "Properties".
> Clicking it opens a panel where the "Switch Location" button cause the server definition to be exported from workspace metadata to "Servers" project.
> The problem is that doing so resets the launch configuration to the default values loosing any customization the user could have done.
> The "Switch Location" function for JBoss Tools server definition should not loose launch config customizations.
> (This is not strictly related but while you are at it,  in the "Export Launch Configurations" panel the "JBoss Application Server Startup Configurations" items are missing the icons).

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