February 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-3592) Unable build any developed project using JBOSS

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3592?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3592: ----------------------------- > Unable build any developed project using JBOSS > ---------------------------------------------- > > Key: JBDS-3592 > URL: https://issues.jboss.org/browse/JBDS-3592 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-dependencies > Affects Versions: 9.1.0.Beta2 > Reporter: Surendhar T > > Unpacking the effective pom.xml file from .jar and inspecting it revealed it has two duplicate lines at the beginning of it because of it unable to deply in our artifactory > <?xml version="1.0" encoding="UTF-8"?> > <?xml version="1.0" encoding="UTF-8"?> > … > Removing one of them and repacking the .jar file, resulted in a successful deploy to Artifactory. > https://maven.repository.redhat.com/techpreview/all/org/jboss/logging/jbo... > https://maven.repository.redhat.com/techpreview/all/org/jboss/jboss-vfs/3... > https://maven.repository.redhat.com/techpreview/all/org/jboss/staxmapper/... > Could you please provide relevant jars by removing the errors. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3592) Unable build any developed project using JBOSS

by Surendhar T (JIRA)

[ https://issues.jboss.org/browse/JBDS-3592?page=com.atlassian.jira.plugin.... ] Surendhar T updated JBDS-3592: ------------------------------ Issue Type: Bug (was: Feature Request) > Unable build any developed project using JBOSS > ---------------------------------------------- > > Key: JBDS-3592 > URL: https://issues.jboss.org/browse/JBDS-3592 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-dependencies > Affects Versions: 9.1.0.Beta2 > Reporter: Surendhar T > > Unpacking the effective pom.xml file from .jar and inspecting it revealed it has two duplicate lines at the beginning of it because of it unable to deply in our artifactory > <?xml version="1.0" encoding="UTF-8"?> > <?xml version="1.0" encoding="UTF-8"?> > … > Removing one of them and repacking the .jar file, resulted in a successful deploy to Artifactory. > https://maven.repository.redhat.com/techpreview/all/org/jboss/logging/jbo... > https://maven.repository.redhat.com/techpreview/all/org/jboss/jboss-vfs/3... > https://maven.repository.redhat.com/techpreview/all/org/jboss/staxmapper/... > Could you please provide relevant jars by removing the errors. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3592) Unable build any developed project using JBOSS

by Surendhar T (JIRA)

[ https://issues.jboss.org/browse/JBDS-3592?page=com.atlassian.jira.plugin.... ] Surendhar T updated JBDS-3592: ------------------------------ Docs QE Status: (was: NEW) > Unable build any developed project using JBOSS > ---------------------------------------------- > > Key: JBDS-3592 > URL: https://issues.jboss.org/browse/JBDS-3592 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-dependencies > Affects Versions: 9.1.0.Beta2 > Reporter: Surendhar T > > Unpacking the effective pom.xml file from .jar and inspecting it revealed it has two duplicate lines at the beginning of it because of it unable to deply in our artifactory > <?xml version="1.0" encoding="UTF-8"?> > <?xml version="1.0" encoding="UTF-8"?> > … > Removing one of them and repacking the .jar file, resulted in a successful deploy to Artifactory. > https://maven.repository.redhat.com/techpreview/all/org/jboss/logging/jbo... > https://maven.repository.redhat.com/techpreview/all/org/jboss/jboss-vfs/3... > https://maven.repository.redhat.com/techpreview/all/org/jboss/staxmapper/... > Could you please provide relevant jars by removing the errors. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-552) create install tests for JBTIS/JBDSIS

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-552?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-552: ---------------------------------- I added a build trigger on completion of JBTIS-aggregate-discovery project build. > create install tests for JBTIS/JBDSIS > ------------------------------------- > > Key: JBTIS-552 > URL: https://issues.jboss.org/browse/JBTIS-552 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > Implement p2director install tests for JBTIS & JBDSIS to verify no missing deps in TP and no conflicting install deps (eg., different IS projects w/ conflicting singleton dependencies) > Should be based on JBT/JBDS p2director install job [1]. > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > Later we could also create a job that maps to the JBT/JBDS install-grinder job [2]. > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21670) Remove ImageStreamTag from WatchManager

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-21670: ------------------------------------- Summary: Remove ImageStreamTag from WatchManager Key: JBIDE-21670 URL: https://issues.jboss.org/browse/JBIDE-21670 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta2 Reporter: Jeff Cantrill Assignee: Jeff Cantrill Fix For: 4.3.1.CR1 Watch of ImageStreamTags is unsupported by the server and causes: {{[DEBUG] 2016-02-09 10:39:33,901 com.openshift.internal.restclient.WatchClient - WatchSocket Error org.eclipse.jetty.websocket.api.UpgradeException: Didn't switch protocols at org.eclipse.jetty.websocket.client.io.UpgradeConnection.validateResponse(UpgradeConnection.java:314) at org.eclipse.jetty.websocket.client.io.UpgradeConnection.read(UpgradeConnection.java:241) at org.eclipse.jetty.websocket.client.io.UpgradeConnection.onFillable(UpgradeConnection.java:163) at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) at java.lang.Thread.run(Thread.java:745) [DEBUG] 2016-02-09 10:39:33,902 com.openshift.internal.restclient.WatchClient - WatchSocket Error org.eclipse.jetty.websocket.api.UpgradeException: Didn't switch protocols at org.eclipse.jetty.websocket.client.io.UpgradeConnection.validateResponse(UpgradeConnection.java:314) at org.eclipse.jetty.websocket.client.io.UpgradeConnection.read(UpgradeConnection.java:241) at org.eclipse.jetty.websocket.client.io.UpgradeConnection.onFillable(UpgradeConnection.java:163) at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) at java.lang.Thread.run(Thread.java:745)}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21670) Remove ImageStreamTag from WatchManager

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21670?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-21670: ---------------------------------- Description: Watch of ImageStreamTags is unsupported by the server and causes: {{ [DEBUG] 2016-02-09 10:39:33,901 com.openshift.internal.restclient.WatchClient - WatchSocket Error org.eclipse.jetty.websocket.api.UpgradeException: Didn't switch protocols at org.eclipse.jetty.websocket.client.io.UpgradeConnection.validateResponse(UpgradeConnection.java:314) at org.eclipse.jetty.websocket.client.io.UpgradeConnection.read(UpgradeConnection.java:241) at org.eclipse.jetty.websocket.client.io.UpgradeConnection.onFillable(UpgradeConnection.java:163) at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) at java.lang.Thread.run(Thread.java:745) [DEBUG] 2016-02-09 10:39:33,902 com.openshift.internal.restclient.WatchClient - WatchSocket Error org.eclipse.jetty.websocket.api.UpgradeException: Didn't switch protocols at org.eclipse.jetty.websocket.client.io.UpgradeConnection.validateResponse(UpgradeConnection.java:314) at org.eclipse.jetty.websocket.client.io.UpgradeConnection.read(UpgradeConnection.java:241) at org.eclipse.jetty.websocket.client.io.UpgradeConnection.onFillable(UpgradeConnection.java:163) at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) at java.lang.Thread.run(Thread.java:745) }} was: Watch of ImageStreamTags is unsupported by the server and causes: {{[DEBUG] 2016-02-09 10:39:33,901 com.openshift.internal.restclient.WatchClient - WatchSocket Error org.eclipse.jetty.websocket.api.UpgradeException: Didn't switch protocols at org.eclipse.jetty.websocket.client.io.UpgradeConnection.validateResponse(UpgradeConnection.java:314) at org.eclipse.jetty.websocket.client.io.UpgradeConnection.read(UpgradeConnection.java:241) at org.eclipse.jetty.websocket.client.io.UpgradeConnection.onFillable(UpgradeConnection.java:163) at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) at java.lang.Thread.run(Thread.java:745) [DEBUG] 2016-02-09 10:39:33,902 com.openshift.internal.restclient.WatchClient - WatchSocket Error org.eclipse.jetty.websocket.api.UpgradeException: Didn't switch protocols at org.eclipse.jetty.websocket.client.io.UpgradeConnection.validateResponse(UpgradeConnection.java:314) at org.eclipse.jetty.websocket.client.io.UpgradeConnection.read(UpgradeConnection.java:241) at org.eclipse.jetty.websocket.client.io.UpgradeConnection.onFillable(UpgradeConnection.java:163) at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) at java.lang.Thread.run(Thread.java:745)}} > Remove ImageStreamTag from WatchManager > --------------------------------------- > > Key: JBIDE-21670 > URL: https://issues.jboss.org/browse/JBIDE-21670 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.1.CR1 > > > Watch of ImageStreamTags is unsupported by the server and causes: > {{ > [DEBUG] 2016-02-09 10:39:33,901 com.openshift.internal.restclient.WatchClient - WatchSocket Error > org.eclipse.jetty.websocket.api.UpgradeException: Didn't switch protocols > at org.eclipse.jetty.websocket.client.io.UpgradeConnection.validateResponse(UpgradeConnection.java:314) > at org.eclipse.jetty.websocket.client.io.UpgradeConnection.read(UpgradeConnection.java:241) > at org.eclipse.jetty.websocket.client.io.UpgradeConnection.onFillable(UpgradeConnection.java:163) > at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) > at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) > at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) > at java.lang.Thread.run(Thread.java:745) > [DEBUG] 2016-02-09 10:39:33,902 com.openshift.internal.restclient.WatchClient - WatchSocket Error > org.eclipse.jetty.websocket.api.UpgradeException: Didn't switch protocols > at org.eclipse.jetty.websocket.client.io.UpgradeConnection.validateResponse(UpgradeConnection.java:314) > at org.eclipse.jetty.websocket.client.io.UpgradeConnection.read(UpgradeConnection.java:241) > at org.eclipse.jetty.websocket.client.io.UpgradeConnection.onFillable(UpgradeConnection.java:163) > at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) > at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) > at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) > at java.lang.Thread.run(Thread.java:745) > }} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21669) Enable easy scaling of OpenShift 3 applications

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21669: ------------------------------------- Summary: Enable easy scaling of OpenShift 3 applications Key: JBIDE-21669 URL: https://issues.jboss.org/browse/JBIDE-21669 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda In Web-UI there is a spinner to set amount of running pods and we don't have something similar and user friendly in our tooling. At the moment to scale up/down an OpenShift 3 application, it is required to modify replication controller (which is a bit buggy see JBIDE-21665 and whole work flow is not quite user friendly). It would be nice to have a context menu item in context menu of a service, something like "Scale Up" enabled all the time and "Scale Down" in case there are at least 2 pods running. Or it could be "Add Pod" "Remove Pod" or something similar. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21669) Enable easy scaling of OpenShift 3 applications

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21669?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21669: ---------------------------------- Labels: explorer openshift_v3 (was: ) > Enable easy scaling of OpenShift 3 applications > ----------------------------------------------- > > Key: JBIDE-21669 > URL: https://issues.jboss.org/browse/JBIDE-21669 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: explorer, openshift_v3 > > In Web-UI there is a spinner to set amount of running pods and we don't have something similar and user friendly in our tooling. At the moment to scale up/down an OpenShift 3 application, it is required to modify replication controller (which is a bit buggy see JBIDE-21665 and whole work flow is not quite user friendly). It would be nice to have a context menu item in context menu of a service, something like "Scale Up" enabled all the time and "Scale Down" in case there are at least 2 pods running. Or it could be "Add Pod" "Remove Pod" or something similar. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-547) JBDS IS 8 and 9 contain old versions of Teiid Designer

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-547?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-547. ------------------------------ Fix Version/s: 9.0.0.Beta1 Resolution: Done Given the active release cycles of both Luna and Mars, it's possible for the older Eclipse platform (Luna) to have a more recent released set of bits than the newer Eclipse platform (Mars) because the Luna release cadence is quicker and occurs before the next scheduled Mars release. In this case we went with the best available Teiid Designer bits for the JBDSIS 9.0.0.Alpha2 (9.0.3.Final) and Luna has released a 9.0.4.Final since then. We are in the process of releasing the latest Mars Teiid Designer bits (10.0.0.Beta2). > JBDS IS 8 and 9 contain old versions of Teiid Designer > ------------------------------------------------------ > > Key: JBTIS-547 > URL: https://issues.jboss.org/browse/JBTIS-547 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Barry LaFond > Fix For: 9.0.0.Beta1 > > Attachments: teiiddes903-in-mars-904-in-luna.png > > > Should the /8.0/ site contain the same (or newer!) version of Teiid Designer than the /9.0/ site? > I see this, and it confuses me: > !teiiddes903-in-mars-904-in-luna.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-553) Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-553?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-553. ------------------------------ Fix Version/s: 4.3.0.Beta1 9.0.0.Beta1 4.3.1.Beta1-TP Resolution: Done Picked up a new graphiti and modified the meta data. QE has confirmed the resulting JBTIS target platform. Should be fixed in JBTIS 4.3.0.Beta1 (community) and JBDSIS 9.0.0.Beta1 (production). > Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71 > -------------------------------------------------------------------------------------- > > Key: JBTIS-553 > URL: https://issues.jboss.org/browse/JBTIS-553 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Reporter: Jan Richter > Assignee: Paul Leacu > Priority: Critical > Fix For: 4.3.0.Beta1, 9.0.0.Beta1, 4.3.1.Beta1-TP > > > Trying to install IS from central early access, I'm getting the following error: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > Problems downloading artifact: osgi.bundle,org.eclipse.graphiti.ui,0.13.0.v20150818-1354. > Unpacking fails because intermediate file is empty: /tmp/work8606338891825741513/p2.optimizers.incoming8698731202719996837.jar > {noformat} -- 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