[JBoss JIRA] (JBIDE-20355) oc location preferences: location is not validated, no help is provided
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20355?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20355:
-------------------------------------
Description:
# EXEC: go to OpenShift v3 preferences (Window->Preferences->OpenShift v3)
# EXEC: hit "Browse" and choose any file (ex. /tmp/test.txt)
Result:
The preferences wont validate your choice. Whatever you pick is used.
!oc-binary-path-not-validated.png!
There also is no explanation to what this "oc binary" is. A dummy user would have no idea what this is all about
Expected:
The preferences should do basic tests like
* is it executable?
* is it an "oc" binary
...and add some explanations on what "oc binary" is and how to obtain it.
was:
# EXEC: go to OpenShift v3 preferences (Window->Preferences->OpenShift v3)
# EXEC: hit "Browse" and choose any file (ex. /tmp/test.txt)
Result:
The preferences wont validate your choice. Whatever you pick is used.
!oc-binary-path-not-validated.png!
There also is no explanation to what this "oc binary" is. A dummy user would have no idea what this is all about
Expected:
The preferences should do basic tests like
* is it executable?
* is it an "oc" binary
Add some explanations on what "oc binary" is and how to obtain it.
> oc location preferences: location is not validated, no help is provided
> -----------------------------------------------------------------------
>
> Key: JBIDE-20355
> URL: https://issues.jboss.org/browse/JBIDE-20355
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Andre Dietisheim
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.3.0.CR1
>
> Attachments: oc-binary-path-not-validated.png
>
>
> # EXEC: go to OpenShift v3 preferences (Window->Preferences->OpenShift v3)
> # EXEC: hit "Browse" and choose any file (ex. /tmp/test.txt)
> Result:
> The preferences wont validate your choice. Whatever you pick is used.
> !oc-binary-path-not-validated.png!
> There also is no explanation to what this "oc binary" is. A dummy user would have no idea what this is all about
> Expected:
> The preferences should do basic tests like
> * is it executable?
> * is it an "oc" binary
> ...and add some explanations on what "oc binary" is and how to obtain it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20377) [origin_intservice_59]Port forwarding info disappeared after refreshing pods
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20377?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-20377:
---------------------------------------
[~adietish] I feared this would come up. This is caused by the limitation in the current design where the port forward process is associated with the capability. If you refresh the pod, then you get a new instance which means you no longer have reference to the process. I presume the process is still running too but now you have no way stop it at all, even if you exit Eclipse. Possible solutions:
* Modify the refresh logic such that you update the object after reload. This is similar to what happened in v2 where significant properties were copied from one object to another
* Add a singleton of some sort for managing the port forward process instances. This would alleviate needing to update objects.
Opinions?
> [origin_intservice_59]Port forwarding info disappeared after refreshing pods
> ----------------------------------------------------------------------------
>
> Key: JBIDE-20377
> URL: https://issues.jboss.org/browse/JBIDE-20377
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta2, 4.3.0.CR1
> Reporter: Yue Wang
> Labels: application_wizard, openshift_v3
>
> Start a port forwarding, you can find port forwarding status 'Started' in 'Application port forwarding' window, then you refresh pod and go to 'Application port forwarding' window again, port forwarding status disappeared.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19948) Reimplement Eclipse Download plugin to allow dynamic work flow
by David Hladky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19948?page=com.atlassian.jira.plugi... ]
David Hladky edited comment on JBIDE-19948 at 7/24/15 7:24 AM:
---------------------------------------------------------------
Hi Rob, thank you for discussing the issue with Max. I would like to add some notes too:
In your yesterday meeting we discussed two things - reading data about files from yaml/rest service. I originally have not thought about it but as we opened this topic I think it is worth discussion, but we should make it a separate issue. I created JBIDE-20375 for it. It would be a nice to have.
The dynamic dialogue is a different thing speaking of the importance though. As I understand you have quite low frequency of releases and because the requirements of management do not respect your release dates it would make it hard to make it consistent with the web pages. But I think the whole thing is simpler than you think and we can limit the dynamic approach to a reasonable complexity.
was (Author: dhladky):
Hi Rob, thank you for discussing the issue with Max. I would like to add some notes too:
In your yesterday meeting we discussed two things - reading data about files from yaml/rest service. I originally have not thought about it but as we opened this topic I think it is worth discussion, but we should make it a separate issue. I created JBIDE-20375 for it.
The dynamic dialogue is a different thing though. As I understand you have quite low frequency of releases and because the requirements of management do not respect your release dates it would make it hard to make it consistent with the web pages. But I think the whole thing is simpler than you think and we can limit the dynamic approach to a reasonable complexity.
> Reimplement Eclipse Download plugin to allow dynamic work flow
> --------------------------------------------------------------
>
> Key: JBIDE-19948
> URL: https://issues.jboss.org/browse/JBIDE-19948
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection, server
> Affects Versions: 4.3.0.Alpha2
> Reporter: David Hladky
> Assignee: Rob Stryker
> Fix For: 4.3.0.CR1
>
>
> We need to reimplement the plugin to accept new terms and conditions models as well as follow the workflow changes in case of changes to the current ones.
> Under this issue I will create the tasks we need to achieve this goal.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months