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

Rob Stryker (JIRA) jira-events at lists.jboss.org
Fri Jul 31 17:29:42 EDT 2009


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

Rob Stryker resolved JBIDE-4680.
--------------------------------

    Resolution: Done


This was a tough thing to figure out. Just making a global dynamic variable for ${jboss_config} would not be possible as I'd not know which server to use it.

If I change it when adding the default fileset to a new fileset, then I'd have to replace ${jboss_config} with ${jboss_config:Some Server Name}, but that'd be bad as now if the user renames the server, the server's own filesets don't work. 

Instead, I have the fileset itself change ${jboss_config} into ${jboss_config:Some Server Name} in the getFolder() method, so teh filesets persist ${jboss_config} and do not persist the server name. However I still feel this is a bit cludgy and gives preference / special treatment to these particular variables. 

Either way, it works, it's clean, and it's committed ;) 

> 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

        


More information about the jbosstools-issues mailing list