September 2019 - jbosstools-issues

[JBoss JIRA] (JBIDE-26805) StacksCoreTest is failing

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26805?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26805. --------------------------------- Closing, build is back to green. > StacksCoreTest is failing > ------------------------- > > Key: JBIDE-26805 > URL: https://issues.jboss.org/browse/JBIDE-26805 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: base > Affects Versions: 4.13.0.AM1 > Environment: CentralCI > Reporter: Josef Kopriva > Priority: Major > Fix For: 4.13.0.AM1 > > > {code:java} > org.jboss.tools.stacks.core.test.StacksCoreTest.testManagerUseDefaultStacks > Stack Trace > junit.framework.AssertionFailedError > at org.jboss.tools.stacks.core.test.StacksCoreTest.testManagerUseDefaultStacks(StacksCoreTest.java:45) > org.jboss.tools.stacks.core.test.StacksCoreTest.testManagerFindsStacks > Stack Trace > junit.framework.AssertionFailedError > at org.jboss.tools.stacks.core.test.StacksCoreTest.testManagerFindsStacks(StacksCoreTest.java:37) > {code} > See: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26804) RuntimeDetectionTest is failing for jboss-as701runtime

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26804?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26804. --------------------------------- Closing, build is back to green. > RuntimeDetectionTest is failing for jboss-as701runtime > ------------------------------------------------------ > > Key: JBIDE-26804 > URL: https://issues.jboss.org/browse/JBIDE-26804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.13.0.AM1 > Environment: CentralCI > Reporter: Josef Kopriva > Priority: Minor > Fix For: 4.13.0.AM1 > > > org.jboss.tools.as.test.core.runtimedetect.RuntimeDetectionTest.testLegacyIds > Error Details > jboss-as701runtime not found. > Stack Trace > junit.framework.AssertionFailedError: jboss-as701runtime not found. > at org.jboss.tools.as.test.core.runtimedetect.RuntimeDetectionTest.testLegacyIds(RuntimeDetectionTest.java:35) > See: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23666) Update or remove quickstarts on Central Home Page

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-23666?page=com.atlassian.jira.plugi... ] André Dietisheim edited comment on JBIDE-23666 at 9/11/19 3:34 PM: ------------------------------------------------------------------- The 3 following examples, that are prominently shown in central have warnings about using outdated jdks: * HTML5: ** The compiler compliance specified is 1.6 but a JRE 1.8 is used jboss-as-kitchensink-html5-mobile Compiler Compliance JRE Compiler Compliance Problem ** Build path specifies execution environment JavaSE-1.6. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-as-kitchensink-html5-mobile Build path JRE System Library Problem * Java EE Web Project: ** Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-javaee-webapp Build path JRE System Library Problem ** The compiler compliance specified is 1.7 but a JRE 1.8 is used jboss-javaee-webapp Compiler Compliance JRE Compiler Compliance Problem * Angular JS Forge: ** Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-forge-html5 Build path JRE System Library Problem ** The compiler compliance specified is 1.7 but a JRE 1.8 is used jboss-forge-html5 Compiler Compliance JRE Compiler Compliance Problem [~jeffmaury] According to what's planned (Option C, see comments above), we'd remove those 3. What's the exact idea of {quote}and redirect user to repo with quickstarts{quote}? Furthermore, if you look into *File > New > Example... > JBoss Tools > Project Examples* there are plenty of outdated examples that use the very same outdated requirements. we should remove those, too: JBIDE-26821 was (Author: adietish): The 3 following examples, that are prominently shown in central have warnings about using outdated jdks: * HTML5: ** The compiler compliance specified is 1.6 but a JRE 1.8 is used jboss-as-kitchensink-html5-mobile Compiler Compliance JRE Compiler Compliance Problem ** Build path specifies execution environment JavaSE-1.6. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-as-kitchensink-html5-mobile Build path JRE System Library Problem * Java EE Web Project: ** Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-javaee-webapp Build path JRE System Library Problem ** The compiler compliance specified is 1.7 but a JRE 1.8 is used jboss-javaee-webapp Compiler Compliance JRE Compiler Compliance Problem * Angular JS Forge: ** Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-forge-html5 Build path JRE System Library Problem ** The compiler compliance specified is 1.7 but a JRE 1.8 is used jboss-forge-html5 Compiler Compliance JRE Compiler Compliance Problem [~jeffmaury] According to what's planned (Option C, see comments above), we'd remove those 3. What's the exact idea of {quote}and redirect user to repo with quickstarts{quote}? Furthermore, if you look into *File > New > Example... > JBoss Tools > Project Examples* there are plenty of outdated examples that use the very same outdated requirements. we should remove those, too > Update or remove quickstarts on Central Home Page > ------------------------------------------------- > > Key: JBIDE-23666 > URL: https://issues.jboss.org/browse/JBIDE-23666 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.4.3.AM1 > Environment: Red Hat JBoss Developer Studio > Version: 10.3.0.AM1 > Build id: AM1-v20161225-1238-B6761 > Build date: 20161225-1238 > Reporter: Josef Kopriva > Assignee: André Dietisheim > Priority: Critical > Fix For: 4.13.0.AM1 > > > Quickstarts on Central home page are old(links: "HTML5 Project", "AngularJS Forge", "Java EE Web Project"), so when importing these quickstarts, multiple warnings occur: > {code:java} > Description Resource Path Location Type > Build path specifies execution environment JavaSE-1.6. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-as-kitchensink-html5-mobile Build path JRE System Library Problem > Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-forge-html5 Build path JRE System Library Problem > Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-javaee-webapp Build path JRE System Library Problem > No connection specified for project. No database-specific validation will be performed. jboss-as-kitchensink-html5-mobile JPA Problem > No connection specified for project. No database-specific validation will be performed. jboss-forge-html5 JPA Problem > No connection specified for project. No database-specific validation will be performed. jboss-javaee-webapp JPA Problem > No grammar constraints (DTD or XML Schema) referenced in the document. cheatsheet.xml /jboss-forge-html5 line 1 XML Problem > No grammar constraints (DTD or XML Schema) referenced in the document. wro.xml /jboss-as-kitchensink-html5-mobile/src/main/webapp/WEB-INF line 1 XML Problem > {code} > For example HTML5 Project is downloading quickstart "jboss-as-kitchensink-html5-mobile", which is probably https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/33c4600/kit... and this quickstart is requiring Java 1.6. This quickstart can be replaced with newer from https://github.com/jboss-developer/jboss-eap-quickstarts/tree/4aa3caa/kit... -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26819) Installing Spring IDE errors, displayed alternatives wont install Spring IDE

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26819?page=com.atlassian.jira.plugi... ] André Dietisheim closed JBIDE-26819. ------------------------------------ Resolution: Rejected Closed as REJECTED given that this was already fixed in current master. > Installing Spring IDE errors, displayed alternatives wont install Spring IDE > ---------------------------------------------------------------------------- > > Key: JBIDE-26819 > URL: https://issues.jboss.org/browse/JBIDE-26819 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.Final > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.AM1 > > Attachments: image-2019-09-09-21-05-52-659.png > > > steps: > # ASSERT: have "Software/Update" tab in central opened > # EXEC: select "Spring IDE" and hit "Install/Update" > Result: > Installation cannot proceed, an alternative is searched: > !image-2019-09-09-21-05-52-659.png! > The original error is > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: Spring IDE OSGi Extension (optional) 3.9.9.201906180643-RELEASE (org.springframework.ide.eclipse.osgi.feature.feature.group 3.9.9.201906180643-RELEASE) > Missing requirement: Spring IDE Core (required) 3.9.9.201906180643-RELEASE (org.springframework.ide.eclipse.feature.feature.group 3.9.9.201906180643-RELEASE) requires 'org.eclipse.equinox.p2.iu; org.springframework.ide.eclipse.xml.namespaces.feature.feature.group 3.9.9' but it could not be found > Cannot satisfy dependency: > From: Spring IDE OSGi Extension (optional) 3.9.9.201906180643-RELEASE (org.springframework.ide.eclipse.osgi.feature.feature.group 3.9.9.201906180643-RELEASE) > To: org.eclipse.equinox.p2.iu; org.springframework.ide.eclipse.feature.feature.group 0.0.0 > {code} > No option that one may choose in the dialog allows Spring IDE to be installed. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26820) Cannot install "Red Hat Data Virtualization Development"

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26820?page=com.atlassian.jira.plugi... ] André Dietisheim closed JBIDE-26820. ------------------------------------ Resolution: Rejected closed as REJECTED given that this was already fixed > Cannot install "Red Hat Data Virtualization Development" > -------------------------------------------------------- > > Key: JBIDE-26820 > URL: https://issues.jboss.org/browse/JBIDE-26820 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.Final > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.AM1 > > Attachments: image-2019-09-09-21-30-30-997.png > > > steps: > # ASSERT: have "Software/Update" tab in central opened > # EXEC: check "Red Hat Data Virtualization Development" and hit "Install/Update" > result: > A dialog pops up telling you that "Red Hat Data Virtualization Development" is not available. > !image-2019-09-09-21-30-30-997.png! > {code} > Problems occurred while performing installation: The following connectors are not available: Red Hat Data Virtualization Development (id=org.teiid.datatools.connectivity.feature.feature.group, org.teiid.designer.feature.feature.group, org.teiid.designer.runtime.feature.feature.group, org.teiid.designer.teiid.client.feature.feature.group, site=https://devstudio.redhat.com/12/stable/updates/integration-stack/) > The following connectors are not available: Red Hat Data Virtualization Development (id=org.teiid.datatools.connectivity.feature.feature.group, org.teiid.designer.feature.feature.group, org.teiid.designer.runtime.feature.feature.group, org.teiid.designer.teiid.client.feature.feature.group, site=https://devstudio.redhat.com/12/stable/updates/integration-stack/) > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26817) link to "Get involved" shows the page for CAT that was suspended in 2016

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26817?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-26817: ------------------------------------------ also replaced urls http:// -> https:// at https://github.com/jbosstools/jbosstools-central-webpage/pull/11 > link to "Get involved" shows the page for CAT that was suspended in 2016 > ------------------------------------------------------------------------ > > Key: JBIDE-26817 > URL: https://issues.jboss.org/browse/JBIDE-26817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.Final > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.AM1 > > Attachments: image-2019-09-09-21-39-10-326.png, image-2019-09-09-21-40-21-204.png, image-2019-09-11-17-34-37-623.png > > > steps: > # ASSERT: have central opened > # EXEC: click on the link "Get involved" > !image-2019-09-09-21-39-10-326.png! > result: > browser is opened displaying the page for the [CAT program|https://tools.jboss.org/cat/] that was suspended in *2016* > !image-2019-09-09-21-40-21-204.png! -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26817) link to "Get involved" shows the page for CAT that was suspended in 2016

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26817?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26817: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-central-webpage/pull/10, https://github.com/jbosstools/jbosstools-central-webpage/pull/11 (was: https://github.com/jbosstools/jbosstools-central-webpage/pull/10) > link to "Get involved" shows the page for CAT that was suspended in 2016 > ------------------------------------------------------------------------ > > Key: JBIDE-26817 > URL: https://issues.jboss.org/browse/JBIDE-26817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.Final > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.AM1 > > Attachments: image-2019-09-09-21-39-10-326.png, image-2019-09-09-21-40-21-204.png, image-2019-09-11-17-34-37-623.png > > > steps: > # ASSERT: have central opened > # EXEC: click on the link "Get involved" > !image-2019-09-09-21-39-10-326.png! > result: > browser is opened displaying the page for the [CAT program|https://tools.jboss.org/cat/] that was suspended in *2016* > !image-2019-09-09-21-40-21-204.png! -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-756) ToolItem traversal does not fire deactivate event. [EBZ#341117]

