[JBoss JIRA] (JBIDE-21836) Preferences: openshift 3 oc location resets to a different/old value on restart
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21836?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21836:
--------------------------------
Fix Version/s: 4.4.x
(was: 4.4.0.Alpha1)
> Preferences: openshift 3 oc location resets to a different/old value on restart
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21836
> URL: https://issues.jboss.org/browse/JBIDE-21836
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Critical
> Labels: oc_binary, openshift_v3, preferences
> Fix For: 4.4.x
>
>
> on start of eclipse new workspace the value is for reason unknown to me set to:
> {code}
> /Users/max/Downloads/openshift-origin-v1.0.3-1695461-darwin-amd64/oc
> {code}
> which does exist, but is old version and publish fails.
> Then I set it to
> {code}
> /usr/local/bin/oc
> {code}
> now publish works.
> Restart eclipse - old value returns and publish starts failing again.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-20513) tricky to login to openshift when token expires
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20513?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20513:
--------------------------------
Fix Version/s: 4.4.x
(was: 4.4.0.Alpha1)
> tricky to login to openshift when token expires
> -----------------------------------------------
>
> Key: JBIDE-20513
> URL: https://issues.jboss.org/browse/JBIDE-20513
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.4.x
>
>
> I logged in with token.
> 24hrs later I start eclipse and expand the connection in explorer
> expecting to just login.
> Here is what happens instead:
> a) info message (not error) is logged to error log hiding the explorer view
> b) after some seconds (seems there is a timeout) a login dialog comes up saying I need to sign in (no clear info that auth failed or token missing etc.).
> cancel the dialog since I'm trying to figure out what happened.
> c) Now the explorer just shows "You must obtain API token by visiting ..." as child and I cannot see straightforward way to log in again.
> Turns out Refresh does trigger login again.
> meanwhile command line 'oc' seem to be fine at logging in with token older than 24 hrs...can't verify that though, but in any case:
> a) do a user really need to re-login every 24 hours ?
> b) the error handling/dialogs shown are not very informative
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-20513) tricky to login to openshift when token expires
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20513?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20513:
--------------------------------
Priority: Major (was: Critical)
> tricky to login to openshift when token expires
> -----------------------------------------------
>
> Key: JBIDE-20513
> URL: https://issues.jboss.org/browse/JBIDE-20513
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Fix For: 4.4.x
>
>
> I logged in with token.
> 24hrs later I start eclipse and expand the connection in explorer
> expecting to just login.
> Here is what happens instead:
> a) info message (not error) is logged to error log hiding the explorer view
> b) after some seconds (seems there is a timeout) a login dialog comes up saying I need to sign in (no clear info that auth failed or token missing etc.).
> cancel the dialog since I'm trying to figure out what happened.
> c) Now the explorer just shows "You must obtain API token by visiting ..." as child and I cannot see straightforward way to log in again.
> Turns out Refresh does trigger login again.
> meanwhile command line 'oc' seem to be fine at logging in with token older than 24 hrs...can't verify that though, but in any case:
> a) do a user really need to re-login every 24 hours ?
> b) the error handling/dialogs shown are not very informative
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-21727) add OpenShift server adapter to downloadable WTP server adapters
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21727?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21727:
--------------------------------
Fix Version/s: 4.4.x
(was: 4.4.0.Alpha1)
> add OpenShift server adapter to downloadable WTP server adapters
> ----------------------------------------------------------------
>
> Key: JBIDE-21727
> URL: https://issues.jboss.org/browse/JBIDE-21727
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.x
>
> Attachments: compositeArtifacts.xml, compositeContent.xml, mockup-change-1.png, mockup-change-2.png, openshiftv3-tools-server-adapter-manually-installed.png, openshiftv3-tools-server-adapter-no-license-found.png, openshiftv3-tools-server-adapter.png
>
>
> We have JBoss server adapters available in Eclise new Server wizard; would be great if we could put OpenShift in there too.
> Anything preventing us from doing so ?
> Is there a workflow from New server that helps users to create openshift connection etc. ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-22075) Confusing error message when trying to attach remote debugger to OS app run in debug mode
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22075:
--------------------------------
Fix Version/s: 4.4.x
(was: 4.4.0.Alpha1)
> Confusing error message when trying to attach remote debugger to OS app run in debug mode
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-22075
> URL: https://issues.jboss.org/browse/JBIDE-22075
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.x
>
> Attachments: error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, remote-debugger-already-launched.png
>
>
> If you restart the server adapter in debug mode ("Restart in Debug" in the context menu to your server adapter) the remote debugger is launched automatically.
> If you're not aware of this and try to launch the remote debugger entry (that was created automatically), you will face an error telling you that it cannot connect (since there's already an instance sitting on the ports). It's not obvious to the dummy user, we should improve this error-message
> When I am trying to run remote debugging of an application on OpenShift I get following error
> !!error-in-launching-remote-debugger.png! !
> {code}
> Failed to connect to remote VM
> com.sun.jdi.connect.spi.ClosedConnectionException
> at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222)
> at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214)
> at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> *Steps to reproduce:*
> ASSERT: Have an OpenShift 3 application based on eap 6 template with server adapter and project in workspace.
> EXEC: Select "Restart in Debug" in context menu of server adapter.
> ASSERT: Server adapter is in state debugging ("[Debugging, Started]").
> EXEC: Click on Debug Remote debugger to 'server adapter name' workbench tool item to start debugging.
> RESULT: Error is shown.
> EXPECTED RESULT: The error message should tell you that there already is an instance running.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-22189) Unhandled event loop exception when selecting builder image in properties view.
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22189?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22189:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
> Unhandled event loop exception when selecting builder image in properties view.
> -------------------------------------------------------------------------------
>
> Key: JBIDE-22189
> URL: https://issues.jboss.org/browse/JBIDE-22189
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Environment: JBDS 9.1.0.CR1c
> Reporter: Radim Hopp
> Fix For: 4.4.0.Alpha1
>
>
> Showing "Builds" in properties view and then selecting "Builder Image", Unhandled event loop exception is thrown:
> {noformat:title=Unhandled event loop exception}
> org.eclipse.core.runtime.AssertionFailedException: assertion failed:
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
> at org.eclipse.jface.viewers.TextCellEditor.doSetValue(TextCellEditor.java:231)
> at org.eclipse.jface.viewers.CellEditor.setValue(CellEditor.java:861)
> at org.eclipse.ui.views.properties.PropertySheetEntry.getEditor(PropertySheetEntry.java:375)
> at org.eclipse.ui.views.properties.PropertySheetViewer.activateCellEditor(PropertySheetViewer.java:166)
> at org.eclipse.ui.views.properties.PropertySheetViewer.handleSelect(PropertySheetViewer.java:738)
> at org.eclipse.ui.views.properties.PropertySheetViewer.access$8(PropertySheetViewer.java:718)
> at org.eclipse.ui.views.properties.PropertySheetViewer$5.widgetDefaultSelected(PropertySheetViewer.java:813)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:119)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> 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:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {noformat}
> I have tried it with eap64-basic-s2i and eap64-mysql-persistent-s2i templates.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-22188) Creating an Openshift3 server adapter on Windows causes rsync failures
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22188?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22188:
--------------------------------
Fix Version/s: 4.4.x
> Creating an Openshift3 server adapter on Windows causes rsync failures
> ----------------------------------------------------------------------
>
> Key: JBIDE-22188
> URL: https://issues.jboss.org/browse/JBIDE-22188
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jeff MAURY
> Labels: openshift_v3
> Fix For: 4.4.x
>
>
> I am on a W10 machine with the cwrsync (https://www.itefix.net/cwrsync) rsync client.
> When I create the server adapter, I always got rync error with the message:
> {code}
> rsync: failed to modify permissions on "/cygdrive/c/work/runtime-JBossTools/.metadata/.plugins/org.jboss.ide.eclipse.as.core/eap-app_at_OpenShift_3_(10.2.2.2)/deploy/ROOT.war": Permission denied (13)
> rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1650) [generator=3.1.2]
> error: exit status 23
> {code}
> Full stack trace:
> {code}
> org.eclipse.equinox.launcher.Main at localhost:55022 (Suspended)
> Daemon System Thread [Attach Listener] (Suspended)
> Daemon System Thread [Signal Dispatcher] (Suspended)
> Daemon System Thread [Finalizer] (Suspended)
> waiting for: ReferenceQueue$Lock (id=661)
> Object.wait(long) line: not available [native method]
> ReferenceQueue.remove(long) line: 143
> ReferenceQueue.remove() line: 164
> Finalizer$FinalizerThread.run() line: 209
> Daemon System Thread [Reference Handler] (Suspended)
> waiting for: Reference$Lock (id=662)
> Object.wait(long) line: not available [native method]
> Reference$Lock(Object).wait() line: 502
> Reference.tryHandlePending(boolean) line: 191
> Reference$ReferenceHandler.run() line: 153
> Thread [main] (Suspended)
> OS.WaitMessage() line: not available
> Display.sleep() line: 4739
> IDEWorkbenchAdvisor(WorkbenchAdvisor).eventLoopIdle(Display) line: 368
> IDEWorkbenchAdvisor.eventLoopIdle(Display) line: 864
> Workbench$3.eventLoopIdle(Display) line: 520
> PartRenderingEngine$4.run() line: 1123
> Realm.runWithDefault(Realm, Runnable) line: 336
> PartRenderingEngine.run(MApplicationElement, IEclipseContext) line: 1019
> E4Workbench.createAndRunUI(MApplicationElement) line: 157
> Workbench$5.run() line: 691
> Realm.runWithDefault(Realm, Runnable) line: 336
> Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 604
> PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 150
> IDEApplication.start(IApplicationContext) line: 138
> EclipseAppHandle.run(Object) line: 196
> EclipseAppLauncher.runApplication(Object) line: 134
> EclipseAppLauncher.start(Object) line: 104
> EclipseStarter.run(Object) line: 388
> EclipseStarter.run(String[], Runnable) line: 243
> NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
> NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62
> DelegatingMethodAccessorImpl.__invoke(Object, Object[]) line: 43
> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: not available
> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: not available
> Method.invoke(Object, Object...) line: 498
> Main.invokeFramework(String[], URL[]) line: 670
> Main.basicRun(String[]) line: 609
> Main.run(String[]) line: 1516
> Main.main(String[]) line: 1489
> Daemon Thread [GroupPoller] (Suspended)
> waiting for: TaskQueue (id=653)
> Object.wait(long) line: not available [native method]
> TimerThread.mainLoop() line: 552
> TimerThread.run() line: 505
> Thread [Active Thread: Equinox Container: c0c5ea0f-4705-0016-1225-a081794d26c1] (Suspended)
> Unsafe.park(boolean, long) line: not available [native method]
> LockSupport.parkNanos(Object, long) line: 215
> AbstractQueuedSynchronizer$ConditionObject.awaitNanos(long) line: 2078
> ScheduledThreadPoolExecutor$DelayedWorkQueue.take() line: 1093
> ScheduledThreadPoolExecutor$DelayedWorkQueue.take() line: 809
> ScheduledThreadPoolExecutor(ThreadPoolExecutor).getTask() line: 1067
> ScheduledThreadPoolExecutor(ThreadPoolExecutor).runWorker(ThreadPoolExecutor$Worker) line: 1127
> ThreadPoolExecutor$Worker.run() line: 617
> Thread.run() line: 745
> Daemon Thread [Framework Event Dispatcher: org.eclipse.osgi.internal.framework.EquinoxEventPublisher@76b642aa] (Suspended)
> waiting for: EventManager$EventThread (id=399)
> Object.wait(long) line: not available [native method]
> EventManager$EventThread(Object).wait() line: 502
> EventManager$EventThread.getNextEvent() line: 400
> EventManager$EventThread.run() line: 336
> Daemon Thread [Start Level: Equinox Container: c0c5ea0f-4705-0016-1225-a081794d26c1] (Suspended)
> waiting for: EventManager$EventThread (id=401)
> Object.wait(long) line: not available [native method]
> EventManager$EventThread(Object).wait() line: 502
> EventManager$EventThread.getNextEvent() line: 400
> EventManager$EventThread.run() line: 336
> Daemon Thread [[Timer] - Main Queue Handler] (Suspended)
> waiting for: Object (id=660)
> Object.wait(long) line: not available [native method]
> TimerImpl.run() line: 141
> Thread.run() line: 745
> Daemon Thread [Bundle File Closer] (Suspended)
> waiting for: EventManager$EventThread (id=406)
> Object.wait(long) line: not available [native method]
> EventManager$EventThread(Object).wait() line: 502
> EventManager$EventThread.getNextEvent() line: 400
> EventManager$EventThread.run() line: 336
> Thread [Worker-JM] (Suspended)
> waiting for: ArrayList (id=659)
> Object.wait(long) line: not available [native method]
> InternalWorker.run() line: 59
> Daemon Thread [JRebel plugin.xml scanner] (Suspended)
> Thread.sleep(long) line: not available [native method]
> PluginXmlScanner.run() line: 89
> Thread.run() line: 745
> Daemon Thread [EMF Reference Cleaner] (Suspended)
> waiting for: ReferenceQueue$Lock (id=657)
> Object.wait(long) line: not available [native method]
> ReferenceQueue.remove(long) line: 143
> ReferenceQueue.remove() line: 164
> CommonUtil$1ReferenceClearingQueuePollingThread.run() line: 70
> Daemon Thread [Java indexing] (Suspended)
> waiting for: IndexManager (id=654)
> Object.wait(long) line: not available [native method]
> IndexManager(Object).wait() line: 502
> IndexManager(JobManager).run() line: 371
> Thread.run() line: 745
> Daemon Thread [[ThreadPool Manager] - Idle Thread] (Suspended)
> waiting for: Executor (id=421)
> Object.wait(long) line: not available [native method]
> Executor(Object).wait() line: 502
> Executor.run() line: 106
> Thread [Worker-3] (Suspended)
> waiting for: Object (id=658)
> Object.wait(long) line: not available [native method]
> Object.wait() line: 502
> ThreadJob.waitForRun(ThreadJob, IProgressMonitor, InternalJob, Thread) line: 270
> ThreadJob.joinRun(ThreadJob, IProgressMonitor) line: 197
> ImplicitJobs.begin(ISchedulingRule, IProgressMonitor, boolean) line: 92
> JobManager.beginRule(ISchedulingRule, IProgressMonitor) line: 307
> StringPoolJob.run(IProgressMonitor) line: 98
> Worker.run() line: 55
> Daemon Thread [EventAdmin Async Event Dispatcher Thread] (Suspended)
> waiting for: EventManager$EventThread (id=436)
> Object.wait(long) line: not available [native method]
> EventManager$EventThread(Object).wait() line: 502
> EventManager$EventThread.getNextEvent() line: 400
> EventManager$EventThread.run() line: 336
> Daemon Thread [JavaScript indexing] (Suspended)
> waiting for: IndexManager (id=656)
> Object.wait(long) line: not available [native method]
> IndexManager(Object).wait() line: 502
> IndexManager(JobManager).run() line: 370
> Thread.run() line: 745
> Thread [Worker-4] (Suspended (breakpoint at line 73 in RSync$1))
> RSync$1.runOCBinary(MultiStatus) line: 73
> RSync$1(OCBinaryOperation).run(MultiStatus) line: 34
> RSync.syncPodsToDirectory(File, MultiStatus, IServerConsoleWriter) line: 78
> OpenShiftPublishController.publishStart(IProgressMonitor) line: 65
> OpenShiftServerBehaviour(CachedPublisherProfileBehavior).publishStart(IProgressMonitor) line: 47
> OpenShiftServerBehaviour(ServerBehaviourDelegate).publish(int, IProgressMonitor) line: 942
> OpenShiftServerBehaviour(ServerBehaviourDelegate).publish(int, List<IModule[]>, IProgressMonitor, IAdaptable) line: 774
> Server.publishImpl(int, List<IModule[]>, IAdaptable, IProgressMonitor) line: 3172
> Server$PublishJob.run(IProgressMonitor) line: 345
> Worker.run() line: 55
> Thread [Worker-8] (Suspended)
> waiting for: Object (id=658)
> Object.wait(long) line: not available [native method]
> Object.wait() line: 502
> ThreadJob.waitForRun(ThreadJob, IProgressMonitor, InternalJob, Thread) line: 270
> ThreadJob.joinRun(ThreadJob, IProgressMonitor) line: 197
> ImplicitJobs.begin(ISchedulingRule, IProgressMonitor, boolean) line: 92
> JobManager.beginRule(ISchedulingRule, IProgressMonitor) line: 307
> Server$PublishJob.run(IProgressMonitor) line: 344
> Worker.run() line: 55
> Daemon System Thread [Java2D Disposer] (Suspended)
> waiting for: ReferenceQueue$Lock (id=663)
> Object.wait(long) line: not available [native method]
> ReferenceQueue.remove(long) line: 143
> ReferenceQueue.remove() line: 164
> Disposer.run() line: 148
> Thread.run() line: 745
> Daemon System Thread [AWT-Windows] (Suspended)
> WToolkit.eventLoop() line: not available
> WToolkit.run() line: 306
> Thread.run() line: 745
> Thread [Worker-11] (Suspended)
> waiting for: WorkerPool (id=655)
> Object.wait(long) line: not available [native method]
> WorkerPool.sleep(long) line: 188
> WorkerPool.startJob(Worker) line: 220
> Worker.run() line: 52
> Thread [Worker-13] (Suspended)
> waiting for: WorkerPool (id=655)
> Object.wait(long) line: not available [native method]
> WorkerPool.sleep(long) line: 188
> WorkerPool.startJob(Worker) line: 220
> Worker.run() line: 52
> Thread [Worker-14] (Suspended)
> waiting for: WorkerPool (id=655)
> Object.wait(long) line: not available [native method]
> WorkerPool.sleep(long) line: 188
> WorkerPool.startJob(Worker) line: 220
> Worker.run() line: 52
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBDS-3806) Installer - reduce footer height to reveal more content
by Josephine Qian (JIRA)
[ https://issues.jboss.org/browse/JBDS-3806?page=com.atlassian.jira.plugin.... ]
Josephine Qian commented on JBDS-3806:
--------------------------------------
[~jowilson] I am not sure if I would call this a blocker, since the scroll bar is presented. I am also not a big fan of semi-transparent footer, even that is a little bit better than the current solution. Since we are so close to the release date, I am fine with leaving it as it is, unless other people think we have to address this.
what do you think [~jrichter1]
> Installer - reduce footer height to reveal more content
> -------------------------------------------------------
>
> Key: JBDS-3806
> URL: https://issues.jboss.org/browse/JBDS-3806
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.Beta2
> Reporter: Joshua Wilson
> Assignee: Joshua Wilson
> Priority: Blocker
> Labels: havoc, ui
> Attachments: confirm.png
>
>
> The footer on the confirm page would look better if it cut into the display of one of the components to be installed. Also, remove the transparency.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months