August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3980) Staging update site advertises old latest build

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3980?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3980: -------------------------------- > Staging update site advertises old latest build > ----------------------------------------------- > > Key: JBDS-3980 > URL: https://issues.jboss.org/browse/JBDS-3980 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Minor > Fix For: 10.1.0.AM2 > > > Staging updatesite > https://devstudio.redhat.com/10.0/staging/updates/ > still shows 10.0.0.GA-b as latest build. It's just this string that is outdated, the build itself is up to date. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3980) Staging update site advertises old latest build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3980?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3980: ----------------------------- > Staging update site advertises old latest build > ----------------------------------------------- > > Key: JBDS-3980 > URL: https://issues.jboss.org/browse/JBDS-3980 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Minor > Fix For: 10.1.0.AM2 > > > Staging updatesite > https://devstudio.redhat.com/10.0/staging/updates/ > still shows 10.0.0.GA-b as latest build. It's just this string that is outdated, the build itself is up to date. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3980) Staging update site advertises old latest build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3980?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3980: ----------------------------- Fix Version/s: 10.1.0.AM2 > Staging update site advertises old latest build > ----------------------------------------------- > > Key: JBDS-3980 > URL: https://issues.jboss.org/browse/JBDS-3980 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Minor > Fix For: 10.1.0.AM2 > > > Staging updatesite > https://devstudio.redhat.com/10.0/staging/updates/ > still shows 10.0.0.GA-b as latest build. It's just this string that is outdated, the build itself is up to date. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22887) Update Docker Tooling in DevStudio

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-22887: ------------------------------------- Summary: Update Docker Tooling in DevStudio Key: JBIDE-22887 URL: https://issues.jboss.org/browse/JBIDE-22887 Project: Tools (JBoss Tools) Issue Type: Task Components: docker, target-platform Reporter: Josef Kopriva Please update Docker Tooling in DevStudio: in latest nightly build of DevStudio(Build id: AM3-v20160805-0433-B5701) is version of Docker Tooling from June. Could affect OpenShift: [~fbricon] [~adietish] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22887) Update Docker Tooling in DevStudio

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22887?page=com.atlassian.jira.plugi... ] Josef Kopriva reassigned JBIDE-22887: ------------------------------------- Assignee: Nick Boldt > Update Docker Tooling in DevStudio > ---------------------------------- > > Key: JBIDE-22887 > URL: https://issues.jboss.org/browse/JBIDE-22887 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: docker, target-platform > Reporter: Josef Kopriva > Assignee: Nick Boldt > > Please update Docker Tooling in DevStudio: in latest nightly build of DevStudio(Build id: AM3-v20160805-0433-B5701) is version of Docker Tooling from June. > Could affect OpenShift: [~fbricon] [~adietish] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22784) Create integration tests PR check job for docker

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22784?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-22784. --------------------------------- Resolution: Done Docker Tooling is upstream project and repository is not located on GitHub. > Create integration tests PR check job for docker > ------------------------------------------------ > > Key: JBIDE-22784 > URL: https://issues.jboss.org/browse/JBIDE-22784 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Josef Kopriva > Fix For: 4.4.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-825) Fix UDFImport test

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/JBTIS-825?page=com.atlassian.jira.plugin.... ] Matus Makovy updated JBTIS-825: ------------------------------- Component/s: QE teiid > Fix UDFImport test > ------------------ > > Key: JBTIS-825 > URL: https://issues.jboss.org/browse/JBTIS-825 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.3.1.Final > Reporter: Matus Makovy > Assignee: Matus Makovy > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-825) Fix UDFImport test

by Matus Makovy (JIRA)

Matus Makovy created JBTIS-825: ---------------------------------- Summary: Fix UDFImport test Key: JBTIS-825 URL: https://issues.jboss.org/browse/JBTIS-825 Project: JBoss Tools Integration Stack Issue Type: Bug Affects Versions: 4.3.1.Final Reporter: Matus Makovy Assignee: Matus Makovy Fix For: 4.3.1.Final -- 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 Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22603: --------------------------------------- Not sure what happened, but today I was not able to reproduce this. My CDK instance gone wild so I had to destroy it and set up again. After new running of CDK OpenShift with latest devstudio I am not able to reproduce issue. Build ID AM3-v20160804-1738-B5697. I tried also build from 2016-07-29 and I was not able to reproduce either. Weird thing is, I destroyed and started CDK since this issue has been created for several times and this is first time it is working. > 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-22886) Unknown component error when using http://xmlns.jcp.org/jsf/composite instead of http://java.sun.com/jsf/composite

by Karl Nicholas (JIRA)

Karl Nicholas created JBIDE-22886: ------------------------------------- Summary: Unknown component error when using http://xmlns.jcp.org/jsf/composite instead of http://java.sun.com/jsf/composite Key: JBIDE-22886 URL: https://issues.jboss.org/browse/JBIDE-22886 Project: Tools (JBoss Tools) Issue Type: Bug Components: bean-validation, jsf, jsp/jsf/xml/html-source-editing Affects Versions: 4.3.0.Final Environment: JBoss Developer Studio 9.0.1.GA. Windows 10. Java 8. Reporter: Karl Nicholas 1. Create a JSF 2.2 KickStart project with WildFly target server. 2. Create a composite component "mycomp.xhtml" 4. Import composite component with http://xmlns.jcp.org/jsf/composite/mycomp"> 5. FAILURE: Unknown composite component "mycomp" in validation. 6. change to Import composite component with http://java.sun.com/jsf/composite/mycomp"> 7. No validation, unknown composite component warning. -- 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