[
https://issues.jboss.org/browse/JBIDE-10045?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-10045:
--------------------------------
Attachment: JBIDE-10045.patch
patch to fix issue. This patch also fixes the case where a properly synchronized module
gets transitioned to state Republish after a simple run as -> run on server, which
should not be happening.
Incremental Publish forcing a push request for openshift when it
should not.
-----------------------------------------------------------------------------
Key: JBIDE-10045
URL:
https://issues.jboss.org/browse/JBIDE-10045
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.M4
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.3.0.M4, 3.3.0.Beta1
Attachments: JBIDE-10045.patch
Every attempt to run as -> run on server creates a publish request, though if no
changes have been made it's an incremental request. In the case where there are no
changes in the workspace, the request to push is still being initiated even for these
incremental publishes. Bad.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira