June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22575) Extract CDK's Docker registry from vagrant service-manager env

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-22575: ----------------------------------- Summary: Extract CDK's Docker registry from vagrant service-manager env Key: JBIDE-22575 URL: https://issues.jboss.org/browse/JBIDE-22575 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdk Affects Versions: 4.4.0.Final Reporter: Fred Bricon The docker registry url is currently hard coded when created a new OpenShift connection for the CDK (JBIDE-22441). With https://github.com/projectatomic/vagrant-service-manager/issues/210 being fixed and the CDK 2.1 looming around the corner, it's now possible to get the DOCKER_REGISTRY value from the CDK: {quote} vagrant service-manager env # docker env: # Set the following environment variables to enable access to the # docker daemon running inside of the vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 export DOCKER_CERT_PATH=/Users/fbricon/Dev/openshift/cdk.old/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 # openshift env: # You can access the OpenShift console on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc login https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io {quote} We should store the docker registry with a https:// prefix, if the value is not a URL -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3938) Dvelopment Suite Installer should install sshfs vagrant plugin

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3938?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3938: -------------------------------- Fix Version/s: 10.0.0.GA > Dvelopment Suite Installer should install sshfs vagrant plugin > -------------------------------------------------------------- > > Key: JBDS-3938 > URL: https://issues.jboss.org/browse/JBDS-3938 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3938) Dvelopment Suite Installer should install sshfs vagrant plugin

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3938?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3938: ----------------------------- > Dvelopment Suite Installer should install sshfs vagrant plugin > -------------------------------------------------------------- > > Key: JBDS-3938 > URL: https://issues.jboss.org/browse/JBDS-3938 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3938) Dvelopment Suite Installer should install sshfs vagrant plugin

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3938: ----------------------------------- Summary: Dvelopment Suite Installer should install sshfs vagrant plugin Key: JBDS-3938 URL: https://issues.jboss.org/browse/JBDS-3938 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.0.0.GA Reporter: Denis Golovin Assignee: Denis Golovin -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3938) Dvelopment Suite Installer should install sshfs vagrant plugin

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3938?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3938: -------------------------------- > Dvelopment Suite Installer should install sshfs vagrant plugin > -------------------------------------------------------------- > > Key: JBDS-3938 > URL: https://issues.jboss.org/browse/JBDS-3938 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22362 at 6/8/16 9:12 AM: ------------------------------------------------------------------ I can replicate this with yesterdays CDK (rhel-7-cdk-vagrant-scratch-7.2.07062016-1.x86_64.vagrant-libvirt.box). The modified file is transferred but no changes are visible in the browser. Same is true if I modify the file in the pod, the changes are not reflected in the browser. There are actually 2 files index.html (modifying any of these has no browser visible effect): * /opt/app-root/src/views/index.html (the one we're publishing to) * /tmp/src/views/index.html was (Author: adietish): I can replicate this with yesterdays CDK (rhel-7-cdk-vagrant-scratch-7.2.07062016-1.x86_64.vagrant-libvirt.box). > 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: 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.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

1
0
0 / 0

[JBoss JIRA] (JBTIS-729) Teiid Designer depends on bundle in JBT/devstudio TP which no longer exists

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-729?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-729: ------------------------------------------- why is it in the birt updatesite ? does birt require it even from Mars ? > Teiid Designer depends on bundle in JBT/devstudio TP which no longer exists > --------------------------------------------------------------------------- > > Key: JBTIS-729 > URL: https://issues.jboss.org/browse/JBTIS-729 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform, teiid > Affects Versions: 4.4.0.Alpha1-TP, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Barry LaFond > Fix For: 4.4.0.Alpha1-TP > > > org.eclipse.core.runtime.compatibility was removed from the JBT and devstudio target platforms because nothing in JBT/devstudio requires it any more. > As a result, when you try to install Teiid Designer into the staged JBT 4.4.0.Final or devstudio 10.0.0.GA via Central, you get this error: > {code} > !MESSAGE Missing requirement: Teiid DataTools Connectivity 10.0.0.Beta3-v20160218-1807-B4076 (org.teiid.datatools.connectivity.feature.feature.group 10.0.0.Beta3-v20160218-1807-B4076) requires 'org.eclipse.core.runtime.compatibility [3.2.200,4.0.0)' but it could not be found > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22362: -------------------------------------- Assignee: Marián Labuda [~mlabuda] So this is OS issue? If so please file this issue upstream. > 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: 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.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

1
0
0 / 0

[JBoss JIRA] (JBDS-3834) Install fail - what next?

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3834?page=com.atlassian.jira.plugin.... ] Misha Ali updated JBDS-3834: ---------------------------- Attachment: error.PNG For example, here is the error I'm getting at the moment. The CDK component told me quite early on that it failed as shown here, but it is not till this point in the install that it stops altogether and now I'm unsure about how to quit the installation or retry that component. > Install fail - what next? > ------------------------- > > Key: JBDS-3834 > URL: https://issues.jboss.org/browse/JBDS-3834 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Misha Ali > Assignee: Denis Golovin > Priority: Minor > Fix For: 10.0.0.GA > > Attachments: error.PNG, fail_install.PNG > > > Testing the Installer a bit more and I realize this is currently tech preview but when one (or more) components fail, there is no next step for users. There is no cancel or quit button to exit the failed install, nor is there a retry for the failed component, nor any error message at all. As a user, I'd be confused about what I should do next at this stage. I think this might be worth looking into with UX for the 9.1 GA++ release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3937) NPE in Web Service Tester

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBDS-3937: --------------------------------------- Summary: NPE in Web Service Tester Key: JBDS-3937 URL: https://issues.jboss.org/browse/JBDS-3937 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: webservices Environment: Version: 10.0.0.GA Build id: GA-v20160603-1025-B5510 Reporter: Andrej Podhradsky NPE in Web Service Tester when calling SOAP WS. {code} java.lang.NullPointerException at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleWSTest(JAXRSWSTestView2.java:1909) at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$34(JAXRSWSTestView2.java:1809) at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$21.run(JAXRSWSTestView2.java:1726) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {code} Note that this works fine in JBDS 9.1.0.GA -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2016