[JBoss JIRA] (JBDS-4014) Track rh-eclipse46-devstudio-*.rpm version usage
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4014?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4014:
----------------------------------
[~mat.booth] ping again on this -- can I apply the above PR? is your new plugin available somewhere upstream from devstudio rpm so I can see them both co-installed in /opt/rh/rh-eclipse46/root/usr/share/ somewhere? I still only see my version of the plugin but maybe I don't have the latest rh-eclipse46* stuff installed ?
> Track rh-eclipse46-devstudio-*.rpm version usage
> ------------------------------------------------
>
> Key: JBDS-4014
> URL: https://issues.jboss.org/browse/JBDS-4014
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: rpm, usage
> Reporter: Alexey Kazakov
> Assignee: Alexander Kurtakov
> Priority: Critical
> Fix For: 10.2.0.AM3
>
>
> We need to distinguish the following use cases:
> 1) Devstudio installed via RPM
> 2) Devstudio installed via P2 but on top of the "base" eclipse rpm
> 3) Devstudio installed traditionally (jar installer or p2)
> As a bonus we could want to track if the DTS + devstudio rpms were both installed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4014) Track rh-eclipse46-devstudio-*.rpm version usage
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4014?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-4014:
---------------------------------
Component/s: rpm
> Track rh-eclipse46-devstudio-*.rpm version usage
> ------------------------------------------------
>
> Key: JBDS-4014
> URL: https://issues.jboss.org/browse/JBDS-4014
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: rpm, usage
> Reporter: Alexey Kazakov
> Assignee: Alexander Kurtakov
> Priority: Critical
> Fix For: 10.2.0.AM3
>
>
> We need to distinguish the following use cases:
> 1) Devstudio installed via RPM
> 2) Devstudio installed via P2 but on top of the "base" eclipse rpm
> 3) Devstudio installed traditionally (jar installer or p2)
> As a bonus we could want to track if the DTS + devstudio rpms were both installed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-22362:
-------------------------------------
[~adietish], JBIDE-22225 is completely different story, so let's not mix them ;-)
just for the record once the V8 debug session ends server republish all changes - https://github.com/jbosstools/jbosstools-openshift/pull/1340/commits/1bf9...
I guess the error you described in the last comment is smth. I also faced. Also, I think there was also another one coupled with changing server adapter state from "debug" to "run". Anyway, it looks like approach with "just" setting DEV_MODE for vanilla runs will not work
> 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
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Ilya Buziuk
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.2.AM3
>
> Attachments: enabling-dev-mode-has-encountered-an-error.png
>
>
> 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, 5 months
[JBoss JIRA] (JBDS-4131) Can't import example project after RPM installation on RHEL 7
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4131?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-4131:
------------------------------------
Assignee: Snjezana Peco (was: Nick Boldt)
> Can't import example project after RPM installation on RHEL 7
> -------------------------------------------------------------
>
> Key: JBDS-4131
> URL: https://issues.jboss.org/browse/JBDS-4131
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.2.0.AM3
> Environment: RHEL Server 7.2.
> Reporter: Lukáš Valach
> Assignee: Snjezana Peco
> Fix For: 10.2.0.AM3
>
> Attachments: DevstudiErrorLog.txt, devstudio10.2.wtf.png, devstudio10.2.wtf2.png, import_wizard.png, rh-eclipse46-devstudio.repo
>
>
> During the test of RPM installation on RHEL 7 I noticed that I can't import HTML5 example project from central. Only the window with message "Refreshing project examples" appear for a while and then nothing happens.
> There is one warning and many errors in Error Log View.
> Error log export: [^DevstudiErrorLog.txt]
> I also tried to import project from file system, but there isn't the "Existing Maven Project" option in the import wizard. [^import_wizard.png]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4131) Can't import example project after RPM installation on RHEL 7
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4131?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-4131:
--------------------------------------
[~snjeza] could you help with this issue please?
> Can't import example project after RPM installation on RHEL 7
> -------------------------------------------------------------
>
> Key: JBDS-4131
> URL: https://issues.jboss.org/browse/JBDS-4131
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.2.0.AM3
> Environment: RHEL Server 7.2.
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM3
>
> Attachments: DevstudiErrorLog.txt, devstudio10.2.wtf.png, devstudio10.2.wtf2.png, import_wizard.png, rh-eclipse46-devstudio.repo
>
>
> During the test of RPM installation on RHEL 7 I noticed that I can't import HTML5 example project from central. Only the window with message "Refreshing project examples" appear for a while and then nothing happens.
> There is one warning and many errors in Error Log View.
> Error log export: [^DevstudiErrorLog.txt]
> I also tried to import project from file system, but there isn't the "Existing Maven Project" option in the import wizard. [^import_wizard.png]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4132) Could not load nodeJSInstall: node-v0.10.22-linux-x86_64
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4132?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4132:
----------------------------------
Need to check if we need to include one of these in the devstudio rpm:
{code}
rh-nodejs4.x86_64 : rh-nodejs4 Software Collection
rh-nodejs4-runtime.x86_64 : Package that handles rh-nodejs4 Software Collection.
{code}
> Could not load nodeJSInstall: node-v0.10.22-linux-x86_64
> --------------------------------------------------------
>
> Key: JBDS-4132
> URL: https://issues.jboss.org/browse/JBDS-4132
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: build, rpm
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Fix For: 10.2.0.AM3
>
>
> Snippet from the log attached to JBDS-4131:
> {code}!ENTRY tern.eclipse.ide.server.nodejs.core 4 0 2016-10-21 14:34:24.958
> !MESSAGE Could not load nodeJSInstall: node-v0.10.22-linux-x86_64
> !STACK 0
> java.io.FileNotFoundException: /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64_1.1.0.201511082254/node-v0.10.22-linux-x86_64/LICENSE (No such file or directory)
> at java.io.FileOutputStream.open0(Native Method)
> at java.io.FileOutputStream.open(FileOutputStream.java:270)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:213)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:162)
> at tern.utils.ZipUtils.extract(ZipUtils.java:83)
> at tern.eclipse.ide.server.nodejs.internal.core.NodejsInstall.<init>(NodejsInstall.java:56)
> at tern.eclipse.ide.server.nodejs.internal.core.NodejsInstallManager.addNodejsInstalls(NodejsInstallManager.java:132)
> at tern.eclipse.ide.server.nodejs.internal.core.NodejsInstallManager.loadNodejsInstalls(NodejsInstallManager.java:117)
> at tern.eclipse.ide.server.nodejs.internal.core.NodejsInstallManager.getNodejsInstalls(NodejsInstallManager.java:69)
> at tern.eclipse.ide.server.nodejs.internal.core.preferences.TernNodejsCorePreferenceConstants.useBundledNodeJsInstall(TernNodejsCorePreferenceConstants.java:91)
> at tern.eclipse.ide.server.nodejs.internal.core.preferences.TernNodejsCorePreferenceConstants.initializeDirectAccess(TernNodejsCorePreferenceConstants.java:70)
> at tern.eclipse.ide.server.nodejs.internal.core.preferences.TernNodejsCorePreferenceConstants.initializeDefaultValues(TernNodejsCorePreferenceConstants.java:45)
> at tern.eclipse.ide.server.nodejs.internal.core.preferences.TernNodejsCorePreferenceInitializer.initializeDefaultPreferences(TernNodejsCorePreferenceInitializer.java:24)
> at org.eclipse.core.internal.preferences.PreferenceServiceRegistryHelper$1.run(PreferenceServiceRegistryHelper.java:298)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.preferences.PreferenceServiceRegistryHelper.runInitializer(PreferenceServiceRegistryHelper.java:301)
> at org.eclipse.core.internal.preferences.PreferenceServiceRegistryHelper.applyRuntimeDefaults(PreferenceServiceRegistryHelper.java:131)
> at org.eclipse.core.internal.preferences.PreferencesService.applyRuntimeDefaults(PreferencesService.java:370)
> at org.eclipse.core.internal.preferences.DefaultPreferences.applyRuntimeDefaults(DefaultPreferences.java:222)
> at org.eclipse.core.internal.preferences.DefaultPreferences.load(DefaultPreferences.java:276)
> at org.eclipse.core.internal.preferences.EclipsePreferences.create(EclipsePreferences.java:370)
> at org.eclipse.core.internal.preferences.EclipsePreferences.internalNode(EclipsePreferences.java:623)
> at org.eclipse.core.internal.preferences.DefaultPreferences.node(DefaultPreferences.java:147)
> at org.eclipse.core.internal.preferences.legacy.PreferenceForwarder.getDefaultPreferences(PreferenceForwarder.java:134)
> at org.eclipse.core.internal.preferences.legacy.PreferenceForwarder.getString(PreferenceForwarder.java:663)
> at tern.eclipse.ide.core.preferences.PreferencesSupport.getWorkspacePreferencesValue(PreferencesSupport.java:115)
> at tern.eclipse.ide.server.nodejs.internal.core.preferences.TernNodejsCorePreferencesSupport.isNodejsRemoteAccess(TernNodejsCorePreferencesSupport.java:147)
> at tern.eclipse.ide.server.nodejs.internal.core.TernNodejsServerFactory.isRemoteAccess(TernNodejsServerFactory.java:67)
> at tern.eclipse.ide.server.nodejs.internal.core.TernNodejsServerFactory.create(TernNodejsServerFactory.java:35)
> at tern.eclipse.ide.internal.core.TernServerType.createServer(TernServerType.java:90)
> at tern.eclipse.ide.internal.core.resources.IDETernProject.getTernServer(IDETernProject.java:161)
> at tern.resources.TernFileSynchronizer.ensureSynchronized(TernFileSynchronizer.java:160)
> at tern.eclipse.ide.internal.ui.EditorActivationTracker$2.run(EditorActivationTracker.java:85)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> !ENTRY tern.eclipse.ide.core 4 0 2016-10-21 14:34:27.182
> !MESSAGE java.io.IOException: Cannot run program "node" (in directory "/home/lvalach/rpm-workspace/StaticWebProject"): error=2, No such file or directory
> !STACK 0
> tern.TernException: java.io.IOException: Cannot run program "node" (in directory "/home/lvalach/rpm-workspace/StaticWebProject"): error=2, No such file or directory
> at tern.eclipse.ide.internal.core.resources.IDETernFileUploader$1.onError(IDETernFileUploader.java:133)
> at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:131)
> at tern.eclipse.ide.internal.core.resources.IDETernFileUploader.run(IDETernFileUploader.java:124)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: tern.server.nodejs.process.NodejsProcessException: java.io.IOException: Cannot run program "node" (in directory "/home/lvalach/rpm-workspace/StaticWebProject"): error=2, No such file or directory
> at tern.server.nodejs.process.internal.NodejsProcess.start(NodejsProcess.java:245)
> at tern.server.nodejs.process.AbstractNodejsProcess.start(AbstractNodejsProcess.java:144)
> at tern.server.nodejs.NodejsTernServer.getBaseURL(NodejsTernServer.java:202)
> at tern.server.nodejs.NodejsTernServer.makeRequest(NodejsTernServer.java:139)
> at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:127)
> ... 2 more
> Caused by: java.io.IOException: Cannot run program "node" (in directory "/home/lvalach/rpm-workspace/StaticWebProject"): error=2, No such file or directory
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
> at tern.server.nodejs.process.internal.NodejsProcess.start(NodejsProcess.java:232)
> ... 6 more
> Caused by: java.io.IOException: error=2, No such file or directory
> at java.lang.UNIXProcess.forkAndExec(Native Method)
> at java.lang.UNIXProcess.<init>(UNIXProcess.java:247)
> at java.lang.ProcessImpl.start(ProcessImpl.java:134)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
> ... 7 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBTIS-949) Rename the name of the installer with runtime
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-949?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-949:
----------------------------------
Hey Andrej - by calling it a 'runtime-installer' it seems to imply that it installs just runtimes and not the tooling as well. Can we combine 'standalone' and runtime somehow - wdyt?
> Rename the name of the installer with runtime
> ---------------------------------------------
>
> Key: JBTIS-949
> URL: https://issues.jboss.org/browse/JBTIS-949
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: distribution
> Affects Versions: 10.0.0.CR1
> Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Minor
>
> Rename the name of the installer with runtime. I suggest
> {code}
> devstudio-integration-stack-10.0.0.CR1-runtime-installer.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBTIS-950) Cannot connect to fuse runtime after installing by the installer
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-950?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-950:
----------------------------------
Hey [~lhein] - We had talked about this before. Do you want to ship the Fuse Runtime with user 'admin' enabled by default? Clearly nothing to be done except document this for this release - question is for future Fuse releases.
> Cannot connect to fuse runtime after installing by the installer
> ----------------------------------------------------------------
>
> Key: JBTIS-950
> URL: https://issues.jboss.org/browse/JBTIS-950
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 10.0.0.CR1
> Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar
> Reporter: Andrej Podhradsky
> Assignee: Lars Heinemann
> Priority: Critical
>
> Cannot connect to fuse runtime after installing by the installer. The problem is that the runtime doesn't specify any user by default. This is important if you need to execute a command in the terminal (Terminal view).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months