[JBoss JIRA] (JBDS-3947) Some older versions of vagrant skip version validation
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3947?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3947:
-------------------------------------
There is a problem reported against 1.7.0 and in fact it doesn't work at all, but you right about two lines.
So I'll fix two lines problem first, then after I find the way to read installed version form windows registry, I can read version without running vagrant and then validation kick in organically.
> Some older versions of vagrant skip version validation
> ------------------------------------------------------
>
> Key: JBDS-3947
> URL: https://issues.jboss.org/browse/JBDS-3947
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Attachments: vagrant.png
>
>
> Some older versions (so far found 1.7.0, 1.6.5) will not have their version reckognized. As seen on the screenshot, it doesn't show the version it detected and the UI looks like it is going to be used. The installer tries to download and install its own though.
> !vagrant.png|thumbnail!
> The issue might be connected to the fact that with these versions the command
> {noformat}where vagrant{noformat}
> in fact returns 2 files
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22362:
---------------------------------------
IMHO it would be better to have modifiable nodejs application OOTB. Because to be forced to add environment variable to deployment config, deploy application again to get new running pod with DEV_MODE to true is not quite straightforward as I would imagine. What cons could bring us setting DEV_MODE to true by default?
> 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: Ilya Buziuk
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.1.Alpha1
>
>
> 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)
9 years, 10 months