[JBoss JIRA] (ERT-564) [RedOx] Goal 2.3 - Wizards
by Lucas Bullen (JIRA)
Lucas Bullen created ERT-564:
--------------------------------
Summary: [RedOx] Goal 2.3 - Wizards
Key: ERT-564
URL: https://issues.jboss.org/browse/ERT-564
Project: Eclipse Release Train
Issue Type: Task
Reporter: Lucas Bullen
Assignee: Lucas Bullen
Provide new wizards, launch, export - Cargo (rust build system, which will be provisioned by rustup) provides commands for init (bin or library project), build, package, clean, test, run, rustdoc so all these should be thin layer redirecting to cargo calls
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (ERT-563) [RedOx] Goal 2.2 - Manage Plugin
by Lucas Bullen (JIRA)
Lucas Bullen created ERT-563:
--------------------------------
Summary: [RedOx] Goal 2.2 - Manage Plugin
Key: ERT-563
URL: https://issues.jboss.org/browse/ERT-563
Project: Eclipse Release Train
Issue Type: Task
Reporter: Lucas Bullen
Assignee: Lucas Bullen
Manage rustup from the plugin (preference page) - Check whether ~/.rustup and ~/.cargo contain rustup already and make use of it in this case. If not fetch rustup-init and auto install it. One should be able to switch between stable and nightly toolchain. Have rls-preview, rust-src and rust-analysis component installed/updated using rustup
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25111) Explorer, Properties: allow intellingent "Delete Resource" (via label-matching?)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25111?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25111:
-------------------------------------
Fix Version/s: 4.5.2.AM3
(was: 4.5.2.AM2)
> Explorer, Properties: allow intellingent "Delete Resource" (via label-matching?)
> --------------------------------------------------------------------------------
>
> Key: JBIDE-25111
> URL: https://issues.jboss.org/browse/JBIDE-25111
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.5.2.AM3
>
>
> OpenShift Online only allows you 1 project. Thus the usual approach to create a project per application and kill the project to remove all resources cannot be used in OpenShift online. We thus need a way to delete all resources that are related to an application. Ex. with a more powerful delete action that pops up a window with a filter-/query-parameter that would filter the list of available resources and then allow to delete all the visible (or selected ones)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25375) Server adapter: Problem occured during debugging of Fuse app deployed on open.paas.redhat.com
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25375?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25375:
-------------------------------------
Fix Version/s: 4.5.2.AM3
(was: 4.5.2.AM2)
> Server adapter: Problem occured during debugging of Fuse app deployed on open.paas.redhat.com
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-25375
> URL: https://issues.jboss.org/browse/JBIDE-25375
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM1
> Environment: F27 + open.paas.redhat.com + DevStudio 11.2.0.AM1-v20171106-0622-B1520
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.2.AM3
>
>
> {code:java}
> Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com)
> org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 46271 on localhost
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:639)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:643)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:410)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:395)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:276)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:191)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:167)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:98)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> eclipse.buildId=11.2.0.AM1-v20171106-0622-B1520
> java.version=1.8.0_144
> 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
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[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 updated JBIDE-25303:
-------------------------------------
Fix Version/s: 4.5.2.AM3
(was: 4.5.2.AM2)
> 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.2.AM3
>
> Attachments: fuse-on-openshift.zip, project-deployment-assembly.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.
> # 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