[JBoss JIRA] (JBIDE-17905) Server Adapter: cannot publish commits (only) when there are local changes (can only commit and push)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17905?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17905:
-------------------------------------
Labels: new_and_noteworthy server_adapter (was: server_adapter)
Affects Version/s: 4.2.0.Beta3
> Server Adapter: cannot publish commits (only) when there are local changes (can only commit and push)
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17905
> URL: https://issues.jboss.org/browse/JBIDE-17905
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: new_and_noteworthy, server_adapter
> Fix For: 4.2.0.CR1
>
> Attachments: publish-dialog.ogv
>
>
> # EXEC: Add file test.txt
> # EXEC: Commit test.txt
> # EXEC: Add file temporary.txt
> # EXEC: go to openshift server and publish
> # ASSERT: commit dialog shows up
> # ASSERT: I can push the new commits without having to do something about temporary.txt
> this worked in past, now the new commit dialog prevents me from doing this.
> I can use egit push to workaround this but that kinda defeats the purpose of making the server interaction simple via just the "Publish" command.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17968) Application wizard: take less less screen height
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17968?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17968:
-------------------------------------
Affects: Documentation (Ref Guide, User Guide, etc.),Interactive Demo/Tutorial
> Application wizard: take less less screen height
> ------------------------------------------------
>
> Key: JBIDE-17968
> URL: https://issues.jboss.org/browse/JBIDE-17968
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta2
> Environment: Fedora, 1440x900 resolution screen
> Reporter: Catherine Robson
> Assignee: Andre Dietisheim
> Labels: application_wizard, uxtest
> Fix For: 4.2.0.CR1
>
> Attachments: app-config-wizard-page.png, openshift-wizard-title-area.png, shortened-application-wizard.png, wizard-too-tall.png
>
>
> For users with small screen sizes, the OpenShift create application wizard is very tall and might overflow their screen real-estate. Many of the dialogs in this wizard have lots of wasted space, so we should see if we can reduce the size of these dialogs as much as possible.
> The height of the dialog is ~870px high. The most common resolution people run these days is 1366x768 - meaning we're already too high for people's viewable screen.
> !wizard-too-tall.png!
> ----------------
> Screen by screen analysis
> ----------------
> Sign in dialog - ~550px wasted height: https://www.evernote.com/shard/s230/sh/baf765b4-cee1-470c-88a0-1afd237868...
> Existing or new application dialog - ~145px wasted height: https://www.evernote.com/shard/s230/sh/d76f10b6-fb40-455d-bef6-d1b1ea44b0...
> Name, domain, and embedded cartridges dialog - ~200px wasted height: https://www.evernote.com/shard/s230/sh/04381c6a-e9d7-4c6a-bd47-15b5b83a8e...
> Configure project dialog - ~550px wasted height: https://www.evernote.com/shard/s230/sh/4932fd92-12b3-456f-8f9c-a25548f4f6...
> Clone settings, processing dialog - ~480px wasted height: https://www.evernote.com/shard/s230/sh/0d921581-6d12-4ba0-8c99-dc4c904e90...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17954) Logs: openshift puts info logs when authenticating in error log
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17954?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17954:
-------------------------------------
Summary: Logs: openshift puts info logs when authenticating in error log (was: openshift puts info logs when authenticating in error log)
> Logs: openshift puts info logs when authenticating in error log
> ---------------------------------------------------------------
>
> Key: JBIDE-17954
> URL: https://issues.jboss.org/browse/JBIDE-17954
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.0.CR1
>
>
> when logging in I get "User <myuser> was authenticated" in the error log as info messages.
> This should not happen by default. Please remove or add only when debug/trace is enabled.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17656) Forge crashed Eclipse
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17656?page=com.atlassian.jira.plugi... ]
Vineet Reynolds commented on JBIDE-17656:
-----------------------------------------
[~gastaldi], I've tried using that patch, but the class is not loaded for some reason - I think Furnace's modular classloading does not like the class referencing the {{sun.misc.Cleaner}}, resulting in a NCDFE.
Also, if it is used, I'd like to know if the license for the patch class is compatible - apparently it is [CC-BY-SA|http://meta.stackexchange.com/a/54767].
> Forge crashed Eclipse
> ---------------------
>
> Key: JBIDE-17656
> URL: https://issues.jboss.org/browse/JBIDE-17656
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta3
> Environment: Windows 7 64bits, JDK 8.0.0, JBDS 8.0.0.Beta2
> Reporter: Fred Bricon
> Assignee: Vineet Reynolds
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: generate.fsh, hs_err_pid4536.log, hs_err_pid5320.log, hs_err_pid640.log, JVM-GCactivity-heap.png, JVM-GCactivity-Linux.png, JVM-GCactivity.png
>
>
> I tried to reproduce the steps from JBIDE-17655 a 2nd time, Eclipse crashed while forge was scaffolding
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17977) Server adapter: "configure markers" missing in server adapter context menu
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17977?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17977:
-------------------------------------
Affects: Documentation (Ref Guide, User Guide, etc.),Interactive Demo/Tutorial
> Server adapter: "configure markers" missing in server adapter context menu
> --------------------------------------------------------------------------
>
> Key: JBIDE-17977
> URL: https://issues.jboss.org/browse/JBIDE-17977
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Labels: new_and_noteworthy, server_adapter
> Fix For: 4.2.0.CR1
>
> Attachments: server-adapter-configure-markers.png
>
>
> configure markers available from the project context menu should also be accessible from server context menu.
> seem to have been missed when we aligned the context markers.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17984) Application wizard: dont commit nor push changes back to OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17984?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17984:
-------------------------------------
Affects: Documentation (Ref Guide, User Guide, etc.),Interactive Demo/Tutorial,Compatibility/Configuration,User Experience
> Application wizard: dont commit nor push changes back to OpenShift
> ------------------------------------------------------------------
>
> Key: JBIDE-17984
> URL: https://issues.jboss.org/browse/JBIDE-17984
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: new_and_noteworthy
> Fix For: 4.2.0.CR1
>
>
> In JBIDE-10541 we added a "Publish Changes" dialog that shows the dirty changes for the local project, allows users to provide a commit msg and to commit/publish changes to OpenShift.
> In JBIDE-17190 we switched from automatic commit to explicit commit via this dialog when import new/existing OpenShift application. The "Publish Changes" dialog popping up after the OpenShift application was imported (application wizard) proved to be unexpected, disturbing in UX tests.
> We could get back to automatic commit but this is very much opaque for the user (discussed it in length with [~maxandersen]). We therefore decided to fully drop any commit and push when doing the initial import. We just process our changes and keep the imported project dirty. The user can then push the changes back to OpenShift via the server adapter.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17984) Application wizard: dont commit nor push changes back to OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17984?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17984:
-------------------------------------
Labels: new_and_noteworthy (was: )
> Application wizard: dont commit nor push changes back to OpenShift
> ------------------------------------------------------------------
>
> Key: JBIDE-17984
> URL: https://issues.jboss.org/browse/JBIDE-17984
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: new_and_noteworthy
> Fix For: 4.2.0.CR1
>
>
> In JBIDE-10541 we added a "Publish Changes" dialog that shows the dirty changes for the local project, allows users to provide a commit msg and to commit/publish changes to OpenShift.
> In JBIDE-17190 we switched from automatic commit to explicit commit via this dialog when import new/existing OpenShift application. The "Publish Changes" dialog popping up after the OpenShift application was imported (application wizard) proved to be unexpected, disturbing in UX tests.
> We could get back to automatic commit but this is very much opaque for the user (discussed it in length with [~maxandersen]). We therefore decided to fully drop any commit and push when doing the initial import. We just process our changes and keep the imported project dirty. The user can then push the changes back to OpenShift via the server adapter.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18045) Application wizard: Cannot open links in details of quickstarts on OpenShift Enterprise instance
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18045?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18045:
-------------------------------------
Affects: Documentation (Ref Guide, User Guide, etc.),Interactive Demo/Tutorial
> Application wizard: Cannot open links in details of quickstarts on OpenShift Enterprise instance
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18045
> URL: https://issues.jboss.org/browse/JBIDE-18045
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Minor
> Labels: application_wizard
> Fix For: 4.2.0.CR1
>
>
> Quickstarts in New application wizard contains Details area, where is the link to page containing more information about quickstart. After clicking on this link nothing happens.
> I have found out that problem is in URLs
> {code:title=.log}
> !ENTRY org.jboss.tools.openshift.express.ui 4 0 2014-08-08 06:53:10.435
> !MESSAGE Could not display malformed url "null".
> !STACK 0
> java.net.MalformedURLException
> at java.net.URL.<init>(URL.java:620)
> 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.express.internal.ui.wizard.application.ApplicationTemplateDetailViews$QuickstartView$1.widgetSelected(ApplicationTemplateDetailViews.java:342)
> 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:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1526)
> at org.eclipse.swt.widgets.Link.gtk_button_release_event(Link.java:380)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2078)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5510)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4700)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9074)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2473)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3439)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
> at org.eclipse.jface.window.Window.open(Window.java:808)
> at org.jboss.tools.openshift.express.internal.ui.utils.WizardUtils.openWizard(WizardUtils.java:69)
> at org.jboss.tools.openshift.express.internal.ui.utils.WizardUtils.openWizard(WizardUtils.java:60)
> at org.jboss.tools.openshift.express.internal.ui.command.NewApplicationHandler.open(NewApplicationHandler.java:55)
> at org.jboss.tools.openshift.express.internal.ui.command.NewApplicationHandler.execute(NewApplicationHandler.java:43)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294)
> 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:483)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:825)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:701)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$6(HandledContributionItem.java:685)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:613)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> 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:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> 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:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> Caused by: java.lang.NullPointerException
> at java.net.URL.<init>(URL.java:525)
> ... 72 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18175) enabling earlyaccess on a freshly opened central does not make it visible in header
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18175?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18175:
----------------------------------------
This is actually a small layout issue: when adding suffixes to the title, the size changes, and parent widget should be repacked to show the change.
Currently, parent widget keeps all children with the same size, so that the suffix part of the title isn't show until there is a need for repack.
[~maxandersen] Locally, just changing the size of the Central editor a little shows the suffix. Does it work for you as well? (this would validate my theory)
> enabling earlyaccess on a freshly opened central does not make it visible in header
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-18175
> URL: https://issues.jboss.org/browse/JBIDE-18175
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
>
> open central
> enable early access
> assert: early access shown in banner
> The last step fails. nothing is shown.
> Closing central and opening it again with early access enabled it starts showing up and reacting to changing the button.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months