February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21626) Pod is not created when docker image is deployed to OpenShift

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21626?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21626: ---------------------------------- Labels: openshift_v3 (was: ) > Pod is not created when docker image is deployed to OpenShift > ------------------------------------------------------------- > > Key: JBIDE-21626 > URL: https://issues.jboss.org/browse/JBIDE-21626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3 > > When deploying a docker image to OpenShift via oc binary, pod where the image is supposed to run is created, together with service and router. But when deploying a docker image to OpenShift via OpenShift tools, no pod is created, only service and router. When using cli, pod is created later (what I noticed, there is different pull policy between creating from cli with "oc new-app docker-image" and creating from IDE). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-70) Gulp / Grunt support - first iteration [EBZ#486956]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-70?page=com.atlassian.jira.plugin.sys... ] Ilya Buziuk reassigned ERT-70: ------------------------------ Assignee: Ilya Buziuk > Gulp / Grunt support - first iteration [EBZ#486956] > --------------------------------------------------- > > Key: ERT-70 > URL: https://issues.jboss.org/browse/ERT-70 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: 3.8_M6, General, bzira > Fix For: Neon (4.6) M6 > > > This issue includes initial code drop of basic grunt 483398 & gulp 483399 support. > Initial support includes: > - CNF contribution of tasks to project explorer > - Task launch (right click on the Task -> Run As -> grunt / gulp Task). The launch falls back on CLI calls (org.eclipse.wst.jsdt.js.cli) same as for bower & npm > - Basic Launch Configuration UI with build file selection and task selection -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21616) Main tab for CDK launch configuration is not whole by default

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21616?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21616: ------------------------------------- Honestly I've seen this type of issue all throughout eclipse lately. I've just gotten used to simply resizing dialogs and stuff once they open. I don't think it's specific to jbt at all. > Main tab for CDK launch configuration is not whole by default > ------------------------------------------------------------- > > Key: JBIDE-21616 > URL: https://issues.jboss.org/browse/JBIDE-21616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Environment: Fedora 22, GTK3 > Reporter: Marián Labuda > Attachments: after.png, before.png > > > In launch configuration of a CDK server adapter there are 2 tabs - Main and Environment. Upon opening of launch configuration for a CDK server adapter, Main tab is preselected but there are only Location widgets available. > !before.png! > After switching to Environment tab and back, Working directory and Arguments widgets become available. > !after.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21619) Accessing CDK server raises this exception: Problems occurred when invoking code from plug-in: "org.eclipse.jface".

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21619?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-21619. --------------------------------- Fix Version/s: 4.3.1.CR1 Resolution: Duplicate Issue Duplicate of JBIDE-21613 > Accessing CDK server raises this exception: Problems occurred when invoking code from plug-in: "org.eclipse.jface". > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21619 > URL: https://issues.jboss.org/browse/JBIDE-21619 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.Beta2 > Environment: JBoss Developer Studio > Version: 9.1.0.Beta2 > Build id: Beta2-v20160127-2213-B262 > Build date: 20160127-2213 > RHEL7 > Java 1.8 > Reporter: Len DiMaggio > Fix For: 4.3.1.CR1 > > > To recreate the error: > 1) Create a new CDL server runtime - I used CDK2, Beta4 > 2) In the server explorer, start the server, and then left click on the running server > This message is generated: > Problems occurred when invoking code from plug-in: "org.eclipse.jface". > And, this exception is raised: > java.lang.NullPointerException > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.findDockerConnection(CDKDockerUtility.java:53) > at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInDockerViewAfterStartupAction.adaptToViewItem(CDKActionProvider.java:111) > at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.accept(CDKActionProvider.java:188) > at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.selectionChanged(AbstractServerAction.java:85) > at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.selectionChanged(CDKActionProvider.java:203) > at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:144) > at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:163) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160) > at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2197) > at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1228) > at org.eclipse.ui.navigator.CommonViewer.handleSelect(CommonViewer.java:461) > at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1257) > at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242) > at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236) > at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:408) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > 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:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > 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:497) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-61) Implement converter to DOM AST

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-61?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan reassigned ERT-61: ------------------------------- Assignee: Gorkem Ercan > Implement converter to DOM AST > ------------------------------ > > Key: ERT-61 > URL: https://issues.jboss.org/browse/ERT-61 > Project: Eclipse Release Train > Issue Type: Sub-task > Components: JSDT > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: Neon (4.6) M6 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21582) Server adapter: always publishes on Eclipse startup

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21582?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21582: ------------------------------------- When a workspace starts, all 'change' data is lost. The previously-published resources are not persisted in any long-term storage. So when a workspace starts, the current publish state is "unknown". If you want, you can check exactly what publish flags are used during the first startup and you can try to ignore that flag combination... but you may end up with a situation later where that same flag combination occurs (current publish state = unknown, publish type = incremental or auto, etc) and you'll be ignoring it when you shouldnt. > Server adapter: always publishes on Eclipse startup > --------------------------------------------------- > > Key: JBIDE-21582 > URL: https://issues.jboss.org/browse/JBIDE-21582 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21624) Add Deploy menu to deployment configs

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21624?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21624: -------------------------------- Fix Version/s: 4.3.1.CR1 > Add Deploy menu to deployment configs > ------------------------------------- > > Key: JBIDE-21624 > URL: https://issues.jboss.org/browse/JBIDE-21624 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Priority: Critical > Fix For: 4.3.1.CR1 > > > We currently cannot trigger a deployment of a Deployment Config, like in the webconsole. Hopefully it should be trivial to implement. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21624) Add Deploy menu to deployment configs

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21624?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21624: ----------------------------------- Assignee: Jeff Cantrill > Add Deploy menu to deployment configs > ------------------------------------- > > Key: JBIDE-21624 > URL: https://issues.jboss.org/browse/JBIDE-21624 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.3.1.CR1 > > > We currently cannot trigger a deployment of a Deployment Config, like in the webconsole. Hopefully it should be trivial to implement. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21302) Removing user from credentials framework while not authenticated to secure storage should not work

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21302?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-21302: ---------------------------------------- Sprint: devex #0 January 2016, devex #1 February 2016 (was: devex #0 January 2016) > Removing user from credentials framework while not authenticated to secure storage should not work > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-21302 > URL: https://issues.jboss.org/browse/JBIDE-21302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.1.Beta1 > Environment: JBDS 9.0.0.Beta1-v20151210-1836-B183 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > Removing credentials (which are stored in secure storage) using > CredentialPreferencePage without being authenticated to secure storage (see steps to reproduce on how to do that) seems to delete the credentials, but after eclipse restart, the credentials are still there. I would prefer message saying something like "Unable to delete credentials stored in secure storage without atuhenticating to secure storage". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21625) Enable debug mode on OpenShift servers

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-21625: ----------------------------------- Summary: Enable debug mode on OpenShift servers Key: JBIDE-21625 URL: https://issues.jboss.org/browse/JBIDE-21625 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Reporter: Fred Bricon Priority: Critical Need to easily enable debug mode on EAP/Node images -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 February 2016