October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24778) Creating application from Eclipse project which already defines a Git repo should reuse the URL

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24778?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-24778: ---------------------------------- Assignee: Dmitrii Bocharov (was: Andre Dietisheim) > Creating application from Eclipse project which already defines a Git repo should reuse the URL > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24778 > URL: https://issues.jboss.org/browse/JBIDE-24778 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Mickael Istria > Assignee: Dmitrii Bocharov > Fix For: 4.5.x > > > I'm trying to connect an existing Eclipse project to OpenShift. > The project is connected to GitHub ( https://github.com/mickaelistria/demo-dotnet.git ) > The OpenShift application I'm using uses a dotnet-core:2.0 image. > Once I've selected the openshift project, the Eclipse project and the application image; I'm driven to a wizard page asking me for some details about the application, including the Git repo URL. > I would expect the repo URL to be prepopulated with the Git repo URL of my Eclipse project > Instead, the URL was the one of the image example: https://github.com/redhat-developer/s2i-dotnetcore-ex.git > If this is an issue in the .NET Core 2.0 image, please tell me and I'll open a bug for it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24845) [regression] unable to open the Maven Repositories wizard

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24845?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-24845: ---------------------------------- Assignee: Dmitrii Bocharov (was: Fred Bricon) > [regression] unable to open the Maven Repositories wizard > --------------------------------------------------------- > > Key: JBIDE-24845 > URL: https://issues.jboss.org/browse/JBIDE-24845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.4.4.Final > Reporter: Fred Bricon > Assignee: Dmitrii Bocharov > Fix For: 4.5.1.Final > > > 1 - open Preferences > JBoss Tools > JBoss Maven Integration > 2 - click on the Configure Maven Repositories... button > expected: the Maven repositories wizard open > actual: Unhandled event loop exception: > {noformat} > java.lang.NoSuchFieldError: DEFAULT_USER_SETTINGS_FILE > at org.jboss.tools.maven.ui.wizard.ConfigureMavenRepositoriesWizardPage.getUserSettings(ConfigureMavenRepositoriesWizardPage.java:988) > at org.jboss.tools.maven.ui.wizard.ConfigureMavenRepositoriesWizardPage.createControl(ConfigureMavenRepositoriesWizardPage.java:242) > at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:176) > at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:688) > at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:580) > at org.eclipse.jface.window.Window.create(Window.java:426) > at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096) > at org.jboss.tools.maven.ui.preferences.ConfiguratorPreferencePage$2.widgetSelected(ConfiguratorPreferencePage.java:155) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4257) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1502) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1525) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1510) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1314) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4081) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) > at org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:59) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24899) Deploy Docker Image wizard: Image not found

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24899?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-24899: ---------------------------------- Assignee: Jeff MAURY > Deploy Docker Image wizard: Image not found > ------------------------------------------- > > Key: JBIDE-24899 > URL: https://issues.jboss.org/browse/JBIDE-24899 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, docker, openshift > Affects Versions: 4.5.1.AM1 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.x > > Attachments: image-2017-08-29-09-50-20-927.png > > > Exception in Error log: > {code:java} > Failed to inspect image: '172.30.1.1:5000/test/hola:latest' > 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) > eclipse.buildId=11.1.0.AM1-v20170824-1835-B873 > java.version=1.8.0_141 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25121) Connection wizard: Image Registry URL is not decorated when not valid (and validation seems weird)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25121?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-25121: ---------------------------------- Assignee: Jeff MAURY > Connection wizard: Image Registry URL is not decorated when not valid (and validation seems weird) > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-25121 > URL: https://issues.jboss.org/browse/JBIDE-25121 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Priority: Minor > Fix For: 4.5.x > > Attachments: image-2017-09-27-22-59-33-548.png > > > steps 1: > # ASSERT: have a connection the cdk > # EXEC: edit the connection and move to "Image Registry URL" text field > # EXEC: provide some bogus URL (ex. bookaroo-banzai) > Result: > the url is validated and an error appears in the title are, "Finish" is disabled. GOOD. > But the text field is not decorated. > !image-2017-09-27-22-59-33-548.png! > steps 2: > # EXEC: provide the following URL: http:/bookaroo-banzai > Result: > It thinks that it's valid, there's no error in the title area, "Finish" is enabled > Expected result: > http:/bookaroo-banzai doesnt look valid to me, it should error and disable "Finish" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25133) Remove deprecated code for Tar files

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25133?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-25133: ----------------------------------- Assignee: Rob Stryker > Remove deprecated code for Tar files > ------------------------------------ > > Key: JBIDE-25133 > URL: https://issues.jboss.org/browse/JBIDE-25133 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.5.x > > > in [JBIDE-25113], a part of the code has been deprecated, it would nice to remove it in next version 4.6. See https://github.com/jbosstools/jbosstools-base/pull/600/commits/2e617a7e82... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25157) Re-add WTP server actions in toolbar configuration, but don't show them initially in the toolbar when installing

by Fabi Yo (JIRA)

Fabi Yo created JBIDE-25157: ------------------------------- Summary: Re-add WTP server actions in toolbar configuration, but don't show them initially in the toolbar when installing Key: JBIDE-25157 URL: https://issues.jboss.org/browse/JBIDE-25157 Project: Tools (JBoss Tools) Issue Type: Enhancement Affects Versions: 4.5.0.Final Environment: Any Reporter: Fabi Yo see linked issue. I added a comment there to explain the situation -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25118) improve errata waiver check script - add waivers for desktop-file-sanity, patches, IP v6

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25118?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-25118. -------------------------------- Fix Version/s: 4.5.1.AM3 (was: 4.5.1.Final) Resolution: Done > improve errata waiver check script - add waivers for desktop-file-sanity, patches, IP v6 > ---------------------------------------------------------------------------------------- > > Key: JBIDE-25118 > URL: https://issues.jboss.org/browse/JBIDE-25118 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, rpm > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: release > Fix For: 4.5.1.AM3 > > Attachments: errata-waiver.results-can't-find-dali.txt > > > {quote} > It sounds like we could add these check types to my script: > > * desktop-file-sanity (always waive?) > * IP v6 (always waive using existing waiver details, eg., https://errata.devel.redhat.com/rpmdiff/show/182126?result_id=5028358 > Yep, yep. > > * patches (waive if %autopatch) > And if the only other complaints are "patch not applied" (I'm not sure if this check may throw different kinds of error){quote} > So, the next time we have an errata with the above types of issues, I can update this script [1] to add those use cases. > [1] https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/errata... > cc: [~mat.booth] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25152) Make the old Hibernate runtime plugins optional

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25152?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25152: ------------------------------------ Simplest option would be to expose these plugins on the update sites directly, then mark all but the latest deprecated. And we could include only the last one in the CoreTools / OOTB install from Marketplace/devstudio installer. For the tests, however, I suppose they need to be updated to 5_2, ideally in a global variable in a single place (rather than hardcoded everywhere), and we can mark the old version-specific ones deprecated too. Then all these deprecated plugins should either be contained in a runtime.old feature / runtime.test.old feature, or simply removed so they're only exposed one by one on the update sites. Here's the complete list of IUs: * hibernate-search-plugins/org.jboss.tools.hibernate.search.runtime.v_4_0 * hibernate-search-plugins/org.jboss.tools.hibernate.search.runtime.v_5_3 * hibernate-search-plugins/org.jboss.tools.hibernate.search.runtime.v_5_5 * hibernate-search-plugins/org.jboss.tools.hibernate.search.runtime.v_5_5.1 * hibernate-search-plugins/org.jboss.tools.hibernate.search.runtime.v_5_7 * plugins/org.jboss.tools.hibernate.libs.antlr.v_2_7_7 * plugins/org.jboss.tools.hibernate.libs.bsh.v_2_0_b4 * plugins/org.jboss.tools.hibernate.libs.dom4j.v_1_6_1 * plugins/org.jboss.tools.hibernate.libs.freemarker.v_2_3_8 * plugins/org.jboss.tools.hibernate.libs.jtidy.v_r8-20060801 * plugins/org.jboss.tools.hibernate.runtime.v_3_5 * plugins/org.jboss.tools.hibernate.runtime.v_3_6 * plugins/org.jboss.tools.hibernate.runtime.v_4_0 * plugins/org.jboss.tools.hibernate.runtime.v_4_3 * plugins/org.jboss.tools.hibernate.runtime.v_5_0 * plugins/org.jboss.tools.hibernate.runtime.v_5_1 * plugins/org.jboss.tools.hibernate.runtime.v_5_2 * tests/org.jboss.tools.hibernate.runtime.v_3_5.test * tests/org.jboss.tools.hibernate.runtime.v_3_6.test * tests/org.jboss.tools.hibernate.runtime.v_4_0.test * tests/org.jboss.tools.hibernate.runtime.v_4_3.test * tests/org.jboss.tools.hibernate.runtime.v_5_0.test * tests/org.jboss.tools.hibernate.runtime.v_5_1.test * tests/org.jboss.tools.hibernate.runtime.v_5_2.test > Make the old Hibernate runtime plugins optional > ----------------------------------------------- > > Key: JBIDE-25152 > URL: https://issues.jboss.org/browse/JBIDE-25152 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.5.1.AM2 > Reporter: Koen Aers > Fix For: 4.5.1.Final > > > There are a fair number of Hibernate runtime plugins available for the current JBoss Tools. They are named ‘org.jboss.tools.hibernate.runtime.v_x_y’ and use the actual core Hibernate (and Hibernate tools) classes to implement the SPI defined in ‘org.jboss.tools.hibernate.runtime.spi’. But the number of these implementations keeps growing and so it is needed to get this under control. The aimed solution is to only provide the most recent implementation and make the other ones installable on request. > To solve this issue all the places where the actual Hibernate version is hardcoded need to be identified and only the latest version can be used. This is especially true for the tests in 'org.hibernate.eclipse.console.test' which use version 3.5. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3824) Installer: it is not clear what will be downloaded on Confirmation page

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBDS-3824?page=com.atlassian.jira.plugin.... ] Mohit Suman commented on JBDS-3824: ----------------------------------- Now in the Confirmation page, we have a summary of what is _selected to download_ and what is_ previously downloaded_. This also has the *Total Download Size* and *Total Install Size*. > Installer: it is not clear what will be downloaded on Confirmation page > ----------------------------------------------------------------------- > > Key: JBDS-3824 > URL: https://issues.jboss.org/browse/JBDS-3824 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Mohit Suman > Labels: ui > Fix For: 11.x > > > While on the _Confirmation_ page inside installer, there is a button _Download & Install_. User already downloaded 1.5G installer and it's not clear what will be downloaded in the next step. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3824) Installer: it is not clear what will be downloaded on Confirmation page

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBDS-3824?page=com.atlassian.jira.plugin.... ] Mohit Suman resolved JBDS-3824. ------------------------------- Resolution: Done > Installer: it is not clear what will be downloaded on Confirmation page > ----------------------------------------------------------------------- > > Key: JBDS-3824 > URL: https://issues.jboss.org/browse/JBDS-3824 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Mohit Suman > Labels: ui > Fix For: 11.x > > > While on the _Confirmation_ page inside installer, there is a button _Download & Install_. User already downloaded 1.5G installer and it's not clear what will be downloaded in the next step. -- 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 October 2017