[jbosstools-issues] [JBoss JIRA] (JBIDE-13208) Allow custom 'standalone' mode directory in AS7 server plugin

[Rob Stryker (JIRA)]

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

Rob Stryker resolved JBIDE-13208.
---------------------------------

    Resolution: Done


> why not make all the various system properties base, configuration etc. part of the API instead of just adding it for base dir 

It would not make sense to add all of those without also adding UI for each of these elements. As we usually discuss all of these options already being too cluttered, I decided to mimic the existing UI for AS < 7.  So yes, there were UI additions, but they simply make hte AS7 wizard fragment look more similar to the AS < 7 fragment (being able to set more than just the configuration xml). 

This was hte easiest fix that makes the various UIs all match up, without having to completely re-envision the UI for options.  We already have an existing UI for cleaning up the options, but two potential UI changes were both rejected, leaving me a bit stuck for additional ways to hide the data but still expose all options.  Any future attempts to expose more config options would depend on a cleanup of the UI first. Otherwise it will just be clutter. 

>  Was this done without zero effects anywhere ? no need for migration of data ? no need to add things to UI ? 

As said above, a UI element was added to the AS7 wizard fragment, but there is no requirement to migrate any data at all.  XPaths used to locate port, etc, on older servers, are specifically not migrated, and will continue to use standalone directly. I decided not to migrate the xpaths because users have the ability to modify the xpath they wish to use, and there is no clear way for me to know whether hte user has customized their xpaths or not.  In absence of any clear way to determine if the xpaths were modified,  only new servers will benefit from the {config_dir} variable. 
                
> Allow custom 'standalone' mode directory in AS7 server plugin
> -------------------------------------------------------------
>
>                 Key: JBIDE-13208
>                 URL: https://issues.jboss.org/browse/JBIDE-13208
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: server
>         Environment: Mac OS-X 10.8.2, Java 6, Java 7, JBoss AS 7.x, JBoss EAP 6, JBDS 5.0.1
>            Reporter: Duncan Doyle
>            Assignee: Rob Stryker
>              Labels: f2f2012, new_and_noteworthy
>             Fix For: 4.2.0.Alpha1
>
>
> As with JBoss EAP5.x, I have the habit of working in a copy of a 'profile' directory. With JBoss AS7/EAP6 I therefore work in copies of 'standalone' and 'domain' (depending on the operational mode). When I start AS/EAP, I reference the correct server directory with the 'jboss.server.base.dir' or 'jboss.domain.base.dir' system property. This allows me, among other things, to run multiple AS/EAP instances from a single JBoss AS/EAP installation.
> It seems that the JBDS AS7 plugin only allows me to reference the default 'standalone' directory. I'm not able to select a different directory in the 'JBoss Runtime' configuration screen. I would propose to add the possibility to start a JBoss AS7/EAP6 instance from a different directory than 'standalone'.

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