[
https://issues.jboss.org/browse/JBIDE-9334?page=com.atlassian.jira.plugin...
]
Martin Malina commented on JBIDE-9334:
--------------------------------------
@Andre: re your first comment with screenshots: if I create the remote server, then I see
the problem (metadata selected, even if grey). When I change it to local, it's still
using metadata. When I then change to Remote, deployment is changed to Use the JBoss
deploy folder.
If I create a local server and change it to Remote later, it is switched to Use the JBoss
deploy folder correctly. So really in most cases it works correctly. Only in that one
scenario I get the wrong configuration.
Cannot publish to remote EAP 5.1
--------------------------------
Key: JBIDE-9334
URL:
https://issues.jboss.org/browse/JBIDE-9334
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M2
Environment: Mac OS X 10.6 Snow Leopard
Reporter: Martin Malina
Assignee: Martin Malina
Fix For: 3.3.0.M3
Attachments: deploy-folder.png, errorMsg.jpg, metadataWithRSE.jpg, overview.png
Scenario:
1. Start JBT with a fresh workspace
2. Create a simple dynamic web project
3. Add a local EAP 5.1 server runtime + server adapter
4. Add a remote EAP 5.1 server adapter
5. Start the remote server
6. An error message will pop up
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira