August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22785) Create integration tests PR check job for forge

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22785?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-22785: --------------------------------------- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Create integration tests PR check job for forge > ----------------------------------------------- > > Key: JBIDE-22785 > URL: https://issues.jboss.org/browse/JBIDE-22785 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Josef Kopriva > Fix For: 4.4.1.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22793) Create integration tests PR check job for maven

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22793?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-22793. --------------------------------- > Create integration tests PR check job for maven > ----------------------------------------------- > > Key: JBIDE-22793 > URL: https://issues.jboss.org/browse/JBIDE-22793 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Josef Kopriva > Fix For: 4.4.1.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22793) Create integration tests PR check job for maven

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22793?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-22793: --------------------------------------- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Create integration tests PR check job for maven > ----------------------------------------------- > > Key: JBIDE-22793 > URL: https://issues.jboss.org/browse/JBIDE-22793 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Josef Kopriva > Fix For: 4.4.1.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22814) ResourceException below HibernateProjectConfigurator.configureInternal (thrown in Project.checkAccessible)

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22814?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-22814. --------------------------------- I am closing this issue. I was not able to reproduce this bug. In the AERI report are not included steps to reproduce this bug. If this issue occurs, fell free to reopen this JIRA. > ResourceException below HibernateProjectConfigurator.configureInternal (thrown in Project.checkAccessible) > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22814 > URL: https://issues.jboss.org/browse/JBIDE-22814 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.4.0.Final > Reporter: Automated Error Reporting Bot > Assignee: Fred Bricon > Fix For: 4.4.1.AM3 > > > The following problem was reported via the automated error reporting: > Message: HIDDEN > {noformat} > org.eclipse.core.internal.resources.ResourceException: HIDDEN > at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:143) > at org.eclipse.core.internal.resources.Project.hasNature(Project.java:521) > at org.jboss.tools.maven.hibernate.configurators.HibernateProjectConfigurator.configureInternal(HibernateProjectConfigurator.java:53) > at org.jboss.tools.maven.hibernate.configurators.HibernateProjectConfigurator.mavenProjectChanged(HibernateProjectConfigurator.java:90) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.mavenProjectChanged(ProjectConfigurationManager.java:1000) > at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:783) > at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:919) > at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob$1.call(ProjectRegistryRefreshJob.java:98) > at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob$1.call(ProjectRegistryRefreshJob.java:1) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99) > at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355) > at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob.run(ProjectRegistryRefreshJob.java:81) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | > | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160503-1608 | > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 | > | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 | > | org.eclipse.jst.j2ee.ejb.annotations.xdoclet | 1.2.200.v201103302126 | 1.2.200.v201103302126 | > | org.eclipse.m2e.core | 1.6.2.20150902-0002 | 1.7.0.20160603-1933 | > | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 | > | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 | > | org.jboss.tools.maven.hibernate | 1.7.1.Final-v20160401-1059-B103 | 1.8.0.Final-v20160613-2000-B8 | > Operating Systems: > | Linux | 3.10.0.18 | 4.4.0 | > | MacOSX | 10.11.5 | 10.11.5 | > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5720f424e4b0a54983...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22861) Explorer: Pod is not refreshed (watch problem with new ohttp based rest client)

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22861?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22861. --------------------------------- Verified in DevStudio 10.1.0.AM3 build ID AM3-v20160812-0415-B5753. > Explorer: Pod is not refreshed (watch problem with new ohttp based rest client) > ------------------------------------------------------------------------------- > > Key: JBIDE-22861 > URL: https://issues.jboss.org/browse/JBIDE-22861 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Fix For: 4.4.1.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22644) Unable to perform oc binary actions because of insecure flag

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22644?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22644. --------------------------------- Verified in DevStudio 10.1.0.AM3 build ID AM3-v20160812-0415-B5753. > Unable to perform oc binary actions because of insecure flag > ------------------------------------------------------------ > > Key: JBIDE-22644 > URL: https://issues.jboss.org/browse/JBIDE-22644 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.4.1.AM3 > > > Trying to retrieve pod logs or any oc binary action results in warning of: > specifying a root certificates file with the insecure flag is not allowed > Per deads openshift dev "...it means that your kubeconfig file has a CA set, but you're trying to connect insecurely" > Persumably this requires us to make sure KUBECONFIG env var is not set when executing oc binary commands. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22704) Application Wizard: Application based on builder images do not have prefilled configuration

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22704?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22704. --------------------------------- Verified in DevStudio 10.1.0.AM3 build ID AM3-v20160812-0415-B5753. > Application Wizard: Application based on builder images do not have prefilled configuration > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22704 > URL: https://issues.jboss.org/browse/JBIDE-22704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: application_wizard, openshift_v3 > Fix For: 4.4.1.AM3 > > > When opening a New OpenShift Application wizard either from Central or shell menu File - New, details in builder image part of wizard are missing. E.g. there is no default resource name (build configuration wizard page), environment variables (Deployment Configuration and Scalability wizard page) or port mapping (Service and Routing Settings wizard page). When opening the wizard from context menu of an OpenShift 3 project, its works fine. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22868) Import Wizard: Last used git clone location is not used

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22868?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22868. --------------------------------- Verified in DevStudio 10.1.0.AM3 build ID AM3-v20160812-0415-B5753. > Import Wizard: Last used git clone location is not used > ------------------------------------------------------- > > Key: JBIDE-22868 > URL: https://issues.jboss.org/browse/JBIDE-22868 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: import_wizard, openshift_v3 > Fix For: 4.4.1.AM3 > > > When importing an OpenShift 3 application, I can customize where to clone source code. If I change it from default git clone location to something different. e.g. /home/mlabuda/git/alt instead of /home/mlabuda/git, the new value is used all the time. Problem is, when I decide to use default git clone location again so I check the checkbox to use that one. But this choice is not remembered and every time custom location is used. So I have to change it manually by checking the checkbox all the time. > I think, if user want to use customized location all the time he should change it in git preferences. So it would be compatible across whole IDE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22274) Show In->System Explorer on docker volume is not working when the volume is just a file (not a directory)

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22274?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-22274. --------------------------------- Issue is fixed. Verified in: Version: 10.1.0.AM3 Build id: AM3-v20160812-0415-B5753 Build date: 20160812-0415 > Show In->System Explorer on docker volume is not working when the volume is just a file (not a directory) > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22274 > URL: https://issues.jboss.org/browse/JBIDE-22274 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.4.0.Alpha1 > Environment: JBDS 10.0.0.Alpha1-v20160428-0509-B5247 > Reporter: Radim Hopp > Assignee: Jeff Johnston > Fix For: 4.4.1.AM3 > > > Start docker container with -v parameter pointing to some file. For example: "docker run -d -p 5000:5000 -v /home/rhopp/temp/config.yml_new:/etc/docker/registry/config.yml --name registry1 registry:2" > Go to Docker Explorer, expand running container->right click on the only volume in there->Show In->System Explorer-> Error is logged: > {noformat:title=Failed to open in Web Browser} > java.io.IOException: Cannot run program "/bin/sh" (in directory "/home/rhopp/temp/config.yml_new"): error=20, Not a directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) > at java.lang.Runtime.exec(Runtime.java:620) > at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.getLaunchProcess(ShowInSystemExplorerCommandHandler.java:99) > at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.access$0(ShowInSystemExplorerCommandHandler.java:96) > at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler$1.run(ShowInSystemExplorerCommandHandler.java:65) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.io.IOException: error=20, Not a directory > at java.lang.UNIXProcess.forkAndExec(Native Method) > at java.lang.UNIXProcess.<init>(UNIXProcess.java:248) > at java.lang.ProcessImpl.start(ProcessImpl.java:134) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) > ... 5 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22848) Application Wizard: NPE is thrown when closing the wizard and Create OpenShift Project shell

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22848?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22848. --------------------------------- Verified in DevStudio 10.1.0.AM3 build ID AM3-v20160812-0415-B5753. > Application Wizard: NPE is thrown when closing the wizard and Create OpenShift Project shell > -------------------------------------------------------------------------------------------- > > Key: JBIDE-22848 > URL: https://issues.jboss.org/browse/JBIDE-22848 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: application_wizard, openshift_v3 > Fix For: 4.4.1.AM3 > > > There is a prompt to create a new project, if there is no project under an OpenShift 3 connection and New OpenShift Application wizard is opened. If I close popped up shell Create OpenShift Project, also New App wizard is closed and following NPE is shown. This is happening only when opening the wizard through context menu in OpenShift Explorer. Wizards opened via central/shell menu leave New App wizard opened upon cancellation/closing of Create OpenShift Project shell. > {code} > org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:64) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:433) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:454) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:482) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) > Caused by: java.lang.NullPointerException > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizard.setConnection(NewApplicationWizard.java:292) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizard.init(NewApplicationWizard.java:98) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:281) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270) > at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54) > ... 37 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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