October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19506: ------------------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Connection wizard, Connection: should have unit tests > ------------------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.4.2.AM3 > > Original Estimate: 2 days > Time Spent: 3 days > Remaining Estimate: 3 days > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23005) Server Adapter: Stuck on creating/publishing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23005?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23005: ------------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.2.AM2) > Server Adapter: Stuck on creating/publishing > -------------------------------------------- > > Key: JBIDE-23005 > URL: https://issues.jboss.org/browse/JBIDE-23005 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.2.AM3 > > Attachments: stucked_server_adapter > > > When I am trying to create a new OpenShift 3 server adapter, many times creation does not work. Server get stucked at publishing and there is a hanging job Check module status for server eap-app at OpenShift... I am using CDK OpenShift and build an application on eap 6.4 template with kitchensink context_dir. Connection is not established. While this is happening (job is hanging) there is no error in error log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23131) Integration tests: move openshift integration tests to jbosstools/openshift repo

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23131?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23131: ------------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.2.AM2) Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Integration tests: move openshift integration tests to jbosstools/openshift repo > -------------------------------------------------------------------------------- > > Key: JBIDE-23131 > URL: https://issues.jboss.org/browse/JBIDE-23131 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration-test > Fix For: 4.4.2.AM3 > > Original Estimate: 1 day > Time Spent: 4 hours > Remaining Estimate: 4 hours > > we need to move jbosstools/openshift integration tests from their [repo|https://github.com/jbosstools/jbosstools-integration-tests] to the jbosstools/openshift tools [repo|https://github.com/jbosstools/jbosstools-openshift] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23343) Arquillian New and Noteworthy for 4.4.2.AM2

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23343?page=com.atlassian.jira.plugi... ] Snjezana Peco resolved JBIDE-23343. ----------------------------------- Resolution: Rejected No changes for N&N. > Arquillian New and Noteworthy for 4.4.2.AM2 > --------------------------------------------------- > > Key: JBIDE-23343 > URL: https://issues.jboss.org/browse/JBIDE-23343 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Jeff MAURY > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.4.2.AM2 > > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Arquillian 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 Arquillian, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Arquillian 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 'JBIDE-56789 #comment Create N&N for Arquillian4.4.2.AM2 #close', 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 Arquillian for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23343) Arquillian New and Noteworthy for 4.4.2.AM2

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23343?page=com.atlassian.jira.plugi... ] Snjezana Peco closed JBIDE-23343. --------------------------------- > Arquillian New and Noteworthy for 4.4.2.AM2 > --------------------------------------------------- > > Key: JBIDE-23343 > URL: https://issues.jboss.org/browse/JBIDE-23343 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Jeff MAURY > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.4.2.AM2 > > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Arquillian 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 Arquillian, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Arquillian 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 'JBIDE-56789 #comment Create N&N for Arquillian4.4.2.AM2 #close', 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 Arquillian for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23166) MBean Stubs New Wizard cannot be open

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23166?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23166. --------------------------------- Resolution: Done It was an attempt 9 years ago to make a wizard for creating mbeans. It was extremely old, did not follow current expectations, made lots of classes that probably didn't need to be made, and generally didn't work as any user would expect. It was then removed. > MBean Stubs New Wizard cannot be open > ------------------------------------- > > Key: JBIDE-23166 > URL: https://issues.jboss.org/browse/JBIDE-23166 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.1.Final > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.2.AM2 > > Attachments: mbinstubs.gif, screenshot-1.png > > > It just throws exception below > {code}The selected wizard could not be started. > Plug-in org.jboss.ide.eclipse.as.ui.mbeans was unable to load class org.jboss.ide.eclipse.as.ui.mbeans.wizards.NewMBeanWizard. > org.jboss.ide.eclipse.as.ui.mbeans.wizards.NewMBeanWizard cannot be found by org.jboss.ide.eclipse.as.ui.mbeans_3.2.1.v20160607-2122{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4112) create verification test to ensure that we never point a GA release at snapshot or staging URLs in ide-config.properties

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4112?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4112: -------------------------------- Assignee: Nick Boldt > create verification test to ensure that we never point a GA release at snapshot or staging URLs in ide-config.properties > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-4112 > URL: https://issues.jboss.org/browse/JBDS-4112 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 10.1.0.GA, 10.2.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM3 > > > As reported in https://developer.jboss.org/message/964029#964029 it seems there may have been a situation where a user installed devstudio 10.1.0.GA from the installer jar, but then using Central got the staging/snapshot URLs into their Available Update Sites, which then caused them to be prompted to update to 10.2. > Mixing an AM1 staging build into a .GA stable build should not happen. > We need a better test/check to ensure that if GA is live, its ide-config.properties content NEVER points to the future snapshot/staging content. > This testing could be part of the staging/release guide, but could also be run as a Jenkins job to check at intervals: > * ide-config.properties: URLs exist, are valid, don't 404, don't mismatch content > * foundation plugin / devstudio version plugin have correct version (eg., can't still be GA after GA is live) - see https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... job -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4112) create verification test to ensure that we never point a GA release at snapshot or staging URLs in ide-config.properties

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4112?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4112: ----------------------------- Fix Version/s: 10.2.0.AM3 > create verification test to ensure that we never point a GA release at snapshot or staging URLs in ide-config.properties > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-4112 > URL: https://issues.jboss.org/browse/JBDS-4112 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 10.1.0.GA, 10.2.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM3 > > > As reported in https://developer.jboss.org/message/964029#964029 it seems there may have been a situation where a user installed devstudio 10.1.0.GA from the installer jar, but then using Central got the staging/snapshot URLs into their Available Update Sites, which then caused them to be prompted to update to 10.2. > Mixing an AM1 staging build into a .GA stable build should not happen. > We need a better test/check to ensure that if GA is live, its ide-config.properties content NEVER points to the future snapshot/staging content. > This testing could be part of the staging/release guide, but could also be run as a Jenkins job to check at intervals: > * ide-config.properties: URLs exist, are valid, don't 404, don't mismatch content > * foundation plugin / devstudio version plugin have correct version (eg., can't still be GA after GA is live) - see https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... job -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4112) create verification test to ensure that we never point a GA release at snapshot or staging URLs in ide-config.properties

