[JBoss JIRA] (JBIDE-23625) JMX: jmx tree is not very usable
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23625?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23625:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.3.AM2)
> JMX: jmx tree is not very usable
> --------------------------------
>
> Key: JBIDE-23625
> URL: https://issues.jboss.org/browse/JBIDE-23625
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Andre Dietisheim
> Fix For: 4.4.3.AM1
>
> Attachments: image-2016-12-02-16-47-59-519.png
>
>
> steps to reproduce:
> # EXEC: create a new app via eap64-basic-s2i template and import the source to a workspace project
> # EXEC: create a server adapter for it
> # ASSERT: your server adapter now has a JMX child node
> # EXEC: double click it and wait until all MBeans are loaded
> # EXEC: now try to see if you can find your deployment
> Result:
> You get a listing of tons of beans.
> !mbeans.png!
> Your deployment is a child bean of jboss.as, named by the war that was created:
> !mbean-deployment.png!
> Rather painfull to find a listing of your deployments in this way.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (JBIDE-23602) Server adapter: Hot code replace failed dialog has poor usability
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23602?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23602:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.3.AM2)
> Server adapter: Hot code replace failed dialog has poor usability
> -----------------------------------------------------------------
>
> Key: JBIDE-23602
> URL: https://issues.jboss.org/browse/JBIDE-23602
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Andre Dietisheim
> Fix For: 4.4.3.AM1
>
> Attachments: hot-code-replace-failed-2.png
>
>
> steps to reproduce:
> # ASSERT: have jboss-helloworld running in OpenShift (create it via eap64-basic-s2i template), the source code for it imported to a workspace project and a server adapter for it
> # EXEC: open HelloService and change it to the following:
> {code:title=HelloService}
> public class HelloService {
> private static final String MAGIC_STRING = "42";
>
> String createHelloMessage(String name) {
> return "Hello " + name + ", the magic string is " + MAGIC_STRING + "!";
> }
> }
> {code}
> and save the editor
> Result:
> "Hot code replace failed" dialog pops up, which is expected.
> !hot-code-replace-failed-2.png!
> But it's usability is poor:
> * the affected module is not fully shown (half of it cut off)
> * there's no margin on the right border of the dialog
> * No button is pre-selected so that I can simply hit Return to pick a sane default choice (I have to hit tap to get to the button I want to press or use my mouse).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (JBIDE-23490) Provide ability to link pods when no service is available
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23490:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.3.AM2)
> Provide ability to link pods when no service is available
> ---------------------------------------------------------
>
> Key: JBIDE-23490
> URL: https://issues.jboss.org/browse/JBIDE-23490
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy
> Fix For: 4.4.3.AM1
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application.
> The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23136:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.3.AM2)
> Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-23136
> URL: https://issues.jboss.org/browse/JBIDE-23136
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.3.AM1
>
> Attachments: eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png
>
>
> I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see:
> 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB
> Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411
> Steps to reproduce:
> - have a project with a file named {{Dockerfile}} with the following content (1 line):
> {code}
> FROM fedora:latest
> {code}
> - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}})
> - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}.
> - In the wizard, select the option to push the image to the registry (add a dummy port if needed)
> - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (JBIDE-22375) Improve HCR OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22375?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22375:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.3.AM2)
> Improve HCR OpenShift
> ---------------------
>
> Key: JBIDE-22375
> URL: https://issues.jboss.org/browse/JBIDE-22375
> Project: Tools (JBoss Tools)
> Issue Type: Epic
> Components: jmx, openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.3.AM1
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (JBIDE-16879) Explorer: context menu for cartridges opens away from cartridge
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16879?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16879:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.3.AM2)
> Explorer: context menu for cartridges opens away from cartridge
> ---------------------------------------------------------------
>
> Key: JBIDE-16879
> URL: https://issues.jboss.org/browse/JBIDE-16879
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.2.0.Beta1
> Environment: Fedora 19, 64-bit, java version "1.7.0_51", OpenJDK Runtime Environment (fedora-2.4.5.0.fc19-x86_64 u51-b31) GTK3
> Reporter: Michelle Murray
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: explorer, gtk3, openshift_v2, openshift_v3, upstream
> Fix For: 4.4.3.AM1
>
> Attachments: OpenShift_conmenu.png
>
>
> In OpenShift Explorer view, expand tree down to cartridge level for an app. Right-click cartridge. The context menu opens away from mouse pointer rather than adjacent to it as it does for other tree items, like connection, domain or app.
> I can 100% of time reproduce it by first right-clicking app and then immediately right-clicking (twice) cartridge.
> I can't reproduce it by first right-clicking connection or domain and then immediately right-clicking (twice) cartridge.
> !OpenShift_conmenu.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months