February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21658) Property sheet cells are editable

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21658?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21658: --------------------------------------------- can't we return a propertyeditor that just don't react to edit/modifyevents ? That should allow one to select the value and copy that but not do any edits? > Property sheet cells are editable > --------------------------------- > > Key: JBIDE-21658 > URL: https://issues.jboss.org/browse/JBIDE-21658 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.x > Environment: Boss Openshift UI Plugin Version: 3.1.0.CR1-v20160202-0335-B166 > Reporter: Steve Speicher > Attachments: Screen Shot 2016-02-06 at 9.03.05 AM.png > > > When I bring up the property sheet, values are editable but I can't really edit them. It would be good if users were disallowed from changing values (like the property name field is restricted) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21660) openshift 3 is not inlcuded by default in JBoss Tools

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21660?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-21660. ----------------------------------------- Resolution: Rejected not a bug - yes, I used marketplace thinking of this as being our next beta but since we are in GA mode it is not there. brainfart. Too bad marketplace doens't support "beta" mode ;) > openshift 3 is not inlcuded by default in JBoss Tools > ----------------------------------------------------- > > Key: JBIDE-21660 > URL: https://issues.jboss.org/browse/JBIDE-21660 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace, openshift, updatesite > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.CR1 > > > installing latest release and I don't get OpenShift 3 into default install. > The goal was to get openshift included by default - is it ready for it ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21626) Pod is not created when docker image is deployed to OpenShift

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21626?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21626: --------------------------------------- [~mlabuda] I think we are only now mapping images that are resolved using ImageStreamTags. Are you able to provide an example of what you describe above so we have a scenario to work with? > Pod is not created when docker image is deployed to OpenShift > ------------------------------------------------------------- > > Key: JBIDE-21626 > URL: https://issues.jboss.org/browse/JBIDE-21626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Critical > Labels: openshift_v3 > Fix For: 4.3.1.CR1 > > > When deploying a docker image to OpenShift via oc binary, pod where the image is supposed to run is created, together with service and router. But when deploying a docker image to OpenShift via OpenShift tools, no pod is created, only service and router. When using cli, pod is created later (what I noticed, there is different pull policy between creating from cli with "oc new-app docker-image" and creating from IDE). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21658) Property sheet cells are editable

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21658?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21658: ----------------------------------------------- If cell editor is not defined, then copying is possible, but it copies the pair name-value, for instance {code} Namespace cake1 {code} and there is no way to select and copy part of the value. If it is ok, then just cell editor should be removed. Or, could it be preferrable to have more user friendly (imho) approach with uneditable cell editor that allows to select and copy any part of the value? [~maxandersen], what do you advise? > Property sheet cells are editable > --------------------------------- > > Key: JBIDE-21658 > URL: https://issues.jboss.org/browse/JBIDE-21658 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.x > Environment: Boss Openshift UI Plugin Version: 3.1.0.CR1-v20160202-0335-B166 > Reporter: Steve Speicher > Attachments: Screen Shot 2016-02-06 at 9.03.05 AM.png > > > When I bring up the property sheet, values are editable but I can't really edit them. It would be good if users were disallowed from changing values (like the property name field is restricted) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18082) Application wizard, Connection wizard: Last used connection from explorer is not preselected

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18082?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-18082: ----------------------------------------------- [~adietish], please take a look at the pull request. > Application wizard, Connection wizard: Last used connection from explorer is not preselected > -------------------------------------------------------------------------------------------- > > Key: JBIDE-18082 > URL: https://issues.jboss.org/browse/JBIDE-18082 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard, connection_wizard > Fix For: LATER > > > In JBIDE-17568 was implemented preselection of last used connection via menu File - New - OpenShift Application. But preselection of last used connection from OpenShift explorer is not working (probably has not been implemented yet). > We should provide preselection also for last used connection via OpenShift explorer. Preselection via Menu now works like this: > User has lets say 2 connections. If he opens New Application wizard via menu File - New - OpenShift Application, then first connection is preselected. He chooses second connection in opened New Application wizard (on the first page containing credentials), clicks Next button and then user clicks Cancel. Then user open New application wizard via menu File - New - OpenShift application again and second connection is preselected. > Suggested solution for explorer: > User has 2 connections and first one is used for preselection. User selects in OpenShift explorer second connection and opens New application wizard via context menu. After closing New application wizard shell (by its completion or canceling) user should get preselected second connection after opening a New Application wizard via menu File - New - OpenShift Application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18497) Importing PicketLink quickstart raises error

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18497?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-18497. --------------------------------- I cannot reproduce this in Beta2 using the jboss-picketlink-sts quickstart from Central. Closing. > Importing PicketLink quickstart raises error > -------------------------------------------- > > Key: JBIDE-18497 > URL: https://issues.jboss.org/browse/JBIDE-18497 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.CR1 > Java 1.7 - OpenJDK > RHEL6 > Reporter: Len DiMaggio > Assignee: Rob Stryker > Labels: upstream, xml_validation_quickstarts_redirect > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > Steps to recreate issue: > * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap > * Install JBDS8.0.CR1 > * Import-> Existing Maven Projects - select the quickstart > The error is: > jboss-picketlink-sts > Referenced file contains errors (http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-wsse-server.xml /jboss-picketlink-sts/src/main/webapp/WEB-INF line 1 XML Problem -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20663) getAndInstallEclipse.groovy :: composite install, Install grinder and p2 director installer jobs need to be updated to support new mars.N filename conventions

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20663?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20663. --------------------------------- Install grinder is working, so I believe this can be closed. > getAndInstallEclipse.groovy :: composite install, Install grinder and p2 director installer jobs need to be updated to support new mars.N filename conventions > -------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20663 > URL: https://issues.jboss.org/browse/JBIDE-20663 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.CR1, 4.3.1.Beta2, 4.4.0.Alpha1 > > Attachments: install-grinder-results.png > > > *Old filename convention:* > http://download.eclipse.org/technology/epp/downloads/release/mars/R/eclip... > So, we used to be able to pass in versionLabel = R or eclipseBundleVersion = mars.R > And this could be parsed easily into folder = mars/R with filename mars-R. > *New filename convension:* > http://download.eclipse.org/technology/epp/downloads/release/mars/SR1-RC3... > But here, we have a mix of "mars/SR1-RC3" and "mars-1-RC3", so we need to include logic to add in the "SR" part that appears ONLY in the folder, but not the filename. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21666) Set correct OpenShift resource name for Repplication controller in properties view

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21666: ------------------------------------- Summary: Set correct OpenShift resource name for Repplication controller in properties view Key: JBIDE-21666 URL: https://issues.jboss.org/browse/JBIDE-21666 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda At the moment we have following OpenShift resources listed for a project in Properties view: * Builds * Build Configs * Deployment Configs * Pods * Deployments * Image Streams * Routes * Services What is misleading is having "Deployment Configs" and "Deployments". We are trying to copy web-UI, as far as I know. But in the web-UI under Deployments are placed "Deployment Configs". We, under "Deployments" in properties view, have "Replication Controllers". So its misleading for me. I think we should rename our Deployment Configs to Deployment and our Deployments to Replication Controllers, which are missing in web-ui because the most significant functionality accessible via Replication Controllers is editable in web-ui through overview page (e.g spinner for amount of pods). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21666) Set correct OpenShift resource name for Repplication controller in properties view

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21666?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21666: ---------------------------------- Labels: openshift_v3 (was: ) > Set correct OpenShift resource name for Repplication controller in properties view > ---------------------------------------------------------------------------------- > > Key: JBIDE-21666 > URL: https://issues.jboss.org/browse/JBIDE-21666 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > > At the moment we have following OpenShift resources listed for a project in Properties view: > * Builds > * Build Configs > * Deployment Configs > * Pods > * Deployments > * Image Streams > * Routes > * Services > What is misleading is having "Deployment Configs" and "Deployments". We are trying to copy web-UI, as far as I know. But in the web-UI under Deployments are placed "Deployment Configs". We, under "Deployments" in properties view, have "Replication Controllers". So its misleading for me. I think we should rename our Deployment Configs to Deployment and our Deployments to Replication Controllers, which are missing in web-ui because the most significant functionality accessible via Replication Controllers is editable in web-ui through overview page (e.g spinner for amount of pods). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21666) Set correct OpenShift resource name for Repplication controller in properties view

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21666?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21666: ---------------------------------- Priority: Critical (was: Major) > Set correct OpenShift resource name for Repplication controller in properties view > ---------------------------------------------------------------------------------- > > Key: JBIDE-21666 > URL: https://issues.jboss.org/browse/JBIDE-21666 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3 > > At the moment we have following OpenShift resources listed for a project in Properties view: > * Builds > * Build Configs > * Deployment Configs > * Pods > * Deployments > * Image Streams > * Routes > * Services > What is misleading is having "Deployment Configs" and "Deployments". We are trying to copy web-UI, as far as I know. But in the web-UI under Deployments are placed "Deployment Configs". We, under "Deployments" in properties view, have "Replication Controllers". So its misleading for me. I think we should rename our Deployment Configs to Deployment and our Deployments to Replication Controllers, which are missing in web-ui because the most significant functionality accessible via Replication Controllers is editable in web-ui through overview page (e.g spinner for amount of pods). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 February 2016