April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25677) Server adapter: Timers are incorrectly managed

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25677?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25677: ------------------------------- Fix Version/s: 4.6.0.AM1 (was: 4.5.x) > Server adapter: Timers are incorrectly managed > ---------------------------------------------- > > Key: JBIDE-25677 > URL: https://issues.jboss.org/browse/JBIDE-25677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, server_adapter > Fix For: 4.6.0.AM1 > > > Timers are incorrectly managed in OpenShift server adapter. I tried to create a NodeJS server adapter on OpenShift Online Starter. As the first rsync is long (thanks to .npm and node_modules), it may take more than 5mns as OpenShift Online Starter is resource limited. I think we should rather monitor the activity of the rsync operation (through messages) and set a timer related to this activity. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25586) OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25586?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25586: ------------------------------- Fix Version/s: 4.6.0.AM1 (was: 4.5.3.Final) > OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK > ---------------------------------------------------------------- > > Key: JBIDE-25586 > URL: https://issues.jboss.org/browse/JBIDE-25586 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.5.2.Final > Environment: FC27 > OpenJDK 9.0.1 > CDK v3.3.0-rc.1-1 > eclipse.buildId=11.2.0.GA-v20180115-0516-B1866 > java.version=9.0.1 > 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 > Reporter: Josef Kopriva > Assignee: Rob Stryker > Priority: Critical > Labels: cdk, connection > Fix For: 4.6.0.AM1 > > > But, connecting to online openshift instance works. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25867) When downloading CDK runtime, seems the delete archive flag is not processed

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25867?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25867: ------------------------------- Fix Version/s: 4.6.0.AM1 (was: 4.6.x) > When downloading CDK runtime, seems the delete archive flag is not processed > ---------------------------------------------------------------------------- > > Key: JBIDE-25867 > URL: https://issues.jboss.org/browse/JBIDE-25867 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.3.AM3 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: cdk, cdk_server_adapter > Fix For: 4.6.0.AM1 > > > I used many time the download runtime for CDK server adapter but even if the delete archive after download is unchecked, the download is always executed -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25923) Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25923?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25923: ------------------------------- Fix Version/s: 4.6.0.AM1 > Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over > ------------------------------------------------------------------------------------ > > Key: JBIDE-25923 > URL: https://issues.jboss.org/browse/JBIDE-25923 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.3.Final > Environment: Fedora, JBoss EAP 7.1, WildFly 11, 12 > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.6.0.AM1 > > Attachments: ServerAdapterEAP.gif, ServerAdapterEAPRepaired.gif > > > When there is specific maven project imported in Project explorer (jbosstools-openshift), Started EAP 7.1 server adapter is printing output where deployment scanner replaces deployment and redeploy over and over again, see part of log: > {code} > 15:35:15,824 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v1.xml" (runtime-name : "standalone.v1.xml") > 15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml") > 15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.v2.xml" (runtime-name: "standalone.v2.xml") > 15:35:20,856 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml") > 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.last.xml" (runtime-name : "standalone.last.xml") > 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v2.xml" (runtime-name : "standalone.v2.xml") > 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.xml" (runtime-name : "standalone.xml") > 15:35:25,951 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 20ms > 15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "standalone.v3.xml" (runtime-name: "standalone.v3.xml") > 15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml") > 15:35:25,957 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 2ms > 15:35:25,964 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml") > 15:35:26,037 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml" > 15:35:26,038 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v3.xml" (runtime-name : "standalone.v3.xml") > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24979) Scale up/down/to: NPE if you have only a rc, no dc for your app

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24979?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24979: ------------------------------- Fix Version/s: 4.6.0.AM1 (was: 4.5.x) > Scale up/down/to: NPE if you have only a rc, no dc for your app > --------------------------------------------------------------- > > Key: JBIDE-24979 > URL: https://issues.jboss.org/browse/JBIDE-24979 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.x > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Labels: openshift_v3, scale > Fix For: 4.6.0.AM1 > > Attachments: eap-without-service-nor-deploymentconfig.json, image-2017-09-04-21-24-57-027.png > > > # ASSERT: make sure that you have an app that has *NO* deployment config, just a replication controller > (EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json]) > # EXEC: in OpenShift explorer: select the pod for your rc, pick "Scale > Up" or "Scale > Down" or "Scale > To" > !image-2017-09-04-21-24-57-027.png! > The very same is true if you do the same via the properties view "Deployments". There's a "Scale" item for the deployment context menu, but it does nothing. > Result: > Nothing happens and in the log you discover the following: > {code} > org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:65) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:239) > 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:487) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:431) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:446) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:472) > 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.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153) > at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151) > 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:653) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590) > at org.eclipse.equinox.launcher.Main.run(Main.java:1499) > at org.eclipse.equinox.launcher.Main.main(Main.java:1472) > Caused by: java.lang.NullPointerException > at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:143) > at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:136) > at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:106) > at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.execute(ScaleDeploymentHandler.java:78) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:291) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:92) > at sun.reflect.GeneratedMethodAccessor104.invoke(Unknown Source) > 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:55) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25900) Support hyperlinks in Project Template Details group

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25900?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25900: ------------------------------- Fix Version/s: 4.6.0.AM1 (was: 4.5.x) > Support hyperlinks in Project Template Details group > ---------------------------------------------------- > > Key: JBIDE-25900 > URL: https://issues.jboss.org/browse/JBIDE-25900 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM3 > Reporter: Denis Golovin > Assignee: Jeff MAURY > Priority: Optional > Fix For: 4.6.0.AM1 > > Attachments: image-2018-04-04-00-36-48-807.png > > > Would be good to support links in Template Details group, so copy/paste to browser would not be required. > !image-2018-04-04-00-36-48-807.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25825) Properties: Basic block should always be displayed 1st

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25825?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25825: ------------------------------- Fix Version/s: 4.6.0.AM1 (was: 4.5.x) > Properties: Basic block should always be displayed 1st > ------------------------------------------------------ > > Key: JBIDE-25825 > URL: https://issues.jboss.org/browse/JBIDE-25825 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.3.AM2 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Labels: properties > Fix For: 4.6.0.AM1 > > Attachments: image-2018-03-19-19-14-10-158.png, image-2018-03-19-19-17-41-770.png, image-2018-03-19-19-20-48-227.png > > > # ASSERT: have an application running in OpenShift > # EXEC: in OpenShift Explorer: select the project of your application > # EXEC: in Properties view: select *Details* tab, look at the blocks being shown > Result: > 1st block being displayed is *Annotations*, 2nd is *Details* > !image-2018-03-19-19-14-10-158.png! > # EXEC: in Properties view: select *Builds*, select an entry, look at the details of it > Result: > !image-2018-03-19-19-17-41-770.png! > # EXEC: in Properties view: select *Deployments*, select an entry, look at the details of it > Result: > !image-2018-03-19-19-20-48-227.png! > Same is true for *Deployment Configs*, *Pods*, etc -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25928) Create New and Noteworthy for 4.6.0.AM1

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25928?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25928: ------------------------------- Sprint: devex #148 April 2018 > Create New and Noteworthy for 4.6.0.AM1 > --------------------------------------- > > Key: JBIDE-25928 > URL: https://issues.jboss.org/browse/JBIDE-25928 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.6.0.AM1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N. See subtasks below. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25942) JSF New and Noteworthy for 4.6.0.AM1

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25942?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25942: ------------------------------- Labels: task (was: ) > JSF New and Noteworthy for 4.6.0.AM1 > --------------------------------------------------- > > Key: JBIDE-25942 > URL: https://issues.jboss.org/browse/JBIDE-25942 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsf, jsp/jsf/xml/html-source-editing > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.6.0.AM1 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed JSF 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 JSF, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for JSF 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-25928 #comment Create N&N for JSF 4.6.0.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 JSF for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25936) Fuse Tools New and Noteworthy for 4.6.0.AM1

by Jeff MAURY (JIRA)

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

7 years, 11 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 April 2018