[JBoss JIRA] (JBIDE-25430) New Openshift Server should not allow editing connection
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25430?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-25430.
---------------------------------
Closing. Verified also with notes in PR.
Verified in:
Red Hat JBoss Developer Studio
Version: 11.2.0.AM3
Build id: AM3-v20171218-0506-B1798
Build date: 20171218-0506
> New Openshift Server should not allow editing connection
> --------------------------------------------------------
>
> Key: JBIDE-25430
> URL: https://issues.jboss.org/browse/JBIDE-25430
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.5.2.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.5.2.AM2
>
>
> The openshift 3 new server wizard page allows you to change the details of the connection you've selected. This already seems very wrong. It's inappropriate for you to be changing the details of a connection that already exists, at least if you're not making a duplicate connection and leaving the original untouched.
> Other server adapters or other parts of code may refer to these connections. Changing them in the new server wizard should not be a primary usecase. If the user does need to change them, it should be done via an 'edit connection' button, so teh user changes the connection but is aware he is changing it and is not simply making a duplicate with slightly different details.
> Some of the fields (in the advanced section) are even changed on the connection EVEN if you CANCEL out of the new server wizard. THis is a big problem, and probably has more to do with the openshift connection API than anything. However, limiting that from occurring in the new server wizard will remove half the ways this bug can occur, so that's still a benefit.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25227) Control dcoration hint is almost hidden in "OpenShift Server Adapter Settings" wizard for Eclipse project field
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25227?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-25227.
---------------------------------
Layout glitch is gone. Tested on Win10, MacOS and FC27.
Verified in:
Red Hat JBoss Developer Studio
Version: 11.2.0.AM3
Build id: AM3-v20171218-0506-B1798
Build date: 20171218-0506
> Control dcoration hint is almost hidden in "OpenShift Server Adapter Settings" wizard for Eclipse project field
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25227
> URL: https://issues.jboss.org/browse/JBIDE-25227
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Priority: Minor
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.5.2.AM2
>
> Attachments: image-2017-10-12-14-32-10-976.png, screenshot-1.png, screenshot-2.png
>
>
> The decoration that indicates that autocomplete is available for the "Eclipse Project" text field in the server adapter wizard is partially cut off by the "Browse" button:
> !screenshot-1.png!
> Weird enough this layout glitch seems only to be happen in Linux? Here's my Mac:
> !screenshot-2.png!
--
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 Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-25303:
------------------------------------
After a long discussion, I agree that the correct route would be 1).
So we just need now to have the Maven project configurator bound to the Maven Spring Boot plugin and correct place would be in jbosstools-central
> 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
[JBoss JIRA] (JBIDE-25507) Move RHAMT tooling out of early access
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25507?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25507:
------------------------------------
After installing the latest JBT 4.5.2.AM3 or 11.2.0.AM3 from the snapshots sites, I can install RHAMT 4.0.0.Final without enabling Early Access connectors:
!install-jbt-central.png|thumbnail!
!install-devstudio-central.png|thumbnail!
!rhamt-no-ea.png|thumbnail!
> Move RHAMT tooling out of early access
> --------------------------------------
>
> Key: JBIDE-25507
> URL: https://issues.jboss.org/browse/JBIDE-25507
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central-update
> Reporter: John Steele
> Assignee: Nick Boldt
> Fix For: 4.5.2.AM3
>
> Attachments: install-devstudio-central.png, install-jbt-central.png, rhamt-no-ea.png
>
>
> RHAMT 4.0.0.Final will be released December 15th, and now that it's GA, we'd like it be out of early access.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months