[ https://issues.jboss.org/browse/JBIDE-13208?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-13208. --------------------------------- Resolution: Done 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. 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. -- 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