[
https://jira.jboss.org/browse/JBIDE-6286?page=com.atlassian.jira.plugin.s...
]
Rob Stryker resolved JBIDE-6286.
--------------------------------
Fix Version/s: (was: 3.2.x)
Resolution: Rejected
This is not actually a bug at all and in fact WTP is referring to something completely
different than deploy location of the modules. WTP keeps a small .server file to keep all
the attributes of the tooling server object. These are things such as id, server type,
launch configuration, etc. WTP can store this as a .server file in the workspace metadata,
or it can store it in the Servers project in the main workspace.
This cannot be changed by us and really we have no reason to care where they keep this
small server file.
Inconsistent deploy folder in server setting
--------------------------------------------
Key: JBIDE-6286
URL:
https://jira.jboss.org/browse/JBIDE-6286
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.GA
Environment: JBT 3.1.0 GA, JDK 1.6
Reporter: Jiri Peterka
Assignee: Rob Stryker
Attachments: custom-deploy-dir.png, metadata-deploy-dir.png
When there is selected custom deploy folder on Runtime Server properties -> Deployment
tab, in server properties there is still metedata (see screenshots)
Steps:
1. Add Jboss Runtime and create server
2. Click on Server in Servers view
3. On Deployment tab switch to "Use Custom deploy folder"
4. Save setting
5. Click on Servers view
6. Click on Server -> Properties (context menu)
7. See there is metadata dir set as location
ASSERT: Should be custom
ASSERT2: It should be possible to use "Switch Location" to switch location to
custom folder
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira