August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24822) Javascript New and Noteworthy for 4.5.1.AM1

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24822?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-24822. ------------------------------ Resolution: Rejected > Javascript New and Noteworthy for 4.5.1.AM1 > --------------------------------------------------- > > Key: JBIDE-24822 > URL: https://issues.jboss.org/browse/JBIDE-24822 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: javascript, nodejs > Reporter: Jeff MAURY > Assignee: Victor Rubezhny > Priority: Critical > Fix For: 4.5.1.AM1 > > > Victor Rubezhny, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Javascript 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 Javascript, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Javascript 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-24806 #comment Create N&N for Javascript 4.5.1.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 Javascript for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24501) Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24501?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-24501: --------------------------------------- I have tried it with the latest devstudio, but I get the same results as [~rhopp] with the same exception and missing image: {code:java} com.spotify.docker.client.exceptions.ImageNotFoundException: Image not found: 172.30.1.1:5000/test/hola:latest at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1330) at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImageInfo(DockerConnection.java:896) at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.lookupImageMetadata(DeployImageWizardModel.java:655) at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:354) at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) Caused by: com.spotify.docker.client.exceptions.DockerRequestException: Request error: GET https://192.168.42.121:2376/images/172.30.1.1:5000/test/hola:latest/json: 404 at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:2084) at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:2023) at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1326) ... 5 more Caused by: javax.ws.rs.NotFoundException: HTTP 404 Not Found at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:1008) at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:816) at org.glassfish.jersey.client.JerseyInvocation.access$700(JerseyInvocation.java:92) at org.glassfish.jersey.client.JerseyInvocation$5.completed(JerseyInvocation.java:773) at org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:198) at org.glassfish.jersey.client.ClientRuntime.access$300(ClientRuntime.java:79) at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:180) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) at org.glassfish.jersey.internal.Errors.process(Errors.java:315) at org.glassfish.jersey.internal.Errors.process(Errors.java:297) at org.glassfish.jersey.internal.Errors.process(Errors.java:267) at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:340) at org.glassfish.jersey.client.ClientRuntime$3.run(ClientRuntime.java:210) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) {code} [~jeffmaury] WDYT? > Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-24501 > URL: https://issues.jboss.org/browse/JBIDE-24501 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.Final > > Attachments: image-2017-05-23-12-00-51-733.png, image-2017-05-23-12-07-14-028.png, image-2017-05-23-12-10-06-694.png, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24828) Server New and Noteworthy for 4.5.1.AM1

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24828?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-24828. ------------------------------ Resolution: Rejected > Server New and Noteworthy for 4.5.1.AM1 > --------------------------------------------------- > > Key: JBIDE-24828 > URL: https://issues.jboss.org/browse/JBIDE-24828 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.5.1.AM1 > > > Rob Stryker, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Server 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 Server, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Server 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-24806 #comment Create N&N for Server 4.5.1.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 Server for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24896) Cannot start any JBoss server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24896?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24896: --------------------------------------- At least the first job is now down to 6 failures from 100. Not ideal, but much better: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Cannot start any JBoss server > ----------------------------- > > Key: JBIDE-24896 > URL: https://issues.jboss.org/browse/JBIDE-24896 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.1.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.5.1.AM2 > > > When I try to start any server such as WildFly or EAP 6/7, I immediately get a NPE: > {code} > An internal error occurred during: "Starting WildFly 10.1". > java.lang.NullPointerException > {code} > {code} > An internal error occurred during: "Starting WildFly 10.1". > java.lang.NullPointerException > at org.jboss.ide.eclipse.as.core.extensions.descriptors.XMLDocumentRepository.refresh(XMLDocumentRepository.java:131) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:146) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:84) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:132) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:114) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:218) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:204) > at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:67) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:126) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:110) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} > I tried EAP 6.4, 7.0, 7.1 and WildFly 10.1. > This is with devstudio 11.1.0.AM1 B873. > As indicated by Rob, this is likely caused by this commit from JBIDE-24758: > https://github.com/jbosstools/jbosstools-server/commit/1a58a4d54097e4d927... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4493) powershell version <= 2 never returns control to installer after running the scripts

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4493?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4493: -------------------------------- Summary: powershell version <= 2 never returns control to installer after running the scripts (was: Virtualization detection never terminates on powershell version <= 2 ) > powershell version <= 2 never returns control to installer after running the scripts > ------------------------------------------------------------------------------------ > > Key: JBDS-4493 > URL: https://issues.jboss.org/browse/JBDS-4493 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM2 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 11.1.0.AM1 > > > Follow up on the mail thread about detection not finishing on win 7. > Namely methods from the Platform class that call powershell commands: > - isVirtualizationEnabled > - getHypervisorVersion > - isHypervisorEnabled > For some reason when called instead of erroring (since these commands dont work on older powershell) they don't terminate and block the detection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24447) Look for minishift configuration in MINISHIFT_HOME

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24447?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24447. --------------------------------- Closing. > Look for minishift configuration in MINISHIFT_HOME > -------------------------------------------------- > > Key: JBIDE-24447 > URL: https://issues.jboss.org/browse/JBIDE-24447 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection > Affects Versions: 4.4.4.Final > Reporter: Jan Richter > Assignee: Rob Stryker > Fix For: 4.5.1.AM2 > > Attachments: cdk2_x_RD.png, cdk3_minishift_home.png > > > One can use the MINISHIFT_HOME variable to save minishift configuration somewhere else than in ~/.minishift > It would be nice if runtime detection looked there if the variable is configured. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24447) Look for minishift configuration in MINISHIFT_HOME

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24447?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24447: --------------------------------------- [~rob.stryker], I agree with you in general, but it always depends on the case. Here the main purpose was to make MINISHIFT_HOME work. So if it works in general and there is a small bug somewhere in there, I agree a new JIRA is in order. But here before I learnt the details, it seemed that the simple use case and main purpose of this JIRA didn't work for Ondrej, so I felt it was right to reopen this JIRA. Later it turned out that his was not a normal workflow and it was a very specific use case, so yes, in hindsight this JIRA didn't need to be reopened. > Look for minishift configuration in MINISHIFT_HOME > -------------------------------------------------- > > Key: JBIDE-24447 > URL: https://issues.jboss.org/browse/JBIDE-24447 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection > Affects Versions: 4.4.4.Final > Reporter: Jan Richter > Assignee: Rob Stryker > Fix For: 4.5.1.AM2 > > Attachments: cdk2_x_RD.png, cdk3_minishift_home.png > > > One can use the MINISHIFT_HOME variable to save minishift configuration somewhere else than in ~/.minishift > It would be nice if runtime detection looked there if the variable is configured. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4519) Show Download/Install/Failed/Complete Information for Installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4519?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4519: -------------------------------- Fix Version/s: 11.1.0.AM1 (was: 11.x) Sprint: devex #136 August 2017 > Show Download/Install/Failed/Complete Information for Installer > --------------------------------------------------------------- > > Key: JBDS-4519 > URL: https://issues.jboss.org/browse/JBDS-4519 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Mohit Suman > Assignee: Mohit Suman > Fix For: 11.1.0.AM1 > > Attachments: dwnl-info.png, status-new.png > > > Add textual/visual information mentioning the current state of the package Download/Install/Dailed/Complete. > 1. Adds a spinner for Download/Installation/Verification. > 2. error icon for failed download. > 3. Ok icon for complete installation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3839) Change the progress bar color to red in case of failure

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3839?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3839: -------------------------------- Sprint: devex #136 August 2017 > Change the progress bar color to red in case of failure > ------------------------------------------------------- > > Key: JBDS-3839 > URL: https://issues.jboss.org/browse/JBDS-3839 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Srna > Assignee: Mohit Suman > Labels: ui > Fix For: 11.1.0.AM1 > > Attachments: error-descr.png > > > Mark UI changes on for any failed download. > 1. Change the progress bar color. > 2. Add text identifier for the same. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3839) Change the progress bar color to red in case of failure

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3839?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3839: -------------------------------- Fix Version/s: 11.1.0.AM1 (was: 11.x) > Change the progress bar color to red in case of failure > ------------------------------------------------------- > > Key: JBDS-3839 > URL: https://issues.jboss.org/browse/JBDS-3839 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Srna > Assignee: Mohit Suman > Labels: ui > Fix For: 11.1.0.AM1 > > Attachments: error-descr.png > > > Mark UI changes on for any failed download. > 1. Change the progress bar color. > 2. Add text identifier for the same. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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