August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3985) Modify installation progress bar to include supplemental runtimes

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBDS-3985?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBDS-3985: ----------------------------- Attachment: x2.png x1.png > Modify installation progress bar to include supplemental runtimes > ----------------------------------------------------------------- > > Key: JBDS-3985 > URL: https://issues.jboss.org/browse/JBDS-3985 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.1.0.AM1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Minor > Attachments: x1.png, x2.png > > > At install time, if an additional runtime is specified it does not appear in the overall progress bar. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22446) Release process should disallow inclusion of snapshots artifacts

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22446: ------------------------------------ Cool you got the NPE. But I'm not sure I fully got the rest of the comment. Do you mean the build with current master will fail (which I don't expect) or a release build (AMX/|GA|Final) will fail if we don't update the dependency (which is what I was expecting) > Release process should disallow inclusion of snapshots artifacts > ---------------------------------------------------------------- > > Key: JBIDE-22446 > URL: https://issues.jboss.org/browse/JBIDE-22446 > Project: Tools (JBoss Tools) > Issue Type: Release > Components: build > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.4.1.AM3 > > > 4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones > Update: This issues is for adding some automated test/check to detect situation when our release includes a snapshot dependency. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22446) Release process should disallow inclusion of snapshots artifacts

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22446: ------------------------------------ Turns out the NPE was caused by my trying to do null.equals(). I've fixed that here: https://github.com/jbosstools/jbosstools-maven-plugins/commit/40a84804e00... And, I've enabled the enforcer check on all projects (instead of <pluginManagement> I put it into <plugins> in the parent pom): https://github.com/jbosstools/jbosstools-build/commit/98f8bc98f8687237616... So, openshift.client plugin build will now fail unless you disable/override this check, using this PR: https://github.com/jbosstools/jbosstools-openshift/pull/1275/files?w=1 There are three ways to save the build from failing: * include openshift-restclient-java.version in the <excludePattern>...</excludePattern> regex (permanent exception) * <buildAliasSearch>Final|GA</buildAliasSearch> instead of <buildAliasSearch>AM3|Final|GA</buildAliasSearch> (but it'll fail again in the Final sprint) * setting <fail>false</fail> (only a warning will be thrown in the build log) > Release process should disallow inclusion of snapshots artifacts > ---------------------------------------------------------------- > > Key: JBIDE-22446 > URL: https://issues.jboss.org/browse/JBIDE-22446 > Project: Tools (JBoss Tools) > Issue Type: Release > Components: build > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.4.1.AM3 > > > 4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones > Update: This issues is for adding some automated test/check to detect situation when our release includes a snapshot dependency. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-374) Docker Containers View and Docker Images View do not fill in automatically at start up [EBZ#499121]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-374: --------------------------------------- Summary: Docker Containers View and Docker Images View do not fill in automatically at start up [EBZ#499121] Key: ERT-374 URL: https://issues.jboss.org/browse/ERT-374 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon.1 (4.6) When starting up an Eclipse session that had the Docker Explorer view and one or both of the Docker Containers view and Docker Images view, a default connection will be selected, but the Containers and Images view will not fill in their tables. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22647) Update code to support openshift-restclient-java changes including auth context

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22647?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22647: ------------------------------------ I agree but then DefaultClient is attached to an OS3 connection which can have several project thus reaching the limlit > Update code to support openshift-restclient-java changes including auth context > ------------------------------------------------------------------------------- > > Key: JBIDE-22647 > URL: https://issues.jboss.org/browse/JBIDE-22647 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.4.1.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-823) Missing SAP Tool Suite

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-823?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-823. ----------------------------------- Verified > Missing SAP Tool Suite > ---------------------- > > Key: JBTIS-823 > URL: https://issues.jboss.org/browse/JBTIS-823 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.1.CR3 > Reporter: Andrej Podhradsky > Priority: Blocker > Fix For: 9.0.1.CR3 > > > The following update site > https://devstudio.redhat.com/9.0/staging/updates/integration-stack/extras... > refers to 8.0.0.Beta4 which is missing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-823) Missing SAP Tool Suite

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-823?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-823: ------------------------------------ Affects Version/s: 9.0.1.CR3 > Missing SAP Tool Suite > ---------------------- > > Key: JBTIS-823 > URL: https://issues.jboss.org/browse/JBTIS-823 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.1.CR3 > Reporter: Andrej Podhradsky > Priority: Blocker > Fix For: 9.0.1.CR3 > > > The following update site > https://devstudio.redhat.com/9.0/staging/updates/integration-stack/extras... > refers to 8.0.0.Beta4 which is missing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22647) Update code to support openshift-restclient-java changes including auth context

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22647?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-22647: --------------------------------------- Code is not in front of me but it's something in DefaultClient where it creates a clone essentially of okhttclient. -- -- Jeff Cantrill Senior Software Engineer, Red Hat Engineering OpenShift Integration Services Red Hat, Inc. *Office*: 703-748-4420 | 866-546-8970 ext. 8162420 jcantril(a)redhat.com http://www.redhat.com > Update code to support openshift-restclient-java changes including auth context > ------------------------------------------------------------------------------- > > Key: JBIDE-22647 > URL: https://issues.jboss.org/browse/JBIDE-22647 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.4.1.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ] Jeff MAURY edited comment on JBIDE-22603 at 8/3/16 10:06 AM: ------------------------------------------------------------- [~jcantrill] can you check as it seems to me that either we have a state management problem in the WatchClient or WebSocket upgrade requests are being rejected. I was able to reproduce it on Fedore using CDK 2.1 but did not get it on Windows 10. Log file [^watchers.log] was (Author: jeffmaury): [~jcantrill] can you check as it seems to me that either we have a state management problem in the WatchClient or WebSocket upgrade requests are being rejected. I was able to reproduce it on Fedore using CDK 2.1 but did not get it on Windows 10 > Sometimes multiple OpenShift watch managers are periodically created and finished > --------------------------------------------------------------------------------- > > Key: JBIDE-22603 > URL: https://issues.jboss.org/browse/JBIDE-22603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Blocker > Labels: explorer, openshift_v3 > Fix For: 4.4.1.AM3 > > Attachments: openshift_watchers.ogv, watchers.log, watchers.png > > > Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template. > !watchers.png! > It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22603: ------------------------------------ [~jcantrill] can you check as it seems to me that either we have a state management problem in the WatchClient or WebSocket upgrade requests are being rejected. I was able to reproduce it on Fedore using CDK 2.1 but did not get it on Windows 10 > Sometimes multiple OpenShift watch managers are periodically created and finished > --------------------------------------------------------------------------------- > > Key: JBIDE-22603 > URL: https://issues.jboss.org/browse/JBIDE-22603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Blocker > Labels: explorer, openshift_v3 > Fix For: 4.4.1.AM3 > > Attachments: openshift_watchers.ogv, watchers.log, watchers.png > > > Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template. > !watchers.png! > It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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