[JBoss JIRA] (JBIDE-21464) Explorer: Delete context menu of OpenShift elements is incorrect
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21464?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21464.
---------------------------------
... and closing.
> Explorer: Delete context menu of OpenShift elements is incorrect
> ----------------------------------------------------------------
>
> Key: JBIDE-21464
> URL: https://issues.jboss.org/browse/JBIDE-21464
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: explorer, openshift_v2, openshift_v3
> Fix For: 4.3.1.Beta2
>
>
> Currently OpenShift tree items in OpenShift Explorer view have "Delete" context menu item. Previously it was more natural, because we had "Delete connection(s)..." "Delete domain..." etc., not it is all "Delete".
> If just plain "Delete" is considered as a good way to go, at least there should be three dots as suffix, because after click on the context menu Delete there is required user confirmation of deletion. So it should be at least "Delete...".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21472) Server Adapter: Missing context menu item to show application details
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21472?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21472.
---------------------------------
Verified in nigthly build of JBDS 9.1.0.Beta2 with OpenShift tools plugin of version 3.1.0.Beta2-v20160119-1135-B153.
> Server Adapter: Missing context menu item to show application details
> ---------------------------------------------------------------------
>
> Key: JBIDE-21472
> URL: https://issues.jboss.org/browse/JBIDE-21472
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v2, server_adapter
> Fix For: 4.3.1.Beta2
>
>
> In some commit context menu item to show application details of an OpenShift 2 application in OpenShift explorer view was changed from Application details to Properties, what is ok. But probably at same point context menu for properties/application details vanished from OpenShift 2 Server Adapter. There is no context menu "Properties" or "Application details" or any other.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-20935:
------------------------------------------------
I play with this issue and notice that this is not reproducible on Windows if Webkit is used as a browser engine. It means that this is IE + FormEditor problem, cause everything is fine with i.e. HTML editor or with default browser. Also IE 11 by itself works fine.
So here we have very strange case which look like upstream, but I have absolutely no idea how to fix it.
> Central doesn't scale back after being enlarged on Windows
> ----------------------------------------------------------
>
> Key: JBIDE-20935
> URL: https://issues.jboss.org/browse/JBIDE-20935
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Final
> Environment: Windows 10
> 250% UI scale
> Reporter: Jan Richter
> Assignee: Konstantin Marmalyukov
> Labels: ui-scaling
> Fix For: 4.3.x, 4.4.x
>
> Attachments: central.png, JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4, screenshot-1.png
>
>
> When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars.
> Like so:
> !central.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21481) [server adapter] Allow publishing of wtp-style projects
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21481?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21481:
-------------------------------------
To properly get WTP-style projects deployed, a significant number of changes really need to be made to openshift server adapter. In reality, the behavior of the server should really be customized based on what we know of the pod's type (if it's possible to get such information). If we know the POD is an eap server, we'd use a lot of logic from astools, including being able to set .dodeploy markers and check server status and module deployment status.
If the remote pod is something set up for node.js or php or other simple file-tree style projects, it'd use a much more simplified set of logic without any of these extras built in.
The currently attached PR doesn't do the .dodeploy stuff, and so in reality, this patch only really allows changes to html files unless the user is willing to go in and touch the .dodeploy file in the (workspaceroot)/.metadata/.plugins/org.jboss.ide.eclipse.as.core/eap-app_at_OpenShift_3_(192.168.121.62)/deploy/ROOT.war.dodeploy file.
However, once the user does that once, all future rsync's seem to always initiate a new full reload of the app on the server, and so we stop getting class errors when executing actions on kitchensink that require interaction with servlets or classes. Obviously this behaviour isn't ideal, since setting the .dodeploy once will result in every publish being a full restart of the module.
But I think this patch is valuable for a beta2 to get some more user feedback on how it's working, what doesn't flow, and what can be improved.
> [server adapter] Allow publishing of wtp-style projects
> -------------------------------------------------------
>
> Key: JBIDE-21481
> URL: https://issues.jboss.org/browse/JBIDE-21481
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Affects Versions: 4.3.1.Beta1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.Beta2
>
>
> The openshift server adapter as currently coded simply copies the magic project into a hidden metadata location and executes an rsync. This won't work for any project iwth a custom wtp-style layout and mappings available, including maven projects created via m2ewtp.
> This jira targets an initial implementation of a zipped publish of wtp-style projects, both as the magic project or as an added module to be deployed along-side the magic project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months