[
https://issues.jboss.org/browse/JBIDE-13806?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-13806:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure you have an OpenShift application imported to your workspace along
with the server adapter created.
# EXEC: change some file
# EXEC: in *Servers* view, choose its server adapter and pick *Publish* from the context
menu.
Result:
The console with the push log is not opened
Expected result:
After the push/publish is finished, the console with the output should be shown to the
user.
Workaround Description: use tail files before you push. You'll spot the changes
that happen on the PaaS
OpenShift console does not show the maven build logs anymore
------------------------------------------------------------
Key: JBIDE-13806
URL:
https://issues.jboss.org/browse/JBIDE-13806
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.0.Alpha1
Reporter: Xavier Coulon
Assignee: Andre Dietisheim
The OpenShift tooling does not show the maven build logs after some changes were
published on openshift.
The workaround is to tail log files to see the app server activity (and see when the app
is redeployed)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira