February 2019 - jbosstools-issues

[JBoss JIRA] (JBDS-4710) Central page is not showing proper content after page reload

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4710?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4710: ----------------------------- Fix Version/s: 12.11.0.AM1 (was: 12.10.0.AM1) > Central page is not showing proper content after page reload > ------------------------------------------------------------ > > Key: JBDS-4710 > URL: https://issues.jboss.org/browse/JBDS-4710 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 12.0.0.AM3 > Reporter: Vojtech Prusa > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 12.11.0.AM1 > > Attachments: image-2018-06-19-10-04-56-516.png, image-2018-06-19-10-06-27-472.png, screenshot-1.png, screenshot-2.png > > > Relaoding the central page (Getting Started tab) does not load content for project examples. > Jenkins itests fails as well > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/central.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-704) Bring Chain Completion To JDT (From Recommenders)

by Roland Grunberg (Jira)

[ https://issues.jboss.org/browse/ERT-704?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg updated ERT-704: -------------------------------- Sprint: devex #161 January 2019, devex #162 February 2019 (was: devex #161 January 2019) > Bring Chain Completion To JDT (From Recommenders) > ------------------------------------------------- > > Key: ERT-704 > URL: https://issues.jboss.org/browse/ERT-704 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Roland Grunberg > Assignee: Roland Grunberg > Priority: Major > > See http://eclip.se/544108 > Chain Completion could be brought into JDT. The benefit would be that any Eclipse installation containing JDT would benefit users without the need for them to install, or locate the Code Recommenders plugins. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-703) Contributing Non-Compiler Issues Into JDT

by Roland Grunberg (Jira)

[ https://issues.jboss.org/browse/ERT-703?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg updated ERT-703: -------------------------------- Sprint: devex #161 January 2019, devex #162 February 2019 (was: devex #161 January 2019) > Contributing Non-Compiler Issues Into JDT > ----------------------------------------- > > Key: ERT-703 > URL: https://issues.jboss.org/browse/ERT-703 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Roland Grunberg > Assignee: Roland Grunberg > Priority: Major > > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=543713#c0 for background. > While many issues are found and reported in the internal compiler AST code, (eg. org.eclipse.jdt.internal.compiler.ast.Statement#analyseCode(..)), we need a way to report non-compiler issues (eg. style, bad practice, correctness, performance) as does SpotBugs. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26398) Forge New and Noteworthy for 4.10.0.AM1

by George Gastaldi (Jira)

[ https://issues.jboss.org/browse/JBIDE-26398?page=com.atlassian.jira.plugi... ] George Gastaldi closed JBIDE-26398. ----------------------------------- Resolution: Rejected > Forge New and Noteworthy for 4.10.0.AM1 > ---------------------------------------------------- > > Key: JBIDE-26398 > URL: https://issues.jboss.org/browse/JBIDE-26398 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Critical > Labels: task > Fix For: 4.11.0.AM1 > > > George Gastaldi, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Forge JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Forge, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Forge by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26391 #comment Create N&N for Forge 4.10.0.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Forge for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4735) Central projects Wizard sometimes fails to open

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBDS-4735?page=com.atlassian.jira.plugin.... ] Zbyněk Červinka edited comment on JBDS-4735 at 2/21/19 10:01 AM: ----------------------------------------------------------------- I was also able to reproduce the this issue on: - Fedora 29, JDK8, OpenStack, AM1-v20190220-1130-B4104 Steps to reproduce: a) Install devstudio b) Clone integration-tests repository (https://github.com/jbosstools/jbosstools-integration-tests) c) Import the repository in devstudio (import existing maven project) d) wait 30 min with open devstudio, do nothing with the devstudio e) issue will appear was (Author: zcervink): I was also able to reproduce the this issue: - Fedora 29, JDK8, OpenStack, AM1-v20190220-1130-B4104 - right now I know only the fact, that to reproduce this issue it is not enough to run just the devstudio and work with the central - I have added 3 WildFly, imported the integration tests maven repository and performed "mvn clean install" in the cloned repository - now I am working on minimalize the "steps to reproduce" just to necesary steps > Central projects Wizard sometimes fails to open > ----------------------------------------------- > > Key: JBDS-4735 > URL: https://issues.jboss.org/browse/JBDS-4735 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 12.9.0.GA > Environment: manually Fedora 28, automation > Reporter: Vojtech Prusa > Assignee: Jeff MAURY > Priority: Major > Fix For: 12.11.0.AM1 > > Attachments: central.tar.gz, image-2018-10-17-09-24-31-555.png, screenshot-1.png > > > Sometimes central examples wizards fail to load and modal dialog is shown instead (screen attached). > Nothing in Error log view. > Restarting devstudio solves the issue. > Adding screen and central tar of: > devstudio-12.9.0.GA-v20180928-1629-B3448/workspaces/workspace/.metadata/.plugins/org.jboss.tools.central/central -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26555) PR checks fail bcs of jenkins

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26555?page=com.atlassian.jira.plugi... ] Josef Kopriva resolved JBIDE-26555. ----------------------------------- Resolution: Done > PR checks fail bcs of jenkins > ----------------------------- > > Key: JBIDE-26555 > URL: https://issues.jboss.org/browse/JBIDE-26555 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.10.0.AM1 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Priority: Blocker > Labels: build, github, pull_request, sonar > Fix For: 4.11.0.AM1 > > > Latest PRs in github are not built successfully on jenkins any more and seem to point at sonar. > This also matches the fact that we didnt see any sonar report any more for quite some time. > ex. https://github.com/jbosstools/jbosstools-openshift/pull/1830 is red in [jenkins build #1967|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstools-openshift-Pull-Request/1967] with the following output: > {code} > [ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.3.0.603:sonar (default-cli) on project openshift: > Error 404 on https://sonarcloud.io/api/sources/hash?key=org.jboss.tools%3Aopenshift%3A... : {"errors":[{"msg":"Component key 'org.jboss.tools:openshift:plugins/org.jboss.tools.openshift.common.ui/src/org/jboss/tools/openshift/internal/common/ui/utils/OCCommandUtils.java' not found"}]} -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.3.0.603:sonar (default-cli) on project openshift: Error 404 on https://sonarcloud.io/api/sources/hash?key=org.jboss.tools%3Aopenshift%3A... : {"errors":[{"msg":"Component key 'org.jboss.tools:openshift:plugins/org.jboss.tools.openshift.common.ui/src/org/jboss/tools/openshift/internal/common/ui/utils/OCCommandUtils.java' not found"}]} > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26555) PR checks fail bcs of jenkins

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26555?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26555: ---------------------------------- Component/s: common server > PR checks fail bcs of jenkins > ----------------------------- > > Key: JBIDE-26555 > URL: https://issues.jboss.org/browse/JBIDE-26555 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common, openshift, server > Affects Versions: 4.10.0.AM1 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Priority: Blocker > Labels: build, github, pull_request, sonar > Fix For: 4.11.0.AM1 > > > Latest PRs in github are not built successfully on jenkins any more and seem to point at sonar. > This also matches the fact that we didnt see any sonar report any more for quite some time. > ex. https://github.com/jbosstools/jbosstools-openshift/pull/1830 is red in [jenkins build #1967|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstools-openshift-Pull-Request/1967] with the following output: > {code} > [ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.3.0.603:sonar (default-cli) on project openshift: > Error 404 on https://sonarcloud.io/api/sources/hash?key=org.jboss.tools%3Aopenshift%3A... : {"errors":[{"msg":"Component key 'org.jboss.tools:openshift:plugins/org.jboss.tools.openshift.common.ui/src/org/jboss/tools/openshift/internal/common/ui/utils/OCCommandUtils.java' not found"}]} -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.3.0.603:sonar (default-cli) on project openshift: Error 404 on https://sonarcloud.io/api/sources/hash?key=org.jboss.tools%3Aopenshift%3A... : {"errors":[{"msg":"Component key 'org.jboss.tools:openshift:plugins/org.jboss.tools.openshift.common.ui/src/org/jboss/tools/openshift/internal/common/ui/utils/OCCommandUtils.java' not found"}]} > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26555) PR checks fail bcs of jenkins

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26555?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-26555: --------------------------------------- PR decorations from sonarcloud is working for jbosstools-server, jbosstools-openshift, jbosstools-base. The main problem was with sonar parameters in jobs and also settings of triggers in sonar build jobs. Example settings for PR check job: {code:java} clean verify sonar:sonar -Dsonar.host.url=https://sonarcloud.io -Dsonar.organization=default -Dsonar.projectKey=org.jboss.tools:openshift -Dsonar.login= -Dsonar.pullrequest.github.token.secured= -Dsonar.pullrequest.github.endpoint=https://api.github.com/ -Dsonar.pullrequest.github.repository=jbosstools/jbosstools-openshift -Dsonar.pullrequest.provider=GitHub -Dsonar.pullrequest.key=${ghprbPullId} -Dsonar.pullrequest.branch=${ghprbSourceBranch} -Dsonar.pullrequest.base=master -Dsonar.scm.provider=git -U -fae -e -X {code} Example parameters for build: {code:java} clean verify sonar:sonar ${MAVEN_FLAGS} -Dsonar.projectKey=org.jboss.tools:openshift -Dsonar.organization=default -Dsonar.host.url=https://sonarcloud.io -Dsonar.login= {code} > PR checks fail bcs of jenkins > ----------------------------- > > Key: JBIDE-26555 > URL: https://issues.jboss.org/browse/JBIDE-26555 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.10.0.AM1 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Priority: Blocker > Labels: build, github, pull_request, sonar > Fix For: 4.11.0.AM1 > > > Latest PRs in github are not built successfully on jenkins any more and seem to point at sonar. > This also matches the fact that we didnt see any sonar report any more for quite some time. > ex. https://github.com/jbosstools/jbosstools-openshift/pull/1830 is red in [jenkins build #1967|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstools-openshift-Pull-Request/1967] with the following output: > {code} > [ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.3.0.603:sonar (default-cli) on project openshift: > Error 404 on https://sonarcloud.io/api/sources/hash?key=org.jboss.tools%3Aopenshift%3A... : {"errors":[{"msg":"Component key 'org.jboss.tools:openshift:plugins/org.jboss.tools.openshift.common.ui/src/org/jboss/tools/openshift/internal/common/ui/utils/OCCommandUtils.java' not found"}]} -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.3.0.603:sonar (default-cli) on project openshift: Error 404 on https://sonarcloud.io/api/sources/hash?key=org.jboss.tools%3Aopenshift%3A... : {"errors":[{"msg":"Component key 'org.jboss.tools:openshift:plugins/org.jboss.tools.openshift.common.ui/src/org/jboss/tools/openshift/internal/common/ui/utils/OCCommandUtils.java' not found"}]} > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4735) Central projects Wizard sometimes fails to open

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBDS-4735?page=com.atlassian.jira.plugin.... ] Zbyněk Červinka commented on JBDS-4735: --------------------------------------- I was also able to reproduce the this issue: - Fedora 29, JDK8, OpenStack, AM1-v20190220-1130-B4104 - right now I know only the fact, that to reproduce this issue it is not enough to run just the devstudio and work with the central - I have added 3 WildFly, imported the integration tests maven repository and performed "mvn clean install" in the cloned repository - now I am working on minimalize the "steps to reproduce" just to necesary steps > Central projects Wizard sometimes fails to open > ----------------------------------------------- > > Key: JBDS-4735 > URL: https://issues.jboss.org/browse/JBDS-4735 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 12.9.0.GA > Environment: manually Fedora 28, automation > Reporter: Vojtech Prusa > Assignee: Jeff MAURY > Priority: Major > Fix For: 12.11.0.AM1 > > Attachments: central.tar.gz, image-2018-10-17-09-24-31-555.png, screenshot-1.png > > > Sometimes central examples wizards fail to load and modal dialog is shown instead (screen attached). > Nothing in Error log view. > Restarting devstudio solves the issue. > Adding screen and central tar of: > devstudio-12.9.0.GA-v20180928-1629-B3448/workspaces/workspace/.metadata/.plugins/org.jboss.tools.central/central -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-711) setTabs method in Text widget is ignored when style includes SWT.SINGLE [EBZ#436085]

by Eric Williams (Jira)

[ https://issues.jboss.org/browse/ERT-711?page=com.atlassian.jira.plugin.sy... ] Eric Williams resolved ERT-711. ------------------------------- Resolution: Done > setTabs method in Text widget is ignored when style includes SWT.SINGLE [EBZ#436085] > ------------------------------------------------------------------------------------ > > Key: ERT-711 > URL: https://issues.jboss.org/browse/ERT-711 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Priority: Major > Labels: 4.12, SWT, bzira > > Creating a text widget with the style flag set to SWT.SINGLE, means that the setTabs method or at least the setTabStops method it calls) is ignored. > > Text txtInput = new Text(inputHolder, SWT.SINGLE); > txtInput.setTabs(4); > txtInput.addTraverseListener(new TraverseListener() { > //code to ignore traverses > }); > results in tabs still being shown as equal to 8 spaces. > This is coming from the "if ((style & SWT.SINGLE) != 0) return;" line in the setTabStops method of the gtk Text widget. In the win32 version of the widget there is no such check (and may explain the worksforme resolution of bug #34805) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 2019