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