[JBoss JIRA] Created: (JBDS-1079) Referencing custom server config in subdir is not reflected in deploy and tmp directories
11:06 a.m.
Referencing custom server config in subdir is not reflected in deploy and tmp directories
-----------------------------------------------------------------------------------------
Key: JBDS-1079
URL: https://jira.jboss.org/jira/browse/JBDS-1079
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Affects Versions: 3.0.0.CR1
Reporter: Len DiMaggio
To recreate this issue:
1) Make a copy of the server profile into a subdirectory (for example, copy default into
/server/custom/mydefault)
2) Create a server in JBDS using this /server/custom/mydefault server
3) Observe the server's deploy and tmp directories - they will be created in
/server/mydefault
4) To workaround this - see the 3rd screenshot - intuitively, when the user references a
new custom server in a subdir, the deploy and tmp dirs would be in off the same subdir
--
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:08 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1079) Referencing custom server config in subdir is not reflected in deploy and tmp directories
[
https://jira.jboss.org/jira/browse/JBDS-1079?page=com.atlassian.jira.plug...
]
Len DiMaggio updated JBDS-1079:
-------------------------------
Attachment: jbds_custom1.png
jbds_custom2.png
jbds_custom3.png
Referencing custom server config in subdir is not reflected in deploy
and tmp directories
-----------------------------------------------------------------------------------------
Key: JBDS-1079
URL: https://jira.jboss.org/jira/browse/JBDS-1079
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Affects Versions: 3.0.0.CR1
Reporter: Len DiMaggio
Attachments: jbds_custom1.png, jbds_custom2.png, jbds_custom3.png
To recreate this issue:
1) Make a copy of the server profile into a subdirectory (for example, copy default into
/server/custom/mydefault)
2) Create a server in JBDS using this /server/custom/mydefault server
3) Observe the server's deploy and tmp directories - they will be created in
/server/mydefault
4) To workaround this - see the 3rd screenshot - intuitively, when the user references a
new custom server in a subdir, the deploy and tmp dirs would be in off the same subdir
--
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
5:09 a.m.
New subject: [JBoss JIRA] Moved: (JBIDE-5791) Referencing custom server config in subdir is not reflected in deploy and tmp directories
[
https://jira.jboss.org/jira/browse/JBIDE-5791?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen moved JBDS-1079 to JBIDE-5791:
--------------------------------------------------
Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer
Studio))
Key: JBIDE-5791 (was: JBDS-1079)
Affects Version/s: 3.1.0.CR2
(was: 3.0.0.CR1)
Referencing custom server config in subdir is not reflected in deploy
and tmp directories
-----------------------------------------------------------------------------------------
Key: JBIDE-5791
URL: https://jira.jboss.org/jira/browse/JBIDE-5791
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.CR2
Reporter: Len DiMaggio
Attachments: jbds_custom1.png, jbds_custom2.png, jbds_custom3.png
To recreate this issue:
1) Make a copy of the server profile into a subdirectory (for example, copy default into
/server/custom/mydefault)
2) Create a server in JBDS using this /server/custom/mydefault server
3) Observe the server's deploy and tmp directories - they will be created in
/server/mydefault
4) To workaround this - see the 3rd screenshot - intuitively, when the user references a
new custom server in a subdir, the deploy and tmp dirs would be in off the same subdir
--
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
5:11 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5791) Referencing custom server config in subdir is not reflected in deploy and tmp directories
[
https://jira.jboss.org/jira/browse/JBIDE-5791?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-5791:
---------------------------------------
Component/s: JBossAS
Fix Version/s: 3.1.0.CR2
Assignee: Rob Stryker
Priority: Critical (was: Major)
Moved to JBIDE since there is no JBDS specific in this issue.
Rob, looks like a rather annoying bug in the new copy/clone setup of configurations ?
Or is it just the ui being wrong calculating the default ?
Referencing custom server config in subdir is not reflected in deploy
and tmp directories
-----------------------------------------------------------------------------------------
Key: JBIDE-5791
URL: https://jira.jboss.org/jira/browse/JBIDE-5791
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR2
Reporter: Len DiMaggio
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.1.0.CR2
Attachments: jbds_custom1.png, jbds_custom2.png, jbds_custom3.png
To recreate this issue:
1) Make a copy of the server profile into a subdirectory (for example, copy default into
/server/custom/mydefault)
2) Create a server in JBDS using this /server/custom/mydefault server
3) Observe the server's deploy and tmp directories - they will be created in
/server/mydefault
4) To workaround this - see the 3rd screenshot - intuitively, when the user references a
new custom server in a subdir, the deploy and tmp dirs would be in off the same subdir
--
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
5:11 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5791) Referencing custom server config in subdir is not reflected in deploy and tmp directories
[
https://jira.jboss.org/jira/browse/JBIDE-5791?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-5791:
--------------------------------------------
I also thought we introduced variables to be able to have relative deploy locations ?
Referencing custom server config in subdir is not reflected in deploy
and tmp directories
-----------------------------------------------------------------------------------------
Key: JBIDE-5791
URL: https://jira.jboss.org/jira/browse/JBIDE-5791
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR2
Reporter: Len DiMaggio
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.1.0.CR2
Attachments: jbds_custom1.png, jbds_custom2.png, jbds_custom3.png
To recreate this issue:
1) Make a copy of the server profile into a subdirectory (for example, copy default into
/server/custom/mydefault)
2) Create a server in JBDS using this /server/custom/mydefault server
3) Observe the server's deploy and tmp directories - they will be created in
/server/mydefault
4) To workaround this - see the 3rd screenshot - intuitively, when the user references a
new custom server in a subdir, the deploy and tmp dirs would be in off the same subdir
--
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
8:27 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5791) Referencing custom server config in subdir is not reflected in deploy and tmp directories
[
https://jira.jboss.org/jira/browse/JBIDE-5791?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-5791:
------------------------------------
Um... the wizards and APIs are *not* set up at all to have more than 1 segment
configuration name. As you can see, he's browsing to server/custom and selecting
"MyDefault" as the configuration. This is saving "MyDefault" as the
configuration name.
After that, all calculations are going to server/config-name/deploy, so in this case,
thats server/MyDefault/deploy.
None of the APIs are able to handle a multiple-segment configuration "name".
This is not just a bug in the UI but rather not a supported usecase.
User should instead copy the configuration to server/MyDefault, rather than
server/custom/MyDefault
Referencing custom server config in subdir is not reflected in deploy
and tmp directories
-----------------------------------------------------------------------------------------
Key: JBIDE-5791
URL: https://jira.jboss.org/jira/browse/JBIDE-5791
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR2
Reporter: Len DiMaggio
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.1.0.CR2
Attachments: jbds_custom1.png, jbds_custom2.png, jbds_custom3.png
To recreate this issue:
1) Make a copy of the server profile into a subdirectory (for example, copy default into
/server/custom/mydefault)
2) Create a server in JBDS using this /server/custom/mydefault server
3) Observe the server's deploy and tmp directories - they will be created in
/server/mydefault
4) To workaround this - see the 3rd screenshot - intuitively, when the user references a
new custom server in a subdir, the deploy and tmp dirs would be in off the same subdir
--
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:57 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5791) Referencing custom server config in subdir is not reflected in deploy and tmp directories
[
https://jira.jboss.org/jira/browse/JBIDE-5791?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-5791:
--------------------------------------------
okey so could we at least check for this weird restriction in the wizard so users become
aware of this limitation instead of allowing them to do something that is not allowed ?
(dont have an eclipse on this box, but can't users actually point to any directory,
even one outside the AS ? That is a multisegment path ?)
Referencing custom server config in subdir is not reflected in deploy
and tmp directories
-----------------------------------------------------------------------------------------
Key: JBIDE-5791
URL: https://jira.jboss.org/jira/browse/JBIDE-5791
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR2
Reporter: Len DiMaggio
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.1.0.CR2
Attachments: jbds_custom1.png, jbds_custom2.png, jbds_custom3.png
To recreate this issue:
1) Make a copy of the server profile into a subdirectory (for example, copy default into
/server/custom/mydefault)
2) Create a server in JBDS using this /server/custom/mydefault server
3) Observe the server's deploy and tmp directories - they will be created in
/server/mydefault
4) To workaround this - see the 3rd screenshot - intuitively, when the user references a
new custom server in a subdir, the deploy and tmp dirs would be in off the same subdir
--
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
3:51 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-5791) Referencing custom server config in subdir is not reflected in deploy and tmp directories
[
https://jira.jboss.org/jira/browse/JBIDE-5791?page=com.atlassian.jira.plu...
]
Rob Stryker resolved JBIDE-5791.
--------------------------------
Resolution: Done
patched.
The underlying APIs were not using some new API when they should have, and the UI was
ignoring it in very specific cases.
Referencing custom server config in subdir is not reflected in deploy
and tmp directories
-----------------------------------------------------------------------------------------
Key: JBIDE-5791
URL: https://jira.jboss.org/jira/browse/JBIDE-5791
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR2
Reporter: Len DiMaggio
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.1.0.CR2
Attachments: jbds_custom1.png, jbds_custom2.png, jbds_custom3.png
To recreate this issue:
1) Make a copy of the server profile into a subdirectory (for example, copy default into
/server/custom/mydefault)
2) Create a server in JBDS using this /server/custom/mydefault server
3) Observe the server's deploy and tmp directories - they will be created in
/server/mydefault
4) To workaround this - see the 3rd screenshot - intuitively, when the user references a
new custom server in a subdir, the deploy and tmp dirs would be in off the same subdir
--
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
5910
days inactive
5924
days old
jbosstools-issues@lists.jboss.org
7 comments
3 participants
participants (3)
-
Len DiMaggio (JIRA) -
Max Rydahl Andersen (JIRA)
-
Rob Stryker (JIRA)