9:37 p.m.
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
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
9:41 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4680) add conf-relative paths for default filesets
[
https://jira.jboss.org/jira/browse/JBIDE-4680?page=com.atlassian.jira.plu...
]
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
9:48 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-4680) add conf-relative paths for default filesets
[
https://jira.jboss.org/jira/browse/JBIDE-4680?page=com.atlassian.jira.plu...
]
Rob Stryker resolved JBIDE-4680.
--------------------------------
Resolution: Done
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
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
11:24 p.m.
New subject: [JBoss JIRA] Reopened: (JBIDE-4680) add conf-relative paths for default filesets
[
https://jira.jboss.org/jira/browse/JBIDE-4680?page=com.atlassian.jira.plu...
]
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
11:24 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-4680) add conf-relative paths for default filesets
[
https://jira.jboss.org/jira/browse/JBIDE-4680?page=com.atlassian.jira.plu...
]
Rob Stryker resolved JBIDE-4680.
--------------------------------
Resolution: Done
in the future perhaps support for all static variables
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
11:26 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4680) add conf-relative paths for default filesets
[
https://jira.jboss.org/jira/browse/JBIDE-4680?page=com.atlassian.jira.plu...
]
Rob Stryker updated JBIDE-4680:
-------------------------------
Attachment: JBIDE-4680_2.jpg
new pic
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
11:44 p.m.
New subject: [JBoss JIRA] Reopened: (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 reopened JBIDE-4680:
----------------------------------------
reopen for clarification...
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
11:46 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-4680) add conf-relative paths for default filesets
[
https://jira.jboss.org/jira/browse/JBIDE-4680?page=com.atlassian.jira.plu...
]
Rob Stryker resolved JBIDE-4680.
--------------------------------
Resolution: Done
done
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
11:48 p.m.
New subject: [JBoss JIRA] Reopened: (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 reopened JBIDE-4680:
----------------------------------------
reopen since we collided in midair ;)
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
11:48 p.m.
New subject: [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
10:30 p.m.
New subject: [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...
]
Rob Stryker commented on JBIDE-4680:
------------------------------------
Well... I can do that... but then, if the user changes the server name... the variable is
then hardcoded as ${jboss_config:My Server Name} even though the name's been changed
;) But this probably seems better than not using eclipse's substitution engine
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
11:29 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-4680) add conf-relative paths for default filesets
[
https://jira.jboss.org/jira/browse/JBIDE-4680?page=com.atlassian.jira.plu...
]
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
12:34 a.m.
New subject: [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:
--------------------------------------------
In case of the configuration path you would just use jboss_config with no parameters and
just use it from the current context.
The use of the specific username is more relevant for when users want to launch programs
that needs the config directory - i.e. to tell junit tests that runs with the upcoming
embedded. WDYT ?
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
12:37 a.m.
New subject: [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:
--------------------------------------------
hmm - I thought I saw once that you could setup a context for eclipse string variable
replacement but I don't seem be able to find that now ,(
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
11:38 a.m.
New subject: [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:
--------------------------------------------
sucks that eclipse variable replacement doesn't have a "context" to use.
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
5438
days inactive
5444
days old
jbosstools-issues@lists.jboss.org
14 comments
2 participants
participants (2)
-
Max Rydahl Andersen (JIRA) -
Rob Stryker (JIRA)