February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21675) Text editor of OpenShift resource should provide more information about resource

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21675?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21675: ------------------------------------------ [~fbricon] is this easy fix something you could tackle? > Text editor of OpenShift resource should provide more information about resource > -------------------------------------------------------------------------------- > > Key: JBIDE-21675 > URL: https://issues.jboss.org/browse/JBIDE-21675 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Fix For: 4.3.1.CR1 > > > When I choose Edit.. in context menu of an OpenShift resource, its open a new text editor with JSON of resource. Currently name/title of such text editor is in format "resource type : resource name" (example "Image Stream : bug-consolidator"). If I have more such editor opened, e.g. I have a staging project, testing project and production project with same resource name, it is difficult to find out to which resource the content of editor belongs (it is possible but it requires to read content and find namespace or selflink which contain project name). > It would be nice if editor of OpenShift resource would contain at least project name in its name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-558) Cannot install Fuse Data Transformation when offline

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-558: --------------------------------------- Summary: Cannot install Fuse Data Transformation when offline Key: JBTIS-558 URL: https://issues.jboss.org/browse/JBTIS-558 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 9.0.0.Beta1 Environment: JBDS 9.1.0.Beta2 + JBDS-IS 9.0.0.Beta1 EA Zip file Reporter: Andrej Podhradsky Priority: Critical Cannot install Fuse Data Transformation when offline. Cannot complete the install because one or more required items could not be found. Software being installed: JBoss Fuse Tooling Data Transformation 8.0.0.Beta1-v20160211-1659-B703 (org.jboss.tools.fuse.transformation.feature.feature.group 8.0.0.Beta1-v20160211-1659-B703) Missing requirement: org.jboss.tools.fuse.transformation.core 8.0.0.Beta1-v20160211-1659-B703 requires 'bundle javax.xml.bind 2.2.0' but it could not be found Cannot satisfy dependency: From: JBoss Fuse Tooling Data Transformation 8.0.0.Beta1-v20160211-1659-B703 (org.jboss.tools.fuse.transformation.feature.feature.group 8.0.0.Beta1-v20160211-1659-B703) To: org.jboss.tools.fuse.transformation.core [8.0.0.Beta1-v20160211-1659-B703] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-558) Cannot install Fuse Data Transformation when offline

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-558?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-558: ------------------------------------ Description: Cannot install Fuse Data Transformation when offline. {code} Cannot complete the install because one or more required items could not be found. Software being installed: JBoss Fuse Tooling Data Transformation 8.0.0.Beta1-v20160211-1659-B703 (org.jboss.tools.fuse.transformation.feature.feature.group 8.0.0.Beta1-v20160211-1659-B703) Missing requirement: org.jboss.tools.fuse.transformation.core 8.0.0.Beta1-v20160211-1659-B703 requires 'bundle javax.xml.bind 2.2.0' but it could not be found Cannot satisfy dependency: From: JBoss Fuse Tooling Data Transformation 8.0.0.Beta1-v20160211-1659-B703 (org.jboss.tools.fuse.transformation.feature.feature.group 8.0.0.Beta1-v20160211-1659-B703) To: org.jboss.tools.fuse.transformation.core [8.0.0.Beta1-v20160211-1659-B703] {code} was: Cannot install Fuse Data Transformation when offline. Cannot complete the install because one or more required items could not be found. Software being installed: JBoss Fuse Tooling Data Transformation 8.0.0.Beta1-v20160211-1659-B703 (org.jboss.tools.fuse.transformation.feature.feature.group 8.0.0.Beta1-v20160211-1659-B703) Missing requirement: org.jboss.tools.fuse.transformation.core 8.0.0.Beta1-v20160211-1659-B703 requires 'bundle javax.xml.bind 2.2.0' but it could not be found Cannot satisfy dependency: From: JBoss Fuse Tooling Data Transformation 8.0.0.Beta1-v20160211-1659-B703 (org.jboss.tools.fuse.transformation.feature.feature.group 8.0.0.Beta1-v20160211-1659-B703) To: org.jboss.tools.fuse.transformation.core [8.0.0.Beta1-v20160211-1659-B703] > Cannot install Fuse Data Transformation when offline > ---------------------------------------------------- > > Key: JBTIS-558 > URL: https://issues.jboss.org/browse/JBTIS-558 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Beta1 > Environment: JBDS 9.1.0.Beta2 + JBDS-IS 9.0.0.Beta1 EA Zip file > Reporter: Andrej Podhradsky > Priority: Critical > > Cannot install Fuse Data Transformation when offline. > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Fuse Tooling Data Transformation 8.0.0.Beta1-v20160211-1659-B703 (org.jboss.tools.fuse.transformation.feature.feature.group 8.0.0.Beta1-v20160211-1659-B703) > Missing requirement: org.jboss.tools.fuse.transformation.core 8.0.0.Beta1-v20160211-1659-B703 requires 'bundle javax.xml.bind 2.2.0' but it could not be found > Cannot satisfy dependency: > From: JBoss Fuse Tooling Data Transformation 8.0.0.Beta1-v20160211-1659-B703 (org.jboss.tools.fuse.transformation.feature.feature.group 8.0.0.Beta1-v20160211-1659-B703) > To: org.jboss.tools.fuse.transformation.core [8.0.0.Beta1-v20160211-1659-B703] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-555) No repository found when installing JBDS-IS 9.0.0.Beta1

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-555?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-555: ----------------------------------------- The problem is that the following file https://devstudio.redhat.com/9.0/staging/updates/integration-stack/earlya... refers to https://devstudio.redhat.com/9.0/staging/updates/integration-stack/9.0.0.... which is not a correct update site > No repository found when installing JBDS-IS 9.0.0.Beta1 > ------------------------------------------------------- > > Key: JBTIS-555 > URL: https://issues.jboss.org/browse/JBTIS-555 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Beta1 > Environment: JBDS 9.1.0.Beta2 > Reporter: Andrej Podhradsky > Attachments: log.txt > > > The following errors occur when installing JBDS-IS from https://devstudio.redhat.com/9.0/staging/updates/integration-stack > EDIT: when installing from https://devstudio.redhat.com/9.0/staging/updates/integration-stack/earlya... > - No repository found at https://devstudio.redhat.com/9.0/staging/updates/integration-stack/9.0.0.... > - No repository found at https://devstudio.redhat.com/9.0/staging/updates/integration-stack/9.0.0.... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21678) New Connection wizard: Getting started info is not visible by default

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21678?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21678: ------------------------------------------ [~scabanovich] is this something you could tackle, should be quite straight forward? > New Connection wizard: Getting started info is not visible by default > ---------------------------------------------------------------------- > > Key: JBIDE-21678 > URL: https://issues.jboss.org/browse/JBIDE-21678 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: default_new_conn.png, rendered_new_conn.png > > > In opened New Connection wizard there is supposed to be getting started text leading to either sign in page for OpenShift 2 or to getting started content for OpenShift 3, but it it empty by default. Upon changing e.g. server type or checking/unchecking Use default server checkbox, the text appears. Resizing window does not fix the problem. This is also happening when editing an existing OpenShift 3 connection (via context menu of a connection). > See screenshot of fresh opened New Connection wizard: > !default_new_conn.png! > and after checkbox is (un)checked or server type is changed: > !rendered_new_conn.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21685) wildfly-helloworld-ws indicates arquillian xsd is incorrect

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21685?page=com.atlassian.jira.plugi... ] Aslak Knutsen commented on JBIDE-21685: --------------------------------------- [~rob.stryker] Where is the source for the example? > wildfly-helloworld-ws indicates arquillian xsd is incorrect > ----------------------------------------------------------- > > Key: JBIDE-21685 > URL: https://issues.jboss.org/browse/JBIDE-21685 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server, upstream > Affects Versions: 4.3.1.Beta2 > Reporter: Rob Stryker > Fix For: 4.3.x > > > The following error is presented on the wildfly quickstarts 10.x branch for the wildfly-helloworld-ws project: > Multiple annotations found at this line: > - schema_reference.4: Failed to read schema document 'http://jboss.org/schema/arquillian/arquillian_1_0.xsd', because 1) could not > find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. > - cvc-elt.1: Cannot find the declaration of element 'arquillian'. > After viewing the xsd at http://jboss.org/schema/arquillian/arquillian_1_0.xsd, it's shown that the root element is `schema` rather than `xsd:schema` -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-555) No repository found when installing JBDS-IS 9.0.0.Beta1

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-555?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-555: ------------------------------------ Description: The following errors occur when installing JBDS-IS from https://devstudio.redhat.com/9.0/staging/updates/integration-stack EDIT: when installing from https://devstudio.redhat.com/9.0/staging/updates/integration-stack/earlya... - No repository found at https://devstudio.redhat.com/9.0/staging/updates/integration-stack/9.0.0.... - No repository found at https://devstudio.redhat.com/9.0/staging/updates/integration-stack/9.0.0.... was: The following errors occur when installing JBDS-IS from https://devstudio.redhat.com/9.0/staging/updates/integration-stack - No repository found at https://devstudio.redhat.com/9.0/staging/updates/integration-stack/9.0.0.... - No repository found at https://devstudio.redhat.com/9.0/staging/updates/integration-stack/9.0.0.... > No repository found when installing JBDS-IS 9.0.0.Beta1 > ------------------------------------------------------- > > Key: JBTIS-555 > URL: https://issues.jboss.org/browse/JBTIS-555 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Beta1 > Environment: JBDS 9.1.0.Beta2 > Reporter: Andrej Podhradsky > Attachments: log.txt > > > The following errors occur when installing JBDS-IS from https://devstudio.redhat.com/9.0/staging/updates/integration-stack > EDIT: when installing from https://devstudio.redhat.com/9.0/staging/updates/integration-stack/earlya... > - No repository found at https://devstudio.redhat.com/9.0/staging/updates/integration-stack/9.0.0.... > - No repository found at https://devstudio.redhat.com/9.0/staging/updates/integration-stack/9.0.0.... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21678) New Connection wizard: Getting started info is not visible by default

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21678?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21678: ------------------------------------- Fix Version/s: 4.3.1.CR1 > New Connection wizard: Getting started info is not visible by default > ---------------------------------------------------------------------- > > Key: JBIDE-21678 > URL: https://issues.jboss.org/browse/JBIDE-21678 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: default_new_conn.png, rendered_new_conn.png > > > In opened New Connection wizard there is supposed to be getting started text leading to either sign in page for OpenShift 2 or to getting started content for OpenShift 3, but it it empty by default. Upon changing e.g. server type or checking/unchecking Use default server checkbox, the text appears. Resizing window does not fix the problem. This is also happening when editing an existing OpenShift 3 connection (via context menu of a connection). > See screenshot of fresh opened New Connection wizard: > !default_new_conn.png! > and after checkbox is (un)checked or server type is changed: > !rendered_new_conn.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20540) Upstream WTP bundled xsd using relative path for ejb-jar_3_1.xsd

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20540?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20540: ------------------------------------- The upstream error was closed as a duplicate. Please see instead https://bugzilla.redhat.com/show_bug.cgi?id=1192591 > Upstream WTP bundled xsd using relative path for ejb-jar_3_1.xsd > ---------------------------------------------------------------- > > Key: JBIDE-20540 > URL: https://issues.jboss.org/browse/JBIDE-20540 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > See bug as described here: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=476274 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20540) Upstream WTP bundled xsd using relative path for ejb-jar_3_1.xsd

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20540?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20540: ------------------------------------- Need to verify https://bugzilla.redhat.com/show_bug.cgi?id=1192591 actually fixed THIS issue, and not just a related issue. > Upstream WTP bundled xsd using relative path for ejb-jar_3_1.xsd > ---------------------------------------------------------------- > > Key: JBIDE-20540 > URL: https://issues.jboss.org/browse/JBIDE-20540 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > See bug as described here: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=476274 -- 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