[jbosstools-issues] [JBoss JIRA] Reopened: (JBIDE-4680) add conf-relative paths for default filesets

[Rob Stryker (JIRA)]

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

Rob Stryker reopened JBIDE-4680:
--------------------------------



further changes made here. 

Now, instead of typing {config}/conf/jboss-log4j.xml,   you would type:

server/${config}/conf/jboss-log4j.xml

This also persists the variable in the server's version of the fileset rather than translating at server creation. This allows the user to modify the runtime's configuration and not have to manually update paths. 

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