June 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26573) org.jboss.ide.eclipse.archives.ui.test.bot.* failures "There are no projects in your workspace"

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26573?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26573: ------------------------------- Fix Version/s: 4.12.0.Final (was: 4.12.0.AM1) > org.jboss.ide.eclipse.archives.ui.test.bot.* failures "There are no projects in your workspace" > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-26573 > URL: https://issues.jboss.org/browse/JBIDE-26573 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.11.0.Final > Reporter: Aurélien Pupier > Assignee: Josef Kopriva > Priority: Critical > Fix For: 4.12.0.Final > > > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > {noformat} > org.jboss.ide.eclipse.archives.ui.test.bot.ViewIsPresentTest no-configuration.org.jboss.ide.eclipse.archives.ui.test.bot.ViewIsPresentTest no-configuration 7.6 sec 2 > org.jboss.ide.eclipse.archives.ui.test.bot.ArchivePreferencesTest no-configuration.org.jboss.ide.eclipse.archives.ui.test.bot.ArchivePreferencesTest no-configuration 10 sec 2 > org.jboss.ide.eclipse.archives.ui.test.bot.ArchiveViewReSwitchingTest no-configuration.org.jboss.ide.eclipse.archives.ui.test.bot.ArchiveViewReSwitchingTest no-configuration 13 sec 2 > org.jboss.ide.eclipse.archives.ui.test.bot.FolderTest no-configuration.org.jboss.ide.eclipse.archives.ui.test.bot.FolderTest no-configuration 15 sec 2 > org.jboss.ide.eclipse.archives.ui.test.bot.FilesetTest no-configuration.org.jboss.ide.eclipse.archives.ui.test.bot.FilesetTest no-configuration 18 sec 2 > org.jboss.ide.eclipse.archives.ui.test.bot.UserLibrariesFilesetTest no-configuration.org.jboss.ide.eclipse.archives.ui.test.bot.UserLibrariesFilesetTest no-configuration 21 sec 2 > org.jboss.ide.eclipse.archives.ui.test.bot.ArchivesSupportTest no-configuration.org.jboss.ide.eclipse.archives.ui.test.bot.ArchivesSupportTest no-configuration 23 sec 2 > org.jboss.ide.eclipse.archives.ui.test.bot.BuildingArchiveNode no-configuration.org.jboss.ide.eclipse.archives.ui.test.bot.BuildingArchiveNode no-configuration 26 sec 2 > org.jboss.ide.eclipse.archives.ui.test.bot.BuildingProjectTest no-configuration.org.jboss.ide.eclipse.archives.ui.test.bot.BuildingProjectTest no-configuration 29 sec 2 > org.jboss.ide.eclipse.archives.ui.test.bot.BuildingArchiveTest no-configuration.org.jboss.ide.eclipse.archives.ui.test.bot.BuildingArchiveTest no-configuration 31 sec 2 > org.jboss.ide.eclipse.archives.ui.test.bot.CreatingArchiveTest no-configuration.org.jboss.ide.eclipse.archives.ui.test.bot.CreatingArchiveTest no-configuration 34 sec 2 > org.jboss.ide.eclipse.archives.ui.test.bot.DeletingArchiveTest no-configuration.org.jboss.ide.eclipse.archives.ui.test.bot.DeletingArchiveTest no-configuration 37 sec 2 > org.jboss.ide.eclipse.archives.ui.test.bot.ModifyingArchiveTest no-configuration.org.jboss.ide.eclipse.archives.ui.test.bot.ModifyingArchiveTest no-configuration 39 sec 2 > {noformat} > all similar errors: > {noformat} > Error Message > No matching widget found with Matcher matching when all matchers match: [Matcher matching widget with the same type as or type extending class org.eclipse.swt.widgets.Tree] > class org.eclipse.swt.widgets.Composite[shell: 'data'] > class org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer$1[shell: 'data'] > class org.eclipse.swt.widgets.Composite[shell: 'data'] > class org.eclipse.swt.widgets.Composite[shell: 'data'] > class org.eclipse.swt.widgets.Tree[shell: 'data'] > class org.eclipse.swt.widgets.Composite[shell: 'data'] > class org.eclipse.swt.widgets.Composite[shell: 'data'] > class org.eclipse.swt.widgets.Link[shell: 'data'] with text 'There are no projects in your workspace. > To add a project:' > class org.eclipse.swt.widgets.Composite[shell: 'data'] > class org.eclipse.swt.widgets.Label[shell: 'data'] with text '' > class org.eclipse.ui.forms.widgets.Hyperlink[shell: 'data'] with text 'Create a Java project' > class org.eclipse.swt.widgets.Label[shell: 'data'] with text '' > class org.eclipse.ui.forms.widgets.Hyperlink[shell: 'data'] with text 'Create a project...' > class org.eclipse.swt.widgets.Label[shell: 'data'] with text '' > class org.eclipse.ui.forms.widgets.Hyperlink[shell: 'data'] with text 'Import projects...' > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26673) Dependency on org.eclipse.rse.ui 3.3 affects installation

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26673?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-26673: ------------------------------------------ A similar error is reported here: https://developer.ibm.com/mainframe/2018/02/21/rse-version-conflict-insta... [~msparrao] what is the plugin that is bringing rse 4.6 in? Still looks to me as if this isn't our but a 3rd party problem. > Dependency on org.eclipse.rse.ui 3.3 affects installation > --------------------------------------------------------- > > Key: JBIDE-26673 > URL: https://issues.jboss.org/browse/JBIDE-26673 > Project: Tools (JBoss Tools) > Issue Type: Bug > Environment: This happens on eclipse Luna and Oxygen installing from the marketplace or directly from eclipse when creating a new JBOSS server > Reporter: Manuel Parrao > Priority: Minor > Fix For: 4.12.x > > > I have a product that uses different plugins and some of them failed to be installed if JBOSS tools are installed first since JBOSS tools has a dependency on org.eclipse.rse.ui V3.3 and the other plugins I use work with org.eclipse.rse.ui V4.4 and org.eclipse.rse.ui V4.6. On the other hand if I install first the other plugins and then try to install JBOSS tools, JBOSS does not get installed due the same dependency issue. > Would it be possible to modify the manifest to accept org.eclipse.rse.ui 3.3 or later? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26651) Initiate gitlab repo for job-dsl jenkins job definition and make an initial commit

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26651?page=com.atlassian.jira.plugi... ] Ondrej Dockal resolved JBIDE-26651. ----------------------------------- Resolution: Done > Initiate gitlab repo for job-dsl jenkins job definition and make an initial commit > ---------------------------------------------------------------------------------- > > Key: JBIDE-26651 > URL: https://issues.jboss.org/browse/JBIDE-26651 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.12.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: integration-test, quality > Fix For: 4.12.0.AM1 > > > Create a new repo on our gitlab instance that will contains initial structure for job-dsl language definition for our central ci. > Create freestyle job for seeding from this repo and suggest considerable hierarchy for our jobs. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26682) Configure trigger for new openstack rhel image and have our image-provisioning job automated

by Ondrej Dockal (Jira)

Ondrej Dockal created JBIDE-26682: ------------------------------------- Summary: Configure trigger for new openstack rhel image and have our image-provisioning job automated Key: JBIDE-26682 URL: https://issues.jboss.org/browse/JBIDE-26682 Project: Tools (JBoss Tools) Issue Type: Task Components: qa Affects Versions: 4.12.x Reporter: Ondrej Dockal Assignee: Ondrej Dockal Fix For: 4.12.x -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26681) Resource ready gating mechanism implementation in groovy

by Ondrej Dockal (Jira)

Ondrej Dockal created JBIDE-26681: ------------------------------------- Summary: Resource ready gating mechanism implementation in groovy Key: JBIDE-26681 URL: https://issues.jboss.org/browse/JBIDE-26681 Project: Tools (JBoss Tools) Issue Type: Task Components: qa Affects Versions: 4.12.x Reporter: Ondrej Dockal Assignee: Ondrej Dockal Fix For: 4.12.x -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26680) Migration of Devstudio QE jenkins GUI jobs into Job DSL as part of QE - CI

by Ondrej Dockal (Jira)

Ondrej Dockal created JBIDE-26680: ------------------------------------- Summary: Migration of Devstudio QE jenkins GUI jobs into Job DSL as part of QE - CI Key: JBIDE-26680 URL: https://issues.jboss.org/browse/JBIDE-26680 Project: Tools (JBoss Tools) Issue Type: Epic Components: qa Affects Versions: 4.12.x Reporter: Ondrej Dockal Assignee: Ondrej Dockal Fix For: 4.12.x -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-719) GPG key for code signing

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/ERT-719?page=com.atlassian.jira.plugin.sy... ] Ondrej Dockal reassigned ERT-719: --------------------------------- Assignee: Mat Booth (was: Ondrej Dockal) > GPG key for code signing > ------------------------ > > Key: ERT-719 > URL: https://issues.jboss.org/browse/ERT-719 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Mat Booth > Assignee: Mat Booth > Priority: Major > Fix For: Future > > > Hi, this is related to JBDS-4740 -- allow building of flatpak applications. > I will need to GPG sign flatpak applications before users can install them. > Does jenkins know about any GPG keys for code signing? And if so, where does the keyring live? > When I ran "{{gpg --list-keys}}" during a build, to list all the keys in the default keyring location (the default location is ~/.gnupg or /home/hudson/.gnupg in this case), there was no such keyring. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9719) Deploys Teiid artifacts to deploy folder configured in JBDS

by Barry LaFond (Jira)

[ https://issues.jboss.org/browse/JBIDE-9719?page=com.atlassian.jira.plugin... ] Barry LaFond closed JBIDE-9719. ------------------------------- Resolution: Out of Date > Deploys Teiid artifacts to deploy folder configured in JBDS > ----------------------------------------------------------- > > Key: JBIDE-9719 > URL: https://issues.jboss.org/browse/JBIDE-9719 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: teiid > Reporter: Joao Viragine > Assignee: Barry LaFond > Priority: Major > > When we deploy Teiid artifacts (like Datasources, VDB), JBDS *always* deploys the artifacts to JBoss deploy folder. It should use deploy folder configured in JBDS. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11946) CLONE - CLONE - Teiid Designer N&N

by Barry LaFond (Jira)

[ https://issues.jboss.org/browse/JBIDE-11946?page=com.atlassian.jira.plugi... ] Barry LaFond closed JBIDE-11946. -------------------------------- Resolution: Out of Date > CLONE - CLONE - Teiid Designer N&N > ---------------------------------- > > Key: JBIDE-11946 > URL: https://issues.jboss.org/browse/JBIDE-11946 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: teiid > Reporter: Denis Golovin > Assignee: Barry LaFond > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4774) User creates Camel REST definition he can't start, errors are thrown.

by Brian Fitzpatrick (Jira)

[ https://issues.jboss.org/browse/JBDS-4774?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBDS-4774: ----------------------------------------- I was able to reproduce this issue after deleting default route. To fix it, you have to manually edit the Source to move the restConfiguration element ahead of the rest element. Definitely a bug. > User creates Camel REST definition he can't start, errors are thrown. > --------------------------------------------------------------------- > > Key: JBDS-4774 > URL: https://issues.jboss.org/browse/JBDS-4774 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Bug > Components: fusetools > Affects Versions: 12.11.0.GA > Environment: I'm assuming this affects all environments. > Reporter: Bruno Meseguer > Assignee: Aurélien Pupier > Priority: Minor > Fix For: 12.x > > > UI experience: > > customer/user can't run the route. > > he does not understand what he did wrong > > he doesn't know how to fix it > expected: > > REST Configuration always defined before REST operations in XML. > workaround: > > manually switch order of elements > > (or) don't delete default route before REST is defined. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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 June 2019