by Eric Williams (Jira)

[ https://issues.jboss.org/browse/ERT-756?page=com.atlassian.jira.plugin.sy... ] Eric Williams reassigned ERT-756: --------------------------------- Sprint: devex #172 Sep 2019 Assignee: Eric Williams > ToolItem traversal does not fire deactivate event. [EBZ#341117] > --------------------------------------------------------------- > > Key: ERT-756 > URL: https://issues.jboss.org/browse/ERT-756 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Priority: Major > Labels: 4.14_M1, SWT, bzira > > Build Identifier: M20100909-0800 > When using tab to traverse, a ToolItem in a ToolBar does not send deactivate event to existing active control when it receives focus. > This is for Linux, on Windows a deactivate event is fired. > Reproducible: Always > Steps to Reproduce: > 1.Run the attached snippet in Linux (gtk). > 2.Tab through the the two Text controls and the ToolItem button > 3.Note that Text 2 does not receive a deactivate event until Text 1 is activated > 4. On Windows Text 2 gets a deactivate event when the toolbar button receives focus. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-756) ToolItem traversal does not fire deactivate event. [EBZ#341117]

by Friendly Jira Robot (Jira)

Friendly Jira Robot created ERT-756: --------------------------------------- Summary: ToolItem traversal does not fire deactivate event. [EBZ#341117] Key: ERT-756 URL: https://issues.jboss.org/browse/ERT-756 Project: Eclipse Release Train Issue Type: Task Components: Platform Reporter: Friendly Jira Robot Build Identifier: M20100909-0800 When using tab to traverse, a ToolItem in a ToolBar does not send deactivate event to existing active control when it receives focus. This is for Linux, on Windows a deactivate event is fired. Reproducible: Always Steps to Reproduce: 1.Run the attached snippet in Linux (gtk). 2.Tab through the the two Text controls and the ToolItem button 3.Note that Text 2 does not receive a deactivate event until Text 1 is activated 4. On Windows Text 2 gets a deactivate event when the toolbar button receives focus. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-756) ToolItem traversal does not fire deactivate event. [EBZ#341117]

by Friendly Jira Robot (Jira)

[ https://issues.jboss.org/browse/ERT-756?page=com.atlassian.jira.plugin.sy... ] Friendly Jira Robot resolved ERT-756. ------------------------------------- Resolution: Done > ToolItem traversal does not fire deactivate event. [EBZ#341117] > --------------------------------------------------------------- > > Key: ERT-756 > URL: https://issues.jboss.org/browse/ERT-756 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Priority: Major > Labels: 4.14_M1, SWT, bzira > > Build Identifier: M20100909-0800 > When using tab to traverse, a ToolItem in a ToolBar does not send deactivate event to existing active control when it receives focus. > This is for Linux, on Windows a deactivate event is fired. > Reproducible: Always > Steps to Reproduce: > 1.Run the attached snippet in Linux (gtk). > 2.Tab through the the two Text controls and the ToolItem button > 3.Note that Text 2 does not receive a deactivate event until Text 1 is activated > 4. On Windows Text 2 gets a deactivate event when the toolbar button receives focus. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2019