by Nick Boldt (JIRA)

Nick Boldt created JBDS-4112: -------------------------------- Summary: create verification test to ensure that we never point a GA release at snapshot or staging URLs in ide-config.properties Key: JBDS-4112 URL: https://issues.jboss.org/browse/JBDS-4112 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: build Affects Versions: 10.2.0.AM1, 10.1.0.GA Reporter: Nick Boldt As reported in https://developer.jboss.org/message/964029#964029 it seems there may have been a situation where a user installed devstudio 10.1.0.GA from the installer jar, but then using Central got the staging/snapshot URLs into their Available Update Sites, which then caused them to be prompted to update to 10.2. Mixing an AM1 staging build into a .GA stable build should not happen. We need a better test/check to ensure that if GA is live, its ide-config.properties content NEVER points to the future snapshot/staging content. This testing could be part of the staging/release guide, but could also be run as a Jenkins job to check at intervals: * ide-config.properties: URLs exist, are valid, don't 404, don't mismatch content * foundation plugin / devstudio version plugin have correct version (eg., can't still be GA after GA is live) - see https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... job -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23155) tests: sonar should report test coverage

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23155?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23155: ------------------------------------- Description: I'd be great if our sonar instance at sonarqube.com would report test coverage. Docs are here: http://docs.sonarqube.org/display/PLUG/Code+Coverage+by+Unit+Tests+for+Ja... Just to file similar instruments (findbug and error-prone): we also can have a look at Eclipse Che experience in this question: https://github.com/eclipse/che/wiki/Development-Workflow#validate-your-ch... was: I'd be great if our sonar instance at sonarqube.com would report test coverage. Docs are here: http://docs.sonarqube.org/display/PLUG/Code+Coverage+by+Unit+Tests+for+Ja... > tests: sonar should report test coverage > ---------------------------------------- > > Key: JBIDE-23155 > URL: https://issues.jboss.org/browse/JBIDE-23155 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.x > > > I'd be great if our sonar instance at sonarqube.com would report test coverage. > Docs are here: http://docs.sonarqube.org/display/PLUG/Code+Coverage+by+Unit+Tests+for+Ja... > Just to file similar instruments (findbug and error-prone): we also can have a look at Eclipse Che experience in this question: https://github.com/eclipse/che/wiki/Development-Workflow#validate-your-ch... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016