[
https://issues.jboss.org/browse/JBIDE-11254?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-11254.
---------------------------------
Resolution: Done
Because the zipping utility used java.io.file api, a refresh of the folder was needed
before executing the git add operation. This has been fixed
when dragging binary war to project it starts pushing before the
binary is ready
--------------------------------------------------------------------------------
Key: JBIDE-11254
URL:
https://issues.jboss.org/browse/JBIDE-11254
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Fix For: 3.3.0.CR1
have an openshift app + a standard war.
Drag the standar war to the server.
You will be asked if you to publish to the server *before* the binary module have been
fully built/added.
End result is that when you say yes to publish it will actually not have the war remotely
available.
Expected: that it does not ask nor do deployment before its children have been
published.
See workflow here (
http://screencast.com/t/ZSJIoSMkDqj) - in the video I say no to the
publish dialog, but If I had pressed yes the app would not have been deployed.
--
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