[JBoss JIRA] (JBIDE-22593) New application wizard: preselect v3 connection that I most recently used
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22593?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22593:
-------------------------------------
Fix Version/s: 4.4.1.Final
(was: 4.4.1.AM3)
> New application wizard: preselect v3 connection that I most recently used
> -------------------------------------------------------------------------
>
> Key: JBIDE-22593
> URL: https://issues.jboss.org/browse/JBIDE-22593
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Andre Dietisheim
> Labels: application_wizard, connection_wizard, openshift_v2, openshift_v3
> Fix For: 4.4.1.Final
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> # ASSERT: make sure that you have used a v3 connection (ex. import an application from your OpenShift server to your workspace)
> # EXEC: launch openshift wizard via File->New->OpenShift Application
> # ASSERT: connection dialog shows up
> Result:
> Connection dialog shows up with <New Connection> and connection type "OpenShift 2" pre-selected.
> Expected result:
> Connection dialog has my v3 connection preselected, that I recently used.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ERT-358) Replace traces of old parser in Search/Indexing code. [EBZ#498371]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-358?page=com.atlassian.jira.plugin.sy... ]
Gorkem Ercan updated ERT-358:
-----------------------------
Sprint: devex #118 July 2016
> Replace traces of old parser in Search/Indexing code. [EBZ#498371]
> ------------------------------------------------------------------
>
> Key: ERT-358
> URL: https://issues.jboss.org/browse/ERT-358
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Priority: Trivial
> Labels: General, bzira
>
> Search and Indexing should be changed to use the newer dom ASTParser, instead of the old parser (e.g. in org.eclipse.wst.jsdt.internal.core.search.indexing.SourceIndexer).
> This needs to happen before any other improvements/refinements to JSDT Search.
> Looking at org.eclipse.wst.jsdt.internal.compiler.SourceElementParser, most of the class is using deprecated code.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ERT-358) Replace traces of old parser in Search/Indexing code. [EBZ#498371]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-358:
---------------------------------------
Summary: Replace traces of old parser in Search/Indexing code. [EBZ#498371]
Key: ERT-358
URL: https://issues.jboss.org/browse/ERT-358
Project: Eclipse Release Train
Issue Type: Task
Components: JSDT
Reporter: Friendly Jira Robot
Priority: Trivial
Search and Indexing should be changed to use the newer dom ASTParser, instead of the old parser (e.g. in org.eclipse.wst.jsdt.internal.core.search.indexing.SourceIndexer).
This needs to happen before any other improvements/refinements to JSDT Search.
Looking at org.eclipse.wst.jsdt.internal.compiler.SourceElementParser, most of the class is using deprecated code.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22805) Add Scale... menus on Pod resources
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22805?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22805:
-------------------------------
Fix Version/s: 4.4.1.AM3
> Add Scale... menus on Pod resources
> -----------------------------------
>
> Key: JBIDE-22805
> URL: https://issues.jboss.org/browse/JBIDE-22805
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Fred Bricon
> Fix For: 4.4.1.AM3
>
>
> I'm regularly confused/frustrated to not find the Scale... menus on the running pods. Each time I need to slap myself in the face to remind me I need to go to the Service level.
> I think it'd be more intuitive if the scale menus were present on the running pods (not on the build ones).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22644) Unable to perform oc binary actions because of insecure flag
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22644?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22644:
-------------------------------
Fix Version/s: 4.4.1.AM3
> Unable to perform oc binary actions because of insecure flag
> ------------------------------------------------------------
>
> Key: JBIDE-22644
> URL: https://issues.jboss.org/browse/JBIDE-22644
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.4.1.AM3
>
>
> Trying to retrieve pod logs or any oc binary action results in warning of:
> specifying a root certificates file with the insecure flag is not allowed
> Per deads openshift dev "...it means that your kubeconfig file has a CA set, but you're trying to connect insecurely"
> Persumably this requires us to make sure KUBECONFIG env var is not set when executing oc binary commands.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22433) Properties: Add Storage tab
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22433?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22433:
-------------------------------
Fix Version/s: 4.4.1.AM3
(was: 4.4.x)
Labels: new_and_noteworthy openshift_v3 properties (was: openshift_v3 properties)
> Properties: Add Storage tab
> ---------------------------
>
> Key: JBIDE-22433
> URL: https://issues.jboss.org/browse/JBIDE-22433
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Dmitry Bocharov
> Labels: new_and_noteworthy, openshift_v3, properties
> Fix For: 4.4.1.AM3
>
> Attachments: storage from web console.png
>
>
> We should be able to display Persistent Volume (aka Storage) informations in the OpenShift properties.
> Need to define the extent of the informations to display. At the very least, it should be the same as what the OpenShift Console provides.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months