[
https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-22362 at 6/20/16 6:20 AM:
-------------------------------------------------------------------
[~ibuziuk] [~mlabuda] I really think that we should have DEV_MODE enabled by default at
least in our server adapter (create the app via template which has DEV_MODE disabled, then
create the server adapter wich turns DEV_MODE=true by default). IMHO it's completely
unexpected for the user to get an application that he cannot modify while the others (eap,
php, etc.) are all modifyable by default.
The other question I am wondering about is that the casual nodejs users which are using
the cmd-line (oc) will have the very same experience: They'll just wondering about no
changes being propagated - when doing oc rsync - unless they read the documentation and
discover that they first have to enable DEV_MODE. Doesnt seem ideal to me. CC: [~fbricon]
was (Author: adietish):
[~ibuziuk] [~mlabuda] I really think that we should have DEV_MODE enabled by default at
least in our server adapter (create the app via template which has DEV_MODE disabled, then
create the server adapter wich turns DEV_MODE=true by default). IMHO it's completely
unexpected for the user to get an application that he cannot modify while the others (eap,
php, etc.) are all modifyable by default.
The other question I am wondering about is that the casual nodejs users which are using
the cmd-line (oc) will have the very same experience: They'll just wondering about no
changes being propagated - when doing oc rsync - unless they read the documentation and
discover that they first have to enable DEV_MODE. Doesnt seem ideal to me.
Server Adapter: Static changes done to nodejs application are not
visible
-------------------------------------------------------------------------
Key: JBIDE-22362
URL:
https://issues.jboss.org/browse/JBIDE-22362
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: javascript, openshift, upstream
Affects Versions: 4.4.0.Alpha2
Reporter: Marián Labuda
Assignee: Marián Labuda
Priority: Critical
Labels: openshift_v3, server_adapter
Fix For: 4.4.1.S116
I am having an OpenShift application based either on nodejs-example or
nodejs-mongodb-example template. Once application is up and running I create a new server
adapter and perform changes in index.html. These changes are static and should be (?)
immediately visible on OpenShift server, but they are not. I have checked whether changes
were published, but rsync in console shows expected output also changes done manually on
the server side to index.html are not visible in browser (even when cache overwritten is
triggered - so there is no caching problem in browser). This seems to be upstream issues,
but requires investigating.
So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift
instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)