[
https://issues.jboss.org/browse/JBIDE-15185?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-15185:
-------------------------------------
I don't think this is even possible without huge changes to all of our server
adapters. The home directory is stored as a runtime's "location" which WTP
requires to be an IPath. If it is even technically possible, this would require basically
every piece of code where we get the location from a runtime to (runtime.getLocation())
to then turn it into a string, then perform string substitution, etc..
This also means all classpath resolvers (which oftentimes cache project classpaths based
on the location of the runtime) now not only need to listen to runtime changes, but also
changes to the variable framework in eclipse, to know whether or not to clear their cache.
This type of feature only seems useful if the user intends to change the value of that
variable on occasion. However, we currently depend on the fact that changes to runtimes
are propagated via listeners to runtime objects for changes. If a change was accomplished
"under the hood" to the variable, which effectively changes the data of the
runtime but without any notification, all caches would be invalidated, but there would be
no notification of it.
Even though we're currently pondering a redesign of astools, I'm really not sure
this is even possible without overly-complicated workflows or too many moving pieces.
add flexibility that JBoss runttime server uses variables instead of
absolute path for the home directory.
----------------------------------------------------------------------------------------------------------
Key: JBIDE-15185
URL:
https://issues.jboss.org/browse/JBIDE-15185
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Reporter: Gary Hu
Fix For: 4.2.x
The current jbds version only allow users to specify an absolute path for "Home
Directory" when creating JBoss Runtime Server. Is it possible to use a user defined
variable here?
--
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