March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25775) CDI New and Noteworthy for 4.5.3.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25775?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25775. ------------------------------ Resolution: Rejected > CDI New and Noteworthy for 4.5.3.AM3 > --------------------------------------------------- > > Key: JBIDE-25775 > URL: https://issues.jboss.org/browse/JBIDE-25775 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.5.3.AM3 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed CDI 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 CDI, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for CDI 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-25774 #comment Create N&N for CDI 4.5.3.AM3 #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 CDI 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-25787) JSF New and Noteworthy for 4.5.3.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25787?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25787. ------------------------------ Resolution: Rejected > JSF New and Noteworthy for 4.5.3.AM3 > --------------------------------------------------- > > Key: JBIDE-25787 > URL: https://issues.jboss.org/browse/JBIDE-25787 > 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.5.3.AM3 > > > 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-25774 #comment Create N&N for JSF 4.5.3.AM3 #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-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-25303. -------------------------------------- Resolution: Done > Server adapter: support hot-deployment on OpenShift for SpringBoot app > ---------------------------------------------------------------------- > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.3.AM3 > > Attachments: Image+Pasted+at+2018-1-16+10-58.png, docker-explorer-inspect-image.png, fuse-on-openshift.zip, project-deployment-assembly.png, screenshot-1.png, spring-boot-demo.zip > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) > use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": > - there is a SpringBoot app deployed on OpenShift > - the developer want to develop evolution of the SpringBoot app > -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance > -- Remote java debug should be available when the OpenShift server adapter is in debug mode. > Steps: > # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot) > # EXEC: Import project within fuse-on-openshift.zip into your workspace > # EXEC: open launch configuration and change: > ** -Dkubernetes.master= so that it first your cdk instance > ** -Dkubernetes.namespace= to the name of the project that you create in step 1. > ** -Dfabric8.generator.from=fabric8/s2i-java > # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk) > # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running. > # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service) > # ASSERT: server adapter is created and is *[started]* > # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service) > # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end > {code} > simple-route - >>> 455 > simple-route - >>> 695 > simple-route - >>> 935 > {code} > # EXEC: In Project Explorer: open class MyTransformer and change the transform method > # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25303: ------------------------------------------ This is resolved with my latest patch for JBIDE-25700 and the updates in the fabric8/s2i-java image. One should not face errors any more. Resolving. [~jkopriva] Please reopen if you still face issues. > Server adapter: support hot-deployment on OpenShift for SpringBoot app > ---------------------------------------------------------------------- > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.3.AM3 > > Attachments: Image+Pasted+at+2018-1-16+10-58.png, docker-explorer-inspect-image.png, fuse-on-openshift.zip, project-deployment-assembly.png, screenshot-1.png, spring-boot-demo.zip > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) > use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": > - there is a SpringBoot app deployed on OpenShift > - the developer want to develop evolution of the SpringBoot app > -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance > -- Remote java debug should be available when the OpenShift server adapter is in debug mode. > Steps: > # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot) > # EXEC: Import project within fuse-on-openshift.zip into your workspace > # EXEC: open launch configuration and change: > ** -Dkubernetes.master= so that it first your cdk instance > ** -Dkubernetes.namespace= to the name of the project that you create in step 1. > ** -Dfabric8.generator.from=fabric8/s2i-java > # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk) > # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running. > # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service) > # ASSERT: server adapter is created and is *[started]* > # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service) > # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end > {code} > simple-route - >>> 455 > simple-route - >>> 695 > simple-route - >>> 935 > {code} > # EXEC: In Project Explorer: open class MyTransformer and change the transform method > # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25838) Explorer: expand connection to the level that it was expanded to after editing it

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25838?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25838: ------------------------------------- Forum Reference: https://github.com/jbosstools/jbosstools-openshift/pull/1704#issuecomment... > Explorer: expand connection to the level that it was expanded to after editing it > --------------------------------------------------------------------------------- > > Key: JBIDE-25838 > URL: https://issues.jboss.org/browse/JBIDE-25838 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.2.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: connection, explorer > Fix For: 4.5.3.Final > > > steps: > # ASSERT: in OpenShift Explorer: have a connection that is expanded to at least show a/all the projects > # EXEC: edit the connection, change the url, hit "Finish" > Result: > Connection is updated (refreshed) but collapsed, wont show the/all the projects > Expected result: > Connection is updated (refreshed) and expanded like it was before editing it, showing the project(s) (and even service(s) if it was expanded to that level before editing it) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25838) Explorer: expand connection to the level that it was expanded to after editing it

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-25838: ---------------------------------------- Summary: Explorer: expand connection to the level that it was expanded to after editing it Key: JBIDE-25838 URL: https://issues.jboss.org/browse/JBIDE-25838 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.5.2.AM3 Reporter: Andre Dietisheim steps: # ASSERT: in OpenShift Explorer: have a connection that is expanded to at least show a/all the projects # EXEC: edit the connection, change the url, hit "Finish" Result: Connection is updated (refreshed) but collapsed, wont show the/all the projects Expected result: Connection is updated (refreshed) and expanded like it was before editing it, showing the project(s) (and even service(s) if it was expanded to that level before editing it) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25838) Explorer: expand connection to the level that it was expanded to after editing it

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25838?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25838: ------------------------------------- Labels: connection explorer (was: ) > Explorer: expand connection to the level that it was expanded to after editing it > --------------------------------------------------------------------------------- > > Key: JBIDE-25838 > URL: https://issues.jboss.org/browse/JBIDE-25838 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.2.AM3 > Reporter: Andre Dietisheim > Labels: connection, explorer > Fix For: 4.5.3.Final > > > steps: > # ASSERT: in OpenShift Explorer: have a connection that is expanded to at least show a/all the projects > # EXEC: edit the connection, change the url, hit "Finish" > Result: > Connection is updated (refreshed) but collapsed, wont show the/all the projects > Expected result: > Connection is updated (refreshed) and expanded like it was before editing it, showing the project(s) (and even service(s) if it was expanded to that level before editing it) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25838) Explorer: expand connection to the level that it was expanded to after editing it

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25838?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25838: ------------------------------------- Fix Version/s: 4.5.3.Final > Explorer: expand connection to the level that it was expanded to after editing it > --------------------------------------------------------------------------------- > > Key: JBIDE-25838 > URL: https://issues.jboss.org/browse/JBIDE-25838 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.2.AM3 > Reporter: Andre Dietisheim > Labels: connection, explorer > Fix For: 4.5.3.Final > > > steps: > # ASSERT: in OpenShift Explorer: have a connection that is expanded to at least show a/all the projects > # EXEC: edit the connection, change the url, hit "Finish" > Result: > Connection is updated (refreshed) but collapsed, wont show the/all the projects > Expected result: > Connection is updated (refreshed) and expanded like it was before editing it, showing the project(s) (and even service(s) if it was expanded to that level before editing it) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25838) Explorer: expand connection to the level that it was expanded to after editing it

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25838?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-25838: ---------------------------------------- Assignee: Dmitrii Bocharov > Explorer: expand connection to the level that it was expanded to after editing it > --------------------------------------------------------------------------------- > > Key: JBIDE-25838 > URL: https://issues.jboss.org/browse/JBIDE-25838 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.2.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: connection, explorer > Fix For: 4.5.3.Final > > > steps: > # ASSERT: in OpenShift Explorer: have a connection that is expanded to at least show a/all the projects > # EXEC: edit the connection, change the url, hit "Finish" > Result: > Connection is updated (refreshed) but collapsed, wont show the/all the projects > Expected result: > Connection is updated (refreshed) and expanded like it was before editing it, showing the project(s) (and even service(s) if it was expanded to that level before editing it) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25829) Error when you cancel minishift location selection while creating cdk server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25829?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-25829. --------------------------------- Resolution: Done * 306942a - JBIDE-25829 - simple NPE (3 hours ago) <Rob Stryker> > Error when you cancel minishift location selection while creating cdk server > ---------------------------------------------------------------------------- > > Key: JBIDE-25829 > URL: https://issues.jboss.org/browse/JBIDE-25829 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.3.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.3.AM3 > > > I just noticed there is an error when you start the New Server dialog, select cdk 3.2+ and on the next page you first try to Browse for the minishift binary and then you change your mind and cancel that window. > {code} > Unhandled event loop exception > java.lang.NullPointerException > at java.io.File.<init>(File.java:277) > at org.jboss.tools.openshift.cdk.server.ui.internal.CDK3ServerWizardFragment.kickValidationJob(CDK3ServerWizardFragment.java:218) > at org.jboss.tools.openshift.cdk.server.ui.internal.CDK3ServerWizardFragment.access$3(CDK3ServerWizardFragment.java:214) > at org.jboss.tools.openshift.cdk.server.ui.internal.CDK3ServerWizardFragment$3.widgetSelected(CDK3ServerWizardFragment.java:197) > 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:4258) > 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:4082) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3699) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:58) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565) > at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4258) > 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:4082) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3699) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039) > 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) > {code} > -- 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 March 2018