[
https://jira.jboss.org/jira/browse/JBIDE-4093?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4093:
------------------------------------
The Publish to server button is an incremental publish and only alerts of what workspace
files have changed. A change to the deployment location will not be reflected in the
delta model being passed in to my publishers.
The server editor does not allow me to respond on "save" events, so my choices
here are basically to attempt to publish each time the user clicks on a radio, even if
they don't save (which is obviously very bad, deleting the old deployment and
publishing a new one somewhere else, even if the change isn't saveed), or let the user
do a full publish on their own.
I assume using a full publish here is not broken?
Project archive isn't published to the deploy folder after
changing temporary deploy directory.
-----------------------------------------------------------------------------------------------
Key: JBIDE-4093
URL:
https://jira.jboss.org/jira/browse/JBIDE-4093
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 3.1.0
Reporter: Anton Klimkovich
Assignee: Rob Stryker
Priority: Minor
EXECUTE: Create seam web project
EXECUTE: Open Server Overview
EXECUTE: Set checkbox to Use workspace metadata
EXECUTE: Add project to the server
ASSERT: Project is deployed to
\ws3\.metadata\.plugins\org.jboss.ide.eclipse.as.core\jboss-soa-p.4.3.0\deploy\
EXECUTE: Open Server Overview
EXECUTE: Set checkbox to Use a custom deploy folder or Use the JBoss deploy folder. Save
changes.
EXECUTE: Press Publish to the server button
FAILURE: Only seam-ds.xml is published. Seam.war isn't published to the deploy
folder.
--
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