[JBoss JIRA] (JBIDE-20001) Confusing New->Connection dialog that tells v3 and Enterprise users to create an Online account
by Steve Speicher (JIRA)
Steve Speicher created JBIDE-20001:
--------------------------------------
Summary: Confusing New->Connection dialog that tells v3 and Enterprise users to create an Online account
Key: JBIDE-20001
URL: https://issues.jboss.org/browse/JBIDE-20001
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Alpha2
Reporter: Steve Speicher
Priority: Minor
The Eclipse tooling is intended to be used with V2 Online (for now) and V3 when it is available. Also it is intended to be used with on-premise Enterprise instances, which do not require an Online account. This instruction may be confusing to these customers.
Along these lines, the V3 Server is prefilled with the URL for the online service which may not work for some time. I propose selecting a different default value for V3
An alternative could be that after they enter the URL they could attempt to "valid it" or "open in browser".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20000) Creating more readonly labels should not be possible
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20000?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-20000:
----------------------------------
Description:
In New application wizard for v3 connection there is a label management wizard page, where user can create/edit/remove label. It is possible to create more readonly labels, e.g. I was able to create another "template" label which already exists in table and is readonly (edit and remove button are disabled for this label). After the label is created it it not possible to edit/remove it.
!readonly_labels.png!
was:In New application wizard for v3 connection there is a label management wizard page, where user can create/edit/remove label. It is possible to create more readonly labels, e.g. I was able to create another "template" label which already exists in table and is readonly (edit and remove button are disabled for this label)
> Creating more readonly labels should not be possible
> ----------------------------------------------------
>
> Key: JBIDE-20000
> URL: https://issues.jboss.org/browse/JBIDE-20000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Attachments: readonly_labels.png
>
>
> In New application wizard for v3 connection there is a label management wizard page, where user can create/edit/remove label. It is possible to create more readonly labels, e.g. I was able to create another "template" label which already exists in table and is readonly (edit and remove button are disabled for this label). After the label is created it it not possible to edit/remove it.
> !readonly_labels.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20000) Creating more readonly labels should not be possible
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20000?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-20000:
----------------------------------
Priority: Critical (was: Major)
> Creating more readonly labels should not be possible
> ----------------------------------------------------
>
> Key: JBIDE-20000
> URL: https://issues.jboss.org/browse/JBIDE-20000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Priority: Critical
> Attachments: readonly_labels.png
>
>
> In New application wizard for v3 connection there is a label management wizard page, where user can create/edit/remove label. It is possible to create more readonly labels, e.g. I was able to create another "template" label which already exists in table and is readonly (edit and remove button are disabled for this label). After the label is created it it not possible to edit/remove it.
> !readonly_labels.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20000) Creating more readonly labels should not be possible
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20000?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-20000:
----------------------------------
Attachment: readonly_labels.png
> Creating more readonly labels should not be possible
> ----------------------------------------------------
>
> Key: JBIDE-20000
> URL: https://issues.jboss.org/browse/JBIDE-20000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Attachments: readonly_labels.png
>
>
> In New application wizard for v3 connection there is a label management wizard page, where user can create/edit/remove label. It is possible to create more readonly labels, e.g. I was able to create another "template" label which already exists in table and is readonly (edit and remove button are disabled for this label)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19980) (New HTML5) Central search results have low contrast
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19980?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19980:
---------------------------------------
Cool. So if I removed the #666 (is this the proverbial devel which is in the details?) on the text, the resulting color looked good to me. If I changed it to #111, it was darker than after just removing it, so the color that I liked (still not all the way black) was inherited from somewhere. I think it's #333 that I like. In jboss-app.css, the original #666 is after line 8585 and the inherited #333333 is after line 1722.
> (New HTML5) Central search results have low contrast
> ----------------------------------------------------
>
> Key: JBIDE-19980
> URL: https://issues.jboss.org/browse/JBIDE-19980
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
> Assignee: Fred Bricon
> Priority: Optional
> Fix For: 4.3.0.Beta2
>
> Attachments: central-results.png
>
>
> When you search for something in the new html5 central, the results seem pretty low contrast to me, it almost seems like they are disabled or something.
> Got a +1 from Max, too ;)
> {quote}
> [max] agreed - I would go for a darker black there
> {quote}
> !central-results.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20000) Creating more readonly labels should not be possible
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-20000:
-------------------------------------
Summary: Creating more readonly labels should not be possible
Key: JBIDE-20000
URL: https://issues.jboss.org/browse/JBIDE-20000
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Beta1
Reporter: Marián Labuda
In New application wizard for v3 connection there is a label management wizard page, where user can create/edit/remove label. It is possible to create more readonly labels, e.g. I was able to create another "template" label which already exists in table and is readonly (edit and remove button are disabled for this label)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19999) v3 Logging into a server that doesn't support OAuth doesn't provide feedback/error
by Steve Speicher (JIRA)
Steve Speicher created JBIDE-19999:
--------------------------------------
Summary: v3 Logging into a server that doesn't support OAuth doesn't provide feedback/error
Key: JBIDE-19999
URL: https://issues.jboss.org/browse/JBIDE-19999
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Alpha2
Reporter: Steve Speicher
Priority: Minor
Would be "nice" if client could discover what the server supports. If use selects the wrong thing, it would be good to present with appropriate error/message.
eclipse.buildId=4.5.0.I20150528-0700
java.version=1.8.0_40
java.vendor=Oracle Corporation
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product -keyring /Users/sspeiche/.eclipse_keyring -showlocation
Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product -data file:/Users/sspeiche/Documents/workspace/mars/ -product org.eclipse.epp.package.jee.product -keyring /Users/sspeiche/.eclipse_keyring -showlocation
org.jboss.tools.openshift.ui
Error
Tue Jun 09 10:22:09 EDT 2015
Could not display malformed url "".
java.net.MalformedURLException: no protocol:
at java.net.URL.<init>(URL.java:586)
at java.net.URL.<init>(URL.java:483)
at java.net.URL.<init>(URL.java:432)
at org.jboss.tools.foundation.ui.util.BrowserUtility.openUrl(BrowserUtility.java:60)
at org.jboss.tools.foundation.ui.util.BrowserUtility.checkedCreateExternalBrowser(BrowserUtility.java:51)
at org.jboss.tools.openshift.internal.ui.wizard.connection.OAuthDetailView$AuthLinkHandler$1$1.run(OAuthDetailView.java:224)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:172)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:387)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002)
at org.jboss.tools.common.ui.WizardUtils.runInWizard(WizardUtils.java:129)
at org.jboss.tools.common.ui.WizardUtils.runInWizard(WizardUtils.java:93)
at org.jboss.tools.common.ui.WizardUtils.runInWizard(WizardUtils.java:71)
at org.jboss.tools.openshift.internal.ui.wizard.connection.OAuthDetailView$AuthLinkHandler.widgetSelected(OAuthDetailView.java:232)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1564)
at org.eclipse.swt.widgets.Link.textView_clickOnLink_atIndex(Link.java:117)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:6010)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227)
at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1121)
at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1113)
at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2569)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5692)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSend_bool(Native Method)
at org.eclipse.swt.internal.cocoa.NSRunLoop.runMode(NSRunLoop.java:42)
at org.eclipse.swt.widgets.Display.sleep(Display.java:4740)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:828)
at org.eclipse.jface.window.Window.open(Window.java:803)
at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:244)
at org.jboss.tools.openshift.internal.common.ui.command.NewConnectionHandler.execute(NewConnectionHandler.java:29)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19476) Add label validation
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19476?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-19476.
---------------------------------
Verified in JBDS 9.0.0.Beta1 build id B34.
> Add label validation
> --------------------
>
> Key: JBIDE-19476
> URL: https://issues.jboss.org/browse/JBIDE-19476
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
>
> Add label key and value validations to the 'label' page in accordance of what is valid in Kubernetes. This should be part of the 'edit label' page that will be presented to a user
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19958) Labels are not added to resources when creating a new app from template
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19958?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-19958:
----------------------------------
Fix Version/s: 4.3.0.Beta2
> Labels are not added to resources when creating a new app from template
> -----------------------------------------------------------------------
>
> Key: JBIDE-19958
> URL: https://issues.jboss.org/browse/JBIDE-19958
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.3.0.Beta2
>
>
> # EXEC: launch new application wizard using an OpenShift v3 server
> # ASSERT: application wizard shows up listing the projects and templates (child nodes)
> # EXEC: choose a template and hit "Next"
> # EXEC: in "Template Parameters" page do nothing, hit "Next"
> # EXEC: in "Resource Labels" page hit "Add" and create some new label
> # EXEC: hit "Finish"
> # ASSERT: all resources of the template were successfully created.
> # ASSERT: make sure that you have the properties view opened and visible while you browse the resources in OpenShift explorer
> # EXEC: select a freshly created resource and check in the properties view if the label was created
> Result:
> Note none of the server resources have the added label when they should. The server should apply all template labels to its child items. We need to confirm that we are correctly updating those labels before template processing so it can apply them.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3297) Download/Import Existing OpenShift Project
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBDS-3297?page=com.atlassian.jira.plugin.... ]
Marián Labuda closed JBDS-3297.
-------------------------------
Verified in JBDS 9.0.0.Beta1 build id B34.
> Download/Import Existing OpenShift Project
> ------------------------------------------
>
> Key: JBDS-3297
> URL: https://issues.jboss.org/browse/JBDS-3297
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift, requirements
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 9.0.0.Beta1
>
>
> Use Case #1 - Download/Import Existing OpenShift Project
> a) Assume OpenShift is started remotely and provides an entrypoint URL (e.g. http://localhost:8080/osapi/v1beta1/projects)
> b) Assume end-user is logged in (ignore auth for now)
> c) Assume OpenShift already has some deployed "projects", this "project" definition includes the buildconfig, deployconfig, docker image, source git URL, routes and services.
> d) Eclipse user will open a dialog and enter the URL from step a
> e) Eclipse user will see a list of "things" associated with "projects" from step 1c
> "things"
> f) Embedded in one of those things is a Git URL - that will be displayed to the user who will agree to git clone it [1f]
> g) If the downloaded items include a Maven project, the Eclipse user will see a newly configured Eclipse project based on Maven with the appropriately configured facets
> h) If there is no pom.xml, the Eclipse user will see a newly configured generic Eclipse project containing the downloaded files
> i) It is expected that a Maven-based Java project will build locally (leveraging Maven Central and/or maven.repository.redhat.com)
> j) It is expected that a Maven-based Java project will deploy to a localhost EAP/Wildfly or a locally running Docker container:
> docker run -it -p 8080:8080 openshift/wildfly-8-centos
> [1f] https://github.com/openshift/origin/blob/master/examples/sample-app/appli...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months