[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4680) add conf-relative paths for default filesets
[
https://jira.jboss.org/jira/browse/JBIDE-4680?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4680:
--------------------------------------------
I don't understand....werent we talking about using eclipse variables to resolve the
directory ?
shouldn't it be something like ${jboss_config} for the current configuration name and
possibly ${jboss_config_dir} for the full path allowing it to be used other places where
eclipse variables are prsent ?
does ${jboss_config:My Server Name} work too ?
add conf-relative paths for default filesets
--------------------------------------------
Key: JBIDE-4680
URL: https://jira.jboss.org/jira/browse/JBIDE-4680
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.1.0.M2
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.1.0.M3
Attachments: JBIDE-4680.jpg, JBIDE-4680_2.jpg
Currently, relative paths are based on the getLocation() method of the runtime. For JBoss
servers, this means a relative path should be something like server/default/deploy.
The problem here is that the user may want to set up a default fileset relative to the
concrete configuration of that server's runtime.
Allow default filesets for jboss servers to have a relative path of
{config}/conf/jboss-log4j.xml. This path can be translated to
server/all/conf/jboss-log4j.xml when being added to the new server as a fileset.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira