[JBoss JIRA] (JBIDE-25111) Explorer, Properties: allow intellingent "Delete Resource" (via label-matching?)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25111?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25111:
-------------------------------
Attachment: 2018-01-10 at 19-59-40.mp4
> Explorer, Properties: allow intellingent "Delete Resource" (via label-matching?)
> --------------------------------------------------------------------------------
>
> Key: JBIDE-25111
> URL: https://issues.jboss.org/browse/JBIDE-25111
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.5.2.Final
>
> Attachments: 2018-01-10 at 19-59-40.mp4, filter-and-selected-resources.png
>
>
> OpenShift Online only allows you 1 project. Thus the usual approach to create a project per application and kill the project to remove all resources cannot be used in OpenShift online. We thus need a way to delete all resources that are related to an application. Ex. with a more powerful delete action that pops up a window with a filter-/query-parameter that would filter the list of available resources and then allow to delete all the visible (or selected ones)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25551) Format Checker: dont enforce line feed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25551?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25551:
-------------------------------------
Labels: code_format_check (was: )
> Format Checker: dont enforce line feed
> ---------------------------------------
>
> Key: JBIDE-25551
> URL: https://issues.jboss.org/browse/JBIDE-25551
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: code_format_check
> Fix For: 4.5.x
>
>
> Current format checks enforce line feeds which leads to badly readable code when you're using fluent builders like in the following case (see here: https://github.com/jbosstools/jbosstools-openshift/pull/1645/files?diff=u...):
> {code:title=enforced line feeds}
> TableViewer resourcesViewer = new TableViewerBuilder(table, tableContainer)
> .column(resource -> ((IResource) resource).getName()).name("Name").align(SWT.LEFT).weight(1)
> .minWidth(100).buildColumn().column(resource -> ((IResource) resource).getKind()).name("Type")
> .align(SWT.LEFT).weight(1).minWidth(100).buildColumn()
> .column(new LabelsCellLabelProvider(labelFilter)).name("Labels").align(SWT.LEFT).weight(2)
> .minWidth(200).buildColumn().buildViewer();
> {code}
> {code:title=manual line feeds with superior readability}
> TableViewer resourcesViewer = new TableViewerBuilder(table, tableContainer)
> .column(resource -> ((IResource) resource).getName())
> .name("Name").align(SWT.LEFT).weight(1).minWidth(100).buildColumn()
> .column(resource -> ((IResource) resource).getKind())
> .name("Type").align(SWT.LEFT).weight(1).minWidth(100).buildColumn()
> .column(new LabelsCellLabelProvider(labelFilter))
> .name("Labels").align(SWT.LEFT).weight(2).minWidth(200).buildColumn()
> .buildViewer();
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25551) Format Checker: dont enforce line feed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25551?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25551:
------------------------------------------
We currently use formatter plugin version 2.0.1 which doesnt seem to honour the above flag. When using the latest 2.7.1 though the flag seems getting honoured but the maven build fails stating 2.7.1 "Workspace closed". This is known to happen with Eclipse Oxygen 1a: https://github.com/revelc/formatter-maven-plugin/issues/260
Version 2.7.0 doesnt have the issue. But then, plenty of new complaints show up.
I'm postponing this to after 4.5.3.Final since there's no urgency for this.
> Format Checker: dont enforce line feed
> ---------------------------------------
>
> Key: JBIDE-25551
> URL: https://issues.jboss.org/browse/JBIDE-25551
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Fix For: 4.5.x
>
>
> Current format checks enforce line feeds which leads to badly readable code when you're using fluent builders like in the following case (see here: https://github.com/jbosstools/jbosstools-openshift/pull/1645/files?diff=u...):
> {code:title=enforced line feeds}
> TableViewer resourcesViewer = new TableViewerBuilder(table, tableContainer)
> .column(resource -> ((IResource) resource).getName()).name("Name").align(SWT.LEFT).weight(1)
> .minWidth(100).buildColumn().column(resource -> ((IResource) resource).getKind()).name("Type")
> .align(SWT.LEFT).weight(1).minWidth(100).buildColumn()
> .column(new LabelsCellLabelProvider(labelFilter)).name("Labels").align(SWT.LEFT).weight(2)
> .minWidth(200).buildColumn().buildViewer();
> {code}
> {code:title=manual line feeds with superior readability}
> TableViewer resourcesViewer = new TableViewerBuilder(table, tableContainer)
> .column(resource -> ((IResource) resource).getName())
> .name("Name").align(SWT.LEFT).weight(1).minWidth(100).buildColumn()
> .column(resource -> ((IResource) resource).getKind())
> .name("Type").align(SWT.LEFT).weight(1).minWidth(100).buildColumn()
> .column(new LabelsCellLabelProvider(labelFilter))
> .name("Labels").align(SWT.LEFT).weight(2).minWidth(200).buildColumn()
> .buildViewer();
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25551) Format Checker: dont enforce line feed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25551?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25551:
-------------------------------------
Fix Version/s: 4.5.x
> Format Checker: dont enforce line feed
> ---------------------------------------
>
> Key: JBIDE-25551
> URL: https://issues.jboss.org/browse/JBIDE-25551
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Fix For: 4.5.x
>
>
> Current format checks enforce line feeds which leads to badly readable code when you're using fluent builders like in the following case (see here: https://github.com/jbosstools/jbosstools-openshift/pull/1645/files?diff=u...):
> {code:title=enforced line feeds}
> TableViewer resourcesViewer = new TableViewerBuilder(table, tableContainer)
> .column(resource -> ((IResource) resource).getName()).name("Name").align(SWT.LEFT).weight(1)
> .minWidth(100).buildColumn().column(resource -> ((IResource) resource).getKind()).name("Type")
> .align(SWT.LEFT).weight(1).minWidth(100).buildColumn()
> .column(new LabelsCellLabelProvider(labelFilter)).name("Labels").align(SWT.LEFT).weight(2)
> .minWidth(200).buildColumn().buildViewer();
> {code}
> {code:title=manual line feeds with superior readability}
> TableViewer resourcesViewer = new TableViewerBuilder(table, tableContainer)
> .column(resource -> ((IResource) resource).getName())
> .name("Name").align(SWT.LEFT).weight(1).minWidth(100).buildColumn()
> .column(resource -> ((IResource) resource).getKind())
> .name("Type").align(SWT.LEFT).weight(1).minWidth(100).buildColumn()
> .column(new LabelsCellLabelProvider(labelFilter))
> .name("Labels").align(SWT.LEFT).weight(2).minWidth(200).buildColumn()
> .buildViewer();
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25295) Cannot use minishift binary instead of CDK in CDK server adapter in IDE
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25295?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25295:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.2.AM3)
> Cannot use minishift binary instead of CDK in CDK server adapter in IDE
> -----------------------------------------------------------------------
>
> Key: JBIDE-25295
> URL: https://issues.jboss.org/browse/JBIDE-25295
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.5.1.Final
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.5.x
>
> Attachments: Screenshot_20171025_134414.png
>
>
> I am curious what if user will want to use upstream minishift binary for CDK 3.x (3.2+) server adapter. It is not possible now.
> Is there a reason for not allowing user to use upstream minishift binary? Before we did not distinguish between CDK 3.1 and 3.2, it was possible in my opinion. We lost this option when new adapter was added and we started to check CDK v.3.x.x version string for two CDK 3.1 and CDK 3.2 binaries.
> [~rob.stryker] [~jeffmaury] [~mmalina] WDYT?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25547) Connection wizard: cannot save connection if "oc location" in preferences is invalid unless you override
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25547?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-25547:
----------------------------------------
Assignee: Rob Stryker
> Connection wizard: cannot save connection if "oc location" in preferences is invalid unless you override
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25547
> URL: https://issues.jboss.org/browse/JBIDE-25547
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
> Attachments: connection-wizard.png
>
>
> # ASSERT: make sure that you have the location to the oc binary set in OpenShift 3 preferences JBoss Tools > OpenShift 3 > 'oc' executable location
> # EXEC: rename the oc (that your preferences point to) so that the preferences value gets invalid
> (this happens if you setup a new cdk since you have to kill your .minishift and the path to the oc contains a folder named after the version of it: ex. ~/.minishift/cache/oc/v3.6.173.0.21/oc)
> # EXEC: launch connection wizard
> # EXEC: provide server url and authentication means
> # ASSERT: "Finish" is still disabled, an error about oc location is shown in the title area
> !connection-wizard.png!
> Result:
> You cannot save your connection unless you override the oc location for this connection. In order to correct the preferences you have to cancel the wizard and go to the preferences. Once you correct the value in preferences, you are not prevented from saving the connection any more.
> Expected result:
> Either allow saving the connection even with an invalid oc location in preferences or allow to get to the preferences and correct it there.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months