December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21301) Path to OC binary is not shown on OpenShift 3 preference page if binary is on $PATH

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21301?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21301: ---------------------------------- Labels: preferences (was: ) > Path to OC binary is not shown on OpenShift 3 preference page if binary is on $PATH > ----------------------------------------------------------------------------------- > > Key: JBIDE-21301 > URL: https://issues.jboss.org/browse/JBIDE-21301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: preferences > > In JBIDE-21183 was implemented auto-lookup of 'oc' binary on $PATH. This works ok, but in Workbench Preference dialog on OpenShift 3 preference page where location to oc is shown and stored is not this path displayed in this case. If 'oc' binary is located on $PATH it should be also visible on OpenShift 3 preference page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21183) OC binary should be looked up on $PATH if the user doesnt provide a specific location

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21183?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-21183: --------------------------------------- Verified on nightly build having OpenShift tooling of version v20151211-0336-B118. > OC binary should be looked up on $PATH if the user doesnt provide a specific location > ------------------------------------------------------------------------------------- > > Key: JBIDE-21183 > URL: https://issues.jboss.org/browse/JBIDE-21183 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Fred Bricon > Labels: openshift_v3 > Fix For: 4.3.1.Beta1 > > > For port forwarding, log streming and rsyinc the tooling requires an oc binary to be installed on the local machine. The user is asked to to set the location of this binary in the OpenShift 3 preferences. He can do this either manually by browsing and pointing to the binary or by hitting "Restore Defaults" which looks it up in the $PATH. > We should lookup the binary in $PATH if the user doesnt provide anything, we should not error and tell the user to set the location as we do currently. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21183) OC binary should be looked up on $PATH if the user doesnt provide a specific location

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21183?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21183. --------------------------------- > OC binary should be looked up on $PATH if the user doesnt provide a specific location > ------------------------------------------------------------------------------------- > > Key: JBIDE-21183 > URL: https://issues.jboss.org/browse/JBIDE-21183 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Fred Bricon > Labels: openshift_v3 > Fix For: 4.3.1.Beta1 > > > For port forwarding, log streming and rsyinc the tooling requires an oc binary to be installed on the local machine. The user is asked to to set the location of this binary in the OpenShift 3 preferences. He can do this either manually by browsing and pointing to the binary or by hitting "Restore Defaults" which looks it up in the $PATH. > We should lookup the binary in $PATH if the user doesnt provide anything, we should not error and tell the user to set the location as we do currently. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21300) OC binary should be looked up on $PATH if the user doesnt provide a specific location

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21300: ------------------------------------- Summary: OC binary should be looked up on $PATH if the user doesnt provide a specific location Key: JBIDE-21300 URL: https://issues.jboss.org/browse/JBIDE-21300 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Andre Dietisheim Assignee: Fred Bricon Fix For: 4.3.1.Beta1 For port forwarding, log streming and rsyinc the tooling requires an oc binary to be installed on the local machine. The user is asked to to set the location of this binary in the OpenShift 3 preferences. He can do this either manually by browsing and pointing to the binary or by hitting "Restore Defaults" which looks it up in the $PATH. We should lookup the binary in $PATH if the user doesnt provide anything, we should not error and tell the user to set the location as we do currently. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21300) OC binary should be looked up on $PATH if the user doesnt provide a specific location

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21300?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21300: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta1) > OC binary should be looked up on $PATH if the user doesnt provide a specific location > ------------------------------------------------------------------------------------- > > Key: JBIDE-21300 > URL: https://issues.jboss.org/browse/JBIDE-21300 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Fred Bricon > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > For port forwarding, log streming and rsyinc the tooling requires an oc binary to be installed on the local machine. The user is asked to to set the location of this binary in the OpenShift 3 preferences. He can do this either manually by browsing and pointing to the binary or by hitting "Restore Defaults" which looks it up in the $PATH. > We should lookup the binary in $PATH if the user doesnt provide anything, we should not error and tell the user to set the location as we do currently. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21300) OC binary should be looked up on $PATH if the user doesnt provide a specific location

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21300?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-21300. ----------------------------------- Resolution: Done > OC binary should be looked up on $PATH if the user doesnt provide a specific location > ------------------------------------------------------------------------------------- > > Key: JBIDE-21300 > URL: https://issues.jboss.org/browse/JBIDE-21300 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Fred Bricon > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > For port forwarding, log streming and rsyinc the tooling requires an oc binary to be installed on the local machine. The user is asked to to set the location of this binary in the OpenShift 3 preferences. He can do this either manually by browsing and pointing to the binary or by hitting "Restore Defaults" which looks it up in the $PATH. > We should lookup the binary in $PATH if the user doesnt provide anything, we should not error and tell the user to set the location as we do currently. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21299) EL Knowledge Base Problem with PrimeFaces functions

by Andrei Ivanov (JIRA)

Andrei Ivanov created JBIDE-21299: ------------------------------------- Summary: EL Knowledge Base Problem with PrimeFaces functions Key: JBIDE-21299 URL: https://issues.jboss.org/browse/JBIDE-21299 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsf Affects Versions: 4.3.0.Final Environment: Eclipse Mars.1 (4.5.1), Primefaces 5.x Reporter: Andrei Ivanov Priority: Minor The PrimeFaces functions are not recognized: {noformat} "ifAnyGranted" cannot be resolved "ifGranted" cannot be resolved "remoteUser" cannot be resolved {noformat} These are defined in {{org.primefaces.util.SecurityUtils}} and {{primefaces-5.3.jar/META-INF/primefaces-p.taglib.xml}}. {code:xml} <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://xmlns.jcp.org/jsf/facelets" xmlns:h="http://xmlns.jcp.org/jsf/html" xmlns:f="http://xmlns.jcp.org/jsf/core" xmlns:c="http://xmlns.jcp.org/jsp/jstl/core" xmlns:p="http://primefaces.org/ui"> #{p:ifAnyGranted('ROLE_USER, ROLE_ADMIN')} #{p:ifGranted('ROLE_ADMIN')} #{p:remoteUser()} </html> {code} Similar to JBIDE-12317 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19977) Multiple download windows blinking for intermediate images while pulling from docker registry

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19977?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-19977: --------------------------------------- [~mmalina], can you verify if the problem still occurs for you ? > Multiple download windows blinking for intermediate images while pulling from docker registry > --------------------------------------------------------------------------------------------- > > Key: JBIDE-19977 > URL: https://issues.jboss.org/browse/JBIDE-19977 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Xavier Coulon > Fix For: 4.3.x > > > In Docker Tooling, after establishing a connection to my local boot2docker instance, I tried to pull jboss/wildfly in the Docker Images view. > This worked, but the UI was not very nice. To get the WildFly image, Docker needs to download about 30 intermediate images. For each image, a download window would open for a short period of time and then close again. > The overall progress is visible in the status bar of Eclipse, but otherwise you get multiple download windows opening and closing again, which is very distracting and you can't really do any other work in the meantime since a newly opened window will interrupt you again anyway. (Overall, it takes me several minutes to download the wildfly image for the first time.) > I think a better approach would be to have one window for all the images being downloaded combined. > Upstream BZ is here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=469627 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19974) Cannot detect running boot2docker on OS X

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19974?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-19974. ----------------------------------- Resolution: Done Fixed upstream > Cannot detect running boot2docker on OS X > ----------------------------------------- > > Key: JBIDE-19974 > URL: https://issues.jboss.org/browse/JBIDE-19974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Xavier Coulon > Fix For: 4.3.1.Beta1 > > > In Docker Explorer, when I want to create my first connection, I click on the link to create a connection, the dialog is opened and I get this in my Error View: > bash: no job control in this shell > An exception stack trace is not available. > Another warning is generated also: > Could not find default settings to connect to a local Docker daemon > An exception stack trace is not available. > I'm on OS X and have boot2docker running. By default, boot2docker will not add the DOCKER variables to .bash_profile, it will only instruct me to set them up like this: > export DOCKER_HOST=tcp://192.168.59.103:2376 > export DOCKER_CERT_PATH=/Users/rasp/.boot2docker/certs/boot2docker-vm > export DOCKER_TLS_VERIFY=1 > With the way the script in the Docker Tooling works (env | grep DOCKER), it cannot detect the variables unless they are in .bash_profile. > But even if I added them there (and a new Terminal window has these variables), Eclipse still can't detect the running Docker instance. > So something is wrong. > I logged an upstream bug here: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=469624 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21202) Central is stuck on "Loading JBoss Central" when offline

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21202?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21202: -------------------------------- Fix Version/s: 4.3.1.Beta1 (was: 4.3.1.Beta2) > Central is stuck on "Loading JBoss Central" when offline > -------------------------------------------------------- > > Key: JBIDE-21202 > URL: https://issues.jboss.org/browse/JBIDE-21202 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.1.Beta1 > Environment: JBDS 9.1.0.Beta1-v20151208-1226-B169 > Reporter: Radim Hopp > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.1.Beta1 > > > When started without internet access, Central is stuck on "Loading JBoss Central, please wait..." and error pops up: > {noformat} > Unable to open /resources/jbosstools-central-webpage.zip > Can't find embedded central zip > {noformat} > even though studio/plugins/org.jboss.tools.central_2.0.1.Beta1-v20151116-2016-B57/resources/jbosstools-central-webpage.zip is present on file system. > In JBDS 9.0.0.GA Central can be loaded without issues when offline. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 December 2015