[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-4680) add conf-relative paths for default filesets
Rob Stryker (JIRA)
jira-events at lists.jboss.org
Wed Jul 29 15:41:29 EDT 2009
[ https://jira.jboss.org/jira/browse/JBIDE-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Stryker updated JBIDE-4680:
-------------------------------
Attachment: JBIDE-4680.jpg
User is expected to type in {config}/conf/ if that's what they want.
The browse button will continue to always return absolute paths sinec these are default filesets, there's no way for browse to return a relative path. We don't have a concrete server we're building these against.
In this case (in the image), teh final server would have a fileset who's root directory is persisted as server/all/conf rather than {config}/conf.
> 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
More information about the jbosstools-issues
mailing list