September 2017 - jbosstools-issues

[JBoss JIRA] (JBDS-4067) Review labels shown for software components on confirmation page

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBDS-4067?page=com.atlassian.jira.plugin.... ] Mohit Suman updated JBDS-4067: ------------------------------ Sprint: devex #138 September 2017 > Review labels shown for software components on confirmation page > ---------------------------------------------------------------- > > Key: JBDS-4067 > URL: https://issues.jboss.org/browse/JBDS-4067 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: ui > Fix For: 11.x > > > On confirmation page installer shows list of components from software stack. For most components there is detection algorithm that can find already installed components, so installer can skip install. There should be term selected for set of version for the required components: > * required; > * recommended; > * tested; > * ? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24903) Sonar: report correct test coverage (by using a build that does not use pack200)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24903?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24903: ------------------------------- Sprint: devex #138 September 2017 (was: devex #137 September 2017) > Sonar: report correct test coverage (by using a build that does not use pack200) > --------------------------------------------------------------------------------- > > Key: JBIDE-24903 > URL: https://issues.jboss.org/browse/JBIDE-24903 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: build, sonar, test, test-coverage > Fix For: 4.5.x > > Attachments: image-2017-08-29-14-07-45-069.png, image-2017-08-29-14-11-01-604.png > > > Currently our [Sonar instance|https://sonarcloud.io/dashboard?id=org.jboss.tools%3Aopenshift] erroneously reports our test coverage with 0.8% > !image-2017-08-29-14-07-45-069.png! > According to [~lhein] this is caused by the fact that we build using pack200. In Fuse Tools they added a build in jenkins just for sonar, which is *NOT* using pack200 and their [sonar analysis|https://sonarcloud.io/dashboard?id=fusetools] therefore reports their test coverage more accurately at 29% > !image-2017-08-29-14-11-01-604.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24779) Starting an OpenShift application seems to lock workspace

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24779?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24779: ------------------------------- Sprint: devex #138 September 2017 (was: devex #137 September 2017) > Starting an OpenShift application seems to lock workspace > --------------------------------------------------------- > > Key: JBIDE-24779 > URL: https://issues.jboss.org/browse/JBIDE-24779 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Mickael Istria > Assignee: Dmitrii Bocharov > Fix For: 4.5.x > > > I have an openshift application starting from the IDE and can see the progress report. For some reason (not IDE related I imagine), it's taking ages. > In the meantimes, I've tried to turn a regular project into a static web project to be able to create a server adapter, but it seems like the OpenShift Start operation is locking the workspace so my change show a "waiting for background job to complete pop-up", which is persisting as the job in the background doesn't complete. > I have the impression that the openshift start job does lock the workspace and prevents many things from being doable. If it's the case, I believe it should be changed to a regular job without any lock so it's not blocking the user. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25055) Support the profile feature in CDK server adapter

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25055?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25055: ------------------------------- Sprint: devex #138 September 2017 > Support the profile feature in CDK server adapter > ------------------------------------------------- > > Key: JBIDE-25055 > URL: https://issues.jboss.org/browse/JBIDE-25055 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.5.0.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: cdk, cdk_server_adapter_, server_adapter > Fix For: 4.5.x > > > Minishift 1.6 brought the notion of profile for running several instances of clusters. According to [~lalatendum] this will land in CDK 3.2 / Freesia > So we may extend the CDK server adapter to support that feature. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25046) Can't find CDK for registry discovery when 2 connections are defined for CDK

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25046?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25046: ------------------------------- Sprint: devex #138 September 2017 > Can't find CDK for registry discovery when 2 connections are defined for CDK > ---------------------------------------------------------------------------- > > Key: JBIDE-25046 > URL: https://issues.jboss.org/browse/JBIDE-25046 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: cdk, cdk_server_adapter_, explorer, openshift, openshift_v3 > Fix For: 4.5.x > > > EXEC: define an Openshift connection for CDK/admin > EXEC: define an Openshift connection for CDK/developer > EXEC: define a CDK3 server > EXEC: start the CDK 3 server > ASSERT: the CDK/admin OS3 connection is updated (registry not empty) > ASSERT: the CDK/developer OS3 connection is not updated (registry empty) > EXEC: on the CDK/developer OS3 connection, click the DIscover buttoon > ASSERT: the registry URL is updated, not the error dialog is displayed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25049) Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25049?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25049: ------------------------------- Sprint: devex #138 September 2017 > Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started) > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25049 > URL: https://issues.jboss.org/browse/JBIDE-25049 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.5.0.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.x > > Attachments: screenshot-1.png > > > # ASSERT: make sure that you have a minishift that does *NOT* have a docker registry. > {code} > [adietish@localhost minishift]$ ./minishift openshift registry > No information found for 'service/docker-registry' > {code} > # ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse > # ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse > # EXEC/ASSERT: make sure that your CDK/minishift server adapter is started > # EXEC: edit the OpenShift connection > # ASSERT: connection wizard shows up > # EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up > # EXEC: hit "Discover" > Result > An error dialog shows up telling you no registry provider could be found > !screenshot-1.png! > > the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4554) Replace context menu in installer with normally expected UI elements: buttons and links

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBDS-4554?page=com.atlassian.jira.plugin.... ] Mohit Suman updated JBDS-4554: ------------------------------ Sprint: devex #138 September 2017 > Replace context menu in installer with normally expected UI elements: buttons and links > --------------------------------------------------------------------------------------- > > Key: JBDS-4554 > URL: https://issues.jboss.org/browse/JBDS-4554 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.1.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: ui > > Click context menus on the installer - it’s not a functionality one would normally expect. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24990) Warning for OpenShift client > 1.1.1 required but 3.4.1 is available

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24990?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24990: ------------------------------- Sprint: devex #138 September 2017 > Warning for OpenShift client > 1.1.1 required but 3.4.1 is available > -------------------------------------------------------------------- > > Key: JBIDE-24990 > URL: https://issues.jboss.org/browse/JBIDE-24990 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Labels: oc_binary, openshift_v3, server_adapter_wizard > Fix For: 4.5.1.AM3 > > Attachments: screenshot-1.png, screenshot-2.png > > > !screenshot-2.png|thumbnail! > !screenshot-1.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24763) Some server itests are failing on Jenkins

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24763?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24763: ------------------------------- Sprint: devex #138 September 2017 (was: devex #137 September 2017) > Some server itests are failing on Jenkins > ----------------------------------------- > > Key: JBIDE-24763 > URL: https://issues.jboss.org/browse/JBIDE-24763 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.1.AM3 > > Attachments: server-itests.png > > > Here's the job: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Currently we got around 30 failures: > {code} > All Failed Tests > Test Name > Duration > Age > org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[1] 5.3 sec 1 > org.jboss.tools.as.management.itests.AS7ManagerIntegrationTest.canGetServerState[7] 76 ms 1 > org.jboss.tools.as.ui.bot.itests.parametized.server.RuntimeDetectionDuplicatesTest.duplicateRuntimes default [0] 17 sec 1 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[4] 1.7 sec 2 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[4] 5.3 sec 2 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[1] 2.3 sec 3 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[0] 4.4 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[1] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[2] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[3] 2.2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[4] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[5] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[6] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[7] 2.3 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[8] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[9] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[10] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[11] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[12] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[13] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[14] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[15] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[16] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[17] 2 sec 6 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[0] 1.7 sec 6 > org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [0] 1 min 49 sec 6 > org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [1] 1 min 43 sec 6 > org.jboss.tools.wtp.runtimes.tomcat.itests.ServerUtilTest.testUniqueServerName 2.6 sec 6 > org.jboss.tools.wtp.runtimes.tomcat.itests.TomcatDetectionTest.testTomcatDetection 0.13 sec 6 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[2] 1.7 sec 7 > {code} > Nick already shared some details in JBIDE-22799 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24111) Verify EAP 7.1 compatibility from EAP team

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24111?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24111: ------------------------------- Sprint: devex #131 April 2017, devex #138 September 2017 (was: devex #131 April 2017, devex #137 September 2017) > Verify EAP 7.1 compatibility from EAP team > ------------------------------------------ > > Key: JBIDE-24111 > URL: https://issues.jboss.org/browse/JBIDE-24111 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.4.AM1 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: eap, server > Fix For: 4.5.x > > > We should check the problems got from the EAP team. See linked issues -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 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 September 2017