March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23576) Integration tests global refactoring: org.jboss.tools.cdk.ui.bot.test

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23576?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23576: -------------------------------- Fix Version/s: 4.5.3.AM3 (was: 4.5.x) > Integration tests global refactoring: org.jboss.tools.cdk.ui.bot.test > --------------------------------------------------------------------- > > Key: JBIDE-23576 > URL: https://issues.jboss.org/browse/JBIDE-23576 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: cdk, integration, integration_tests > Fix For: 4.5.3.AM3 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.cdk.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25822) Support setup-cdk in Eclipse

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25822?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-25822: --------------------------------------- In case that we will implement setup-cdk and will use --force flag by default, user could set MINISHIFT_HOME, let's say, to ~ folder. do you know what will happen then? Oh yeah, running setup-cdk --force will delete user's home folder... See: https://issues.jboss.org/browse/CDK-156. We should definitely start discussion about it before going this way... > Support setup-cdk in Eclipse > ---------------------------- > > Key: JBIDE-25822 > URL: https://issues.jboss.org/browse/JBIDE-25822 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.5.3.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > > JBIDE-25753 added support for downloading cdk directly from the IDE. So that moves us closer for the user to be able to avoid CLI at all. But there is still one piece missing - running minishift cdk-setup after you download the binary - without that you still won't be able to run cdk. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25822) Support setup-cdk in Eclipse

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25822?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-25822: --------------------------------------- Also, when I run Setup CDK from the context menu, it will ask me if I want to delete the contents of ~/.minishift. That's not ideal - in general we try to avoid input in the Console view, right? Or do you think it's ok? If we want to avoid it, we could consider using the --force flag. But of course the consequence is that stuff will get deleted without asking first. We could work around that by asking before the command is executed, like: Setup CDK will delete any existing contents of ~/.minishift (or whatever). Do you want to continue? BTW, this should honor the MINISHIFT_HOME variable. I didn't check. Did you implement that? > Support setup-cdk in Eclipse > ---------------------------- > > Key: JBIDE-25822 > URL: https://issues.jboss.org/browse/JBIDE-25822 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.5.3.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > > JBIDE-25753 added support for downloading cdk directly from the IDE. So that moves us closer for the user to be able to avoid CLI at all. But there is still one piece missing - running minishift cdk-setup after you download the binary - without that you still won't be able to run cdk. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25822) Support setup-cdk in Eclipse

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25822?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-25822: --------------------------------------- [~rob.stryker], I tried the PR. Can you specify how it's supposed to work? I noticed that when I right-click the server adapter, there is an item called Setup CDK. Is that it? Or is there more? It would be nice to help the user find it. When you first try to start the server adapter, it will fail. In the console, you will see: You need to run 'minishift setup-cdk' first to install required CDK components. We probably can't do anything about that - change it in any way. But the error window that you throw is another thing - I think you could at least include information on what you need to do, no? It seems like a generic error for any startup failure. But you could still at least include a hint that maybe you need to run Setup CDK first and where to find it. Of course ideally you would detect that setup-cdk is needed and (offer to) run it automatically, but I'm not sure if that's feasible. > Support setup-cdk in Eclipse > ---------------------------- > > Key: JBIDE-25822 > URL: https://issues.jboss.org/browse/JBIDE-25822 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.5.3.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > > JBIDE-25753 added support for downloading cdk directly from the IDE. So that moves us closer for the user to be able to avoid CLI at all. But there is still one piece missing - running minishift cdk-setup after you download the binary - without that you still won't be able to run cdk. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24239) Review Arquillian test cases and update tests

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24239?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24239: ---------------------------------- Fix Version/s: 4.5.3.AM3 (was: 4.5.x) > Review Arquillian test cases and update tests > --------------------------------------------- > > Key: JBIDE-24239 > URL: https://issues.jboss.org/browse/JBIDE-24239 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.5.3.AM3 > > > http://docs.jboss.org/tools/whatsnew/arquillian/arquillian-news-4.1.0.Bet... > http://docs.jboss.org/tools/whatsnew/arquillian/arquillian-news-4.2.0.Alp... > http://docs.jboss.org/tools/whatsnew/arquillian/arquillian-news-4.1.1.Alp... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25830) After starting CDK server adapter OpenShift Connection does not work when oc is not on path

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-25830: ------------------------------------- Summary: After starting CDK server adapter OpenShift Connection does not work when oc is not on path Key: JBIDE-25830 URL: https://issues.jboss.org/browse/JBIDE-25830 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk, openshift Affects Versions: 4.5.3.AM3 Reporter: Josef Kopriva Assignee: Rob Stryker OpenShift connection should be working, when user starts CDK server adapter, even if you do not have oc on path. In my opinion OpenShift connection should be working "out of box" when user starts CDK server adapter. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 edited comment on JBIDE-25303 at 3/20/18 10:54 AM: -------------------------------------------------------------------- [~jkopriva] In the CDK but also on OpenShift online I now see the file transfers happening, but there are still permission issues being reported: {code} rsync: failed to set permissions on "/deployments/BOOT-INF/classes/application.properties": Operation not permitted (1) rsync: failed to set permissions on "/deployments/BOOT-INF/classes/logback.xml": Operation not permitted (1) rsync: failed to set permissions on "/deployments/BOOT-INF/classes/org/mycompany/Application.class": Operation not permitted (1) rsync: failed to set permissions on "/deployments/BOOT-INF/classes/org/mycompany/MyTransformer.class": Operation not permitted (1) rsync: failed to set permissions on "/deployments/BOOT-INF/classes/spring/camel-context.xml": Operation not permitted (1) rsync error: some files could not be transferred (code 23) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-52/rsync/main.c(996) [sender=2.6.9] error: exit status 23 {code} On the positive side the overall functionality seems to work, files are synced. On the negative side, the initial sync reports an annoying and possibly misleading error. Btw. to test this you need to pull the latest fabric8 image. was (Author: adietish): [~jkopriva] In the CDK but also on OpenShift online I now see the file transfers happening, but there are still permission issues being reported: {code} rsync: failed to set permissions on "/deployments/BOOT-INF/classes/application.properties": Operation not permitted (1) rsync: failed to set permissions on "/deployments/BOOT-INF/classes/logback.xml": Operation not permitted (1) rsync: failed to set permissions on "/deployments/BOOT-INF/classes/org/mycompany/Application.class": Operation not permitted (1) rsync: failed to set permissions on "/deployments/BOOT-INF/classes/org/mycompany/MyTransformer.class": Operation not permitted (1) rsync: failed to set permissions on "/deployments/BOOT-INF/classes/spring/camel-context.xml": Operation not permitted (1) rsync error: some files could not be transferred (code 23) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-52/rsync/main.c(996) [sender=2.6.9] error: exit status 23 {code} On the positive side the overall functionality seems to work, files are synced. On the negative side, the initial sync reports an annoying and possibly misleading error. > 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)

8 years, 3 months

1
0
0 / 0

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

by Martin Malina (JIRA)

Martin Malina created JBIDE-25829: ------------------------------------- Summary: 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 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)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25828) Properties: reorganize properties context menu

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-25828: ---------------------------------------- Summary: Properties: reorganize properties context menu Key: JBIDE-25828 URL: https://issues.jboss.org/browse/JBIDE-25828 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.5.2.AM3 Reporter: Andre Dietisheim In JBIDE-20569 we reorganized the context menu in the OpenShift explorer. We should now reorg the one in the properties view to match the "new" layout. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25828) Properties: reorganize properties context menu

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25828?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25828: ------------------------------------- Fix Version/s: 4.5.x > Properties: reorganize properties context menu > ---------------------------------------------- > > Key: JBIDE-25828 > URL: https://issues.jboss.org/browse/JBIDE-25828 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.2.AM3 > Reporter: Andre Dietisheim > Labels: properties, ux > Fix For: 4.5.x > > > In JBIDE-20569 we reorganized the context menu in the OpenShift explorer. We should now reorg the one in the properties view to match the "new" layout. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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