[JBoss JIRA] (JBIDE-22065) Application wizard: Validation error description in Resource Labels page is cut off
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22065?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22065.
---------------------------------
Verified in JBDS 10.0.0.Alpha1 B5227.
> Application wizard: Validation error description in Resource Labels page is cut off
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-22065
> URL: https://issues.jboss.org/browse/JBIDE-22065
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Final
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: resource_label_complete.png, resource_label_incomplete.png
>
>
> In Resource Label dialog there is a validation error description about correct format of a label. But the validation error description is cut off. On first sight it does not look like like cut off, but after resizing a shell more text is showed. See following image of cut off description:
> !resource_label_incomplete.png!
> And following image contains full description after resizing to "long enough" width:
> !resource_label_complete.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3698) Installer - We should document (rel notes) the versions of the installable components that we support
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/JBDS-3698?page=com.atlassian.jira.plugin.... ]
Misha Ali commented on JBDS-3698:
---------------------------------
Changed "If the following components are not detected, they will be installed. If they are detected, they are updated or downgraded according to the installer requirements." to one list of components and versions under "If not found, or if an older version is installed, the following supported versions will then be installed for you by the installer:"
https://access.redhat.com/articles/2255391
[~jrichter1] please review.
> Installer - We should document (rel notes) the versions of the installable components that we support
> -----------------------------------------------------------------------------------------------------
>
> Key: JBDS-3698
> URL: https://issues.jboss.org/browse/JBDS-3698
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: documentation, platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Misha Ali
> Labels: havoc
> Fix For: 10.0.0.Alpha1
>
>
> It's good that the installer will allow users to have/retain their own installed components, and verify that the installed versions are supported, but we should provide the users with a documented list of the ranges of supported versions. Thx!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22242) OpenShift Explorer: Reorganize context menus
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22242?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22242:
---------------------------------------
And New context menu should have ordered context menu items in following order (top copy top-down, from most important to least, used on other places)
{code}Connection...
Project...
Application...
{code}
> OpenShift Explorer: Reorganize context menus
> --------------------------------------------
>
> Key: JBIDE-22242
> URL: https://issues.jboss.org/browse/JBIDE-22242
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: explorer, openshift_v3, ux
> Fix For: 4.4.0.Alpha2
>
> Attachments: connection_cm.png, pod_cm.png, project_cm.png, service_cm.png
>
>
> It would be nice if we would have context menus of OpenShift elements in OpenShift Explorer view a bit reorganized, because at the moment some of them seems to be for me a bit messy (as least context menu of a service).
> See screenshots of context menus:
> connection
> !connection_cm.png!
> project
> !project_cm.png!
> service
> !service_cm.png!
> pod
> !pod_cm.png!
> Here is the guideline how should context menus look like
> https://wiki.eclipse.org/User_Interface_Guidelines#Context_Menus_2
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22242) OpenShift Explorer: Reorganize context menus
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22242?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-22242 at 4/26/16 5:01 AM:
----------------------------------------------------------------
And New context menu item should have ordered sub context menu items in following order (top copy top-down, from most important to least, used on other places)
{code}Connection...
Project...
Application...
{code}
was (Author: mlabuda):
And New context menu should have ordered context menu items in following order (top copy top-down, from most important to least, used on other places)
{code}Connection...
Project...
Application...
{code}
> OpenShift Explorer: Reorganize context menus
> --------------------------------------------
>
> Key: JBIDE-22242
> URL: https://issues.jboss.org/browse/JBIDE-22242
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: explorer, openshift_v3, ux
> Fix For: 4.4.0.Alpha2
>
> Attachments: connection_cm.png, pod_cm.png, project_cm.png, service_cm.png
>
>
> It would be nice if we would have context menus of OpenShift elements in OpenShift Explorer view a bit reorganized, because at the moment some of them seems to be for me a bit messy (as least context menu of a service).
> See screenshots of context menus:
> connection
> !connection_cm.png!
> project
> !project_cm.png!
> service
> !service_cm.png!
> pod
> !pod_cm.png!
> Here is the guideline how should context menus look like
> https://wiki.eclipse.org/User_Interface_Guidelines#Context_Menus_2
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22142) Watches should not try to reconnect when a project has been deleted
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22142?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22142.
---------------------------------
Verified in JBDS 10.0.0.Alpha1 B5227.
> Watches should not try to reconnect when a project has been deleted
> -------------------------------------------------------------------
>
> Key: JBIDE-22142
> URL: https://issues.jboss.org/browse/JBIDE-22142
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Labels: respin-b
> Fix For: 4.4.0.Alpha1
>
>
> When a project has been deleted from the webconsole, the watchmanager in eclipse is not notified. Each watch that times out tries to reconnect to some of the dead project's urls. Each access is rejected with 403 errors (the project could exist but not be visible to the user).
> After each attempt, the watches will wait a little longer before trying to reconnect, until it eventually stops trying.
> Since the watch manager has access to the projects, it can try to check the project exists before connecting the watch
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-20415) Runtime download hyperlink not working from New Server dialog on Mac - upstream
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20415?page=com.atlassian.jira.plugi... ]
Martin Malina resolved JBIDE-20415.
-----------------------------------
Fix Version/s: 4.3.1.Final
(was: 4.4.x)
Resolution: Cannot Reproduce Bug
So I read through the original JIRA again: JBIDE-19637
And to refresh everybody's memory a bit: What was causing problems on Mac was if there were several hyperlinks in the workflow, like this:
1. Go to Servers view with no servers present
2. Click the link (hyperlink 1) to add a new server
3. Select an EAP server, Next, Create new runtime
4. Now click the link to download the runtime (hyperlink 2)
At this point, the second link would not work, even after the workaround that Rob pushed.
But now I tried this again with JBDS 9.1.0.GA and it works just fine for me. So have no choice but to close this JIRA.
> Runtime download hyperlink not working from New Server dialog on Mac - upstream
> -------------------------------------------------------------------------------
>
> Key: JBIDE-20415
> URL: https://issues.jboss.org/browse/JBIDE-20415
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.Final
>
>
> When you go through Servers view -> New Server -> EAP 6.1 -> New Runtime and then click "Download and install runtime...", it won't do anything.
> If you go through Preferences -> Server -> Runtime Environments -> Add -> EAP 6.1+ and then click the Download button, it will work.
> This issue applies to both JBDS 8.1.0.GA and JBoss Tools 4.3.0.Alpha2 testing build, but I doubt we will be able to fix this for 4.2.x.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months