December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-20573) OpenShift Explorer: decorate project showing last build/deployment failed/succeeded

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20573?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20573: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > OpenShift Explorer: decorate project showing last build/deployment failed/succeeded > ----------------------------------------------------------------------------------- > > Key: JBIDE-20573 > URL: https://issues.jboss.org/browse/JBIDE-20573 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Fix For: 4.5.0.AM1 > > > As reported by [~sspeiche] (or was it [~crobson]?), it'd be nice to have a visual clue of a project state, in the OpenShift Explorer. We should display the last pod status (build failed or deployment succeeded) next to a project's node -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20575) Improve OpenShift Explorer responsiveness

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20575?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20575: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Improve OpenShift Explorer responsiveness > ----------------------------------------- > > Key: JBIDE-20575 > URL: https://issues.jboss.org/browse/JBIDE-20575 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Fix For: 4.5.0.AM1 > > > As reported by [~sspeiche], OpenShift Explorer feels sluggish when lots of builds/deployments have to be displayed. Currently the tooling perform fetch queries for *everything*, nothing is cached. We need to investigate how implementing some form of caching could help improve responsiveness. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20570) OpenShift Explorer: needs an "Expand All" button

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20570?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20570: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > OpenShift Explorer: needs an "Expand All" button > ------------------------------------------------ > > Key: JBIDE-20570 > URL: https://issues.jboss.org/browse/JBIDE-20570 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Fix For: 4.5.0.AM1 > > > OpenShift Explorer displays collapsed resources by default. Having to expand resources manually one by one is annoying, as reported by [~sspeiche]. It'd be better to have an Expand All button next to the Collapse All one in the explorer. > Or it might make sense to be able to expand all from a particular node -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20569) OpenShift Explorer : "Import Application" menu is confusing

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20569?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20569: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.x) > OpenShift Explorer : "Import Application" menu is confusing > ----------------------------------------------------------- > > Key: JBIDE-20569 > URL: https://issues.jboss.org/browse/JBIDE-20569 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Fix For: 4.4.3.AM1 > > Attachments: import-application.png > > > [~sspeiche] finds the "Import Application" menu in OpenShift Explorer is confusing: does it mean import from eclipse to openshift or the other way around (it's the latter). Needs better wording. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20563) Configure non default console url for OpenShift 3 connections

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20563?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20563: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Configure non default console url for OpenShift 3 connections > ------------------------------------------------------------- > > Key: JBIDE-20563 > URL: https://issues.jboss.org/browse/JBIDE-20563 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Fix For: 4.5.0.AM1 > > > As a follow up on JBIDE-20502, the web console url doesn't necessarily match the connection URL (as in server.url+'/console'). > We should add an advanced section in the connection wizard, so that users can override the default web console url. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20558) org.jboss.tools.common.validation.JBTValidationException at org.jboss.tools.common.validation.AsYouTypeValidatorManager.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20558?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20558: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.3.x) > org.jboss.tools.common.validation.JBTValidationException at org.jboss.tools.common.validation.AsYouTypeValidatorManager. > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20558 > URL: https://issues.jboss.org/browse/JBIDE-20558 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, common > Affects Versions: 4.3.0.Beta2 > Reporter: The Alchemist > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.3.AM1 > > > {noformat} > org.jboss.tools.common.validation.JBTValidationException > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateJavaElement(AsYouTypeValidatorManager.java:222) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateJavaElement(AsYouTypeValidatorManager.java:217) > at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.endProcessing(JavaDirtyRegionProcessor.java:507) > at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:697) > Caused by: java.lang.NullPointerException > at org.jboss.tools.cdi.core.CDIUtil.collectAdditionalInterceptorBindingDeclaratios(CDIUtil.java:1114) > at org.jboss.tools.cdi.core.CDIUtil.collectAdditionalInterceptorBindingDeclaratios(CDIUtil.java:1118) > at org.jboss.tools.cdi.core.CDIUtil.getAllInterceptorBindingDeclaratios(CDIUtil.java:1110) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.hasConflictedInterceptorBindings(CDICoreValidator.java:984) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateInterceptorBindings(CDICoreValidator.java:970) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateClassBean(CDICoreValidator.java:952) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:792) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateResource(CDICoreValidator.java:641) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:574) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183) > ... 4 more > {noformat} > I wish I could see which class is causing this error... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20529) Master JIRA for XML Validation Problems

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20529?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20529: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.x) > Master JIRA for XML Validation Problems > --------------------------------------- > > Key: JBIDE-20529 > URL: https://issues.jboss.org/browse/JBIDE-20529 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples, server > Reporter: Rob Stryker > Labels: xtriage > Fix For: 4.4.3.AM1 > > > This JIRA is meant to be a master container jira for all xml validation issues. These include identifying projects that are enganging in bad xml behavior, projects that point to namespaces or xsd locations that no longer exist, example projects using relative paths for linking to other xsd, and others. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20513) tricky to login to openshift when token expires

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20513?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20513: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > tricky to login to openshift when token expires > ----------------------------------------------- > > Key: JBIDE-20513 > URL: https://issues.jboss.org/browse/JBIDE-20513 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Fix For: 4.5.0.AM1 > > > I logged in with token. > 24hrs later I start eclipse and expand the connection in explorer > expecting to just login. > Here is what happens instead: > a) info message (not error) is logged to error log hiding the explorer view > b) after some seconds (seems there is a timeout) a login dialog comes up saying I need to sign in (no clear info that auth failed or token missing etc.). > cancel the dialog since I'm trying to figure out what happened. > c) Now the explorer just shows "You must obtain API token by visiting ..." as child and I cannot see straightforward way to log in again. > Turns out Refresh does trigger login again. > meanwhile command line 'oc' seem to be fine at logging in with token older than 24 hrs...can't verify that though, but in any case: > a) do a user really need to re-login every 24 hours ? > b) the error handling/dialogs shown are not very informative -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20497) New Application wizard: shows New Project wizard if there's no project yet

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20497?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-20497. ------------------------------ Fix Version/s: 4.4.2.Final (was: 4.4.x) Resolution: Done > New Application wizard: shows New Project wizard if there's no project yet > -------------------------------------------------------------------------- > > Key: JBIDE-20497 > URL: https://issues.jboss.org/browse/JBIDE-20497 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Max Rydahl Andersen > Labels: application_wizard, openshift_v3 > Fix For: 4.4.2.Final > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > When running Create New Application and I have no project a separate dialog pops up asking for Create New project with no real explanation. > Could the Create project step not be something that gets to be a page in New Application or somehow not be so "separate" and at least with some info that you need to create project before creating application. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20484) Application wizard: [origin_intservice_51] warn (but allow) if white space value for template parameter

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20484?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20484: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Application wizard: [origin_intservice_51] warn (but allow) if white space value for template parameter > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20484 > URL: https://issues.jboss.org/browse/JBIDE-20484 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Environment: 3.0.0.CR1-v20150820-0237-B971 > Reporter: Yue Wang > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.5.0.AM1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > " "(several white spaces) value should not allowed for a required parameter. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 2016