[jbosstools-issues] [JBoss JIRA] (JBIDE-7379) Importing / Exporting of AS servers ignore command line args, filesets, xpaths, and even runtimes

[Rob Stryker (JIRA)]

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

Rob Stryker updated JBIDE-7379:
-------------------------------

    Fix Version/s: 4.0.0.Alpha2
                       (was: 3.3.x)

    
> Importing / Exporting of AS servers ignore command line args, filesets, xpaths, and even runtimes
> -------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-7379
>                 URL: https://issues.jboss.org/browse/JBIDE-7379
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 3.2.0.Beta1
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 4.0.0.Alpha2
>
>
> Exporting of servers is incomplete. It does not export any saved filesets, xpaths, or custom launch configuration args. 
> Importing of servers is also incomplete, not importing any of these elements. Also, while the servers themselves are imported, sometimes their runtimes are not created at all, and you get a server with no runtime. This has been very hard to track down, but no runtimeAdded event is ever fired, and in our code it looks as if they're not even created or looked for. 
> This needs to be re-visited and tested extensively. I expect I will move import / export functionality into the AS plugin for now since hte o.j.t.runtime plugin already depends on AS. This will allow me to use classes already in the AS test suite for filesets and xpaths properly. I will keep the handler in the runtimes plugin but merely have it delegate to the functionality stored in the as plugin. 
> It currently seems to be saving only servers and not the runtimes. 

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