[JBoss JIRA] (JBDS-4442) Central page does not work on Fedora 26 if package webkitgtk3 is not installed
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBDS-4442?page=com.atlassian.jira.plugin.... ]
Josef Kopriva commented on JBDS-4442:
-------------------------------------
[~mmalina] I am not sure about F25, I have noticed this after clean installation of F26.
> Central page does not work on Fedora 26 if package webkitgtk3 is not installed
> ------------------------------------------------------------------------------
>
> Key: JBDS-4442
> URL: https://issues.jboss.org/browse/JBDS-4442
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 11.0.0.AM1
> Environment: Fedora 26 Alpha
> Red Hat JBoss Developer Studio
> Version: 11.0.0.AM1
> Build id: AM1-v20170606-1759-B247
> Build date: 20170606-1759
> Reporter: Josef Kopriva
> Assignee: Supriya Bharadwaj
> Fix For: 11.x
>
>
> After fresh installation of F26 and Devstudio central shows error message
> {code:java}
> org.eclipse.swt.SWTException: An exception was raised in JavaScript
> at org.eclipse.swt.browser.WebKit$Webkit2JavascriptEvaluator.evaluate(WebKit.java:1273)
> at org.eclipse.swt.browser.WebKit.evaluate(WebKit.java:1324)
> at org.eclipse.swt.browser.WebBrowser.evaluate(WebBrowser.java:409)
> at org.eclipse.swt.browser.Browser.evaluate(Browser.java:663)
> at org.eclipse.swt.browser.Browser.evaluate(Browser.java:610)
> at org.jboss.tools.central.internal.browser.VersionedBrowser.<init>(VersionedBrowser.java:51)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.createBrowserSection(GettingStartedHtmlPage.java:188)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.createFormContent(GettingStartedHtmlPage.java:175)
> at org.eclipse.ui.forms.editor.FormPage.lambda$0(FormPage.java:163)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:163)
> at org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:480)
> at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1077)
> at org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:614)
> at org.eclipse.ui.forms.editor.SharedHeaderFormEditor.createPages(SharedHeaderFormEditor.java:106)
> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:348)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:151)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:99)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:355)
> 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:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:990)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:955)
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:124)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:399)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:318)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:105)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:74)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:56)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:666)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:772)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:743)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:737)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:721)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$1.handleEvent(PartServiceImpl.java:104)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:144)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:5434)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:212)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:201)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:52)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:173)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:620)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:584)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:768)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:401)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1187)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3261)
> at org.eclipse.ui.internal.WorkbenchPage.access$25(WorkbenchPage.java:3176)
> at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:3158)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3153)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3117)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3098)
> at org.jboss.tools.central.JBossCentralActivator.openJBossCentralEditor(JBossCentralActivator.java:437)
> at org.jboss.tools.central.JBossCentralActivator.getJBossCentralEditor(JBossCentralActivator.java:425)
> at org.jboss.tools.central.ShowJBossCentral$2.run(ShowJBossCentral.java:110)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4492)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4105)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> 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:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> 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:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24796) Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24796?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24796:
-------------------------------------
It took me a long time to figure out what you all meant here. I finally realized that the bug you are mentioning is that if you open the server editor, change the minishift_home, save it, close editor, re-open it, then it still shows the old value. And if you modify, save, and open the launch config, the env variable isn't overridden with the new value.
I have a patch to fix that over at https://github.com/jbosstools/jbosstools-openshift/pull/1537
It's kinda bundled in with another fix. Please test it and let me know if this fixes your issue or if I've misunderstood it.
> Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24796
> URL: https://issues.jboss.org/browse/JBIDE-24796
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.Final
> Environment: Fedora
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Critical
> Attachments: cdk3_sa-manual_correct-mhome.png, cdk3_sa-manual_wrong-mhome2.png
>
>
> In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See
> !cdk3_sa-manual_wrong-mhome2.png|thumbnail!
> In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses, if it is possible (from the side of binary) - but that seems not to be an option here as minishift/cdk stored everything in config that resides in MINISHIFT_HOME or ~/.minishift folder. See
> !cdk3_sa-manual_correct-mhome.png|thumbnail!
> Cc: [~adietish] [~rob.stryker].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24795) Add Minishift Home field to New server dialog for cdk 3
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24795?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24795:
-------------------------------------
> It would be desirable to have this field present in the New Server dialog.
I disagree with this statement. Widgets in the wizard are restricted to basically things that we require or that we expect a large number of people will be changing. This is to make sure we don't overload users just trying to get set up with too many options.
Niche cases (such as changing minishift-home) are not important enough to be a front-facing control in the new server wizard. If this logic was followed for the EAP or AS app servers, we'd have to include multiple wizard pages full of port settings, restart behavior, timeouts, credentials, etc etc etc. The simple fact that someone MAY change it is not enough to shove it in their face during the new server wizard.
> Add Minishift Home field to New server dialog for cdk 3
> -------------------------------------------------------
>
> Key: JBIDE-24795
> URL: https://issues.jboss.org/browse/JBIDE-24795
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.5.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> Somewhat related to JBIDE-24447 which is about allowing different minishift home set via MINISHIFT_HOME.
> When you create your cdk runtime manually, you should have a way of setting a custom Minishift home. Currently the dialog only contains the Minishift Binary field.
> So if you're using a directory other than ~/.minishift, you will have to create the cdk server first and then change this in the server editor. It would be desirable to have this field present in the New Server dialog.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24795) Add Minishift Home field to New server dialog for cdk 3
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24795?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-24795:
-----------------------------------
Assignee: Rob Stryker
> Add Minishift Home field to New server dialog for cdk 3
> -------------------------------------------------------
>
> Key: JBIDE-24795
> URL: https://issues.jboss.org/browse/JBIDE-24795
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.5.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> Somewhat related to JBIDE-24447 which is about allowing different minishift home set via MINISHIFT_HOME.
> When you create your cdk runtime manually, you should have a way of setting a custom Minishift home. Currently the dialog only contains the Minishift Binary field.
> So if you're using a directory other than ~/.minishift, you will have to create the cdk server first and then change this in the server editor. It would be desirable to have this field present in the New Server dialog.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24796) Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24796?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-24796:
-----------------------------------
Assignee: Rob Stryker
> Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24796
> URL: https://issues.jboss.org/browse/JBIDE-24796
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.Final
> Environment: Fedora
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Critical
> Attachments: cdk3_sa-manual_correct-mhome.png, cdk3_sa-manual_wrong-mhome2.png
>
>
> In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See
> !cdk3_sa-manual_wrong-mhome2.png|thumbnail!
> In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses, if it is possible (from the side of binary) - but that seems not to be an option here as minishift/cdk stored everything in config that resides in MINISHIFT_HOME or ~/.minishift folder. See
> !cdk3_sa-manual_correct-mhome.png|thumbnail!
> Cc: [~adietish] [~rob.stryker].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24447) Look for minishift configuration in MINISHIFT_HOME
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24447?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24447:
-------------------------------------
> What is important here is the thing that it is my old CDK 2.x folder with cdk.zip file unzipped and other stuff like vagrant box file, etc... (ls -all gives me no 'cdk' file that would contains runtime detection information which would clarify why it is was detected).
CDK 2 is automatically detected by checking the running eclipse's configuration location and going to the relative path Platform.getOS().equals(Platform.OS_MACOSX) ? "../../../" : "") + "../../../cdk/"; This is typically where the installer would install the older runtimes. It then scans that folder for stuff.
This sounds like it's working as expected?
> But, If I delete that adapter that was magically added via Runtime Detection on fresh start and restart the IDE, I got:
In the first start, we attempt to create runtimes directly, oftentimes using data from the installer. We try our best to do this to the best of our ability without involving user input on their first start. It's assumed that the installer will set variables or points in data files we check. However, after the first start is over, runtime detection will still try to 'detect' runtimes in the various "runtime path" locations, but won't assume nearly as much. They'll no longer check some of the installer configuration files, and will do a pure detection based only on the folder for the runtime path.
This also sounds like it is working as expected?
> The Adapter is called "Container Development Environment 3", which does not happen when you create server adapter manually via New Server. It should be called the same, right?
This sounds like a legitimate bug.
> I found out that in cdk server adapter's launch configuration, under environment tab, there is defined MINISHIFT_HOME env. var. It points to ~/Programs/cdk. But, devstudio is run from shell where MINISHIFT_HOME is set to ~/minishift_home. Very strange.
Once a server adapter is created, we *will not* go modifying it based on whatever shell the user is launching it from. The user may have made several custom changes to it already, and we won't go putting our finger in the stuff they already set, or that we set to defaults. This would lead to inconsistant behavior based on where the user launches his workspace from. So once the server is created, THOSE are the values, and they won't be changed unless the user changes them.
This sounds like when it was launched via the installer, the MINISHIFT_HOME environment variable was set when launching eclipse. Subsequent reloads of the devenv are being run from a shell directly?
This, again, sounds like it's behaving as expected. The installer sets an environment variable (minishift_home) when launching, OR sets a property in some of the files that we asked installer to set for us. We create a server using those values, and we don't change it later if a user decides to relaunch from a different shell, or, if the shell they're launching from (on first start) has a different minishift_home than the installer files we check.
> Look for minishift configuration in MINISHIFT_HOME
> --------------------------------------------------
>
> Key: JBIDE-24447
> URL: https://issues.jboss.org/browse/JBIDE-24447
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: runtime-detection
> Affects Versions: 4.4.4.Final
> Reporter: Jan Richter
> Assignee: Rob Stryker
> Fix For: 4.5.0.Final
>
> Attachments: cdk2_x_RD.png, cdk3_minishift_home.png
>
>
> One can use the MINISHIFT_HOME variable to save minishift configuration somewhere else than in ~/.minishift
> It would be nice if runtime detection looked there if the variable is configured.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4444) [DevSuite Installer] Move Account step after Confirmation step
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4444?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-4444:
-------------------------------------
After discussion on mail list we are going to release with minimal text:
!account-final-2.png!
> [DevSuite Installer] Move Account step after Confirmation step
> --------------------------------------------------------------
>
> Key: JBDS-4444
> URL: https://issues.jboss.org/browse/JBDS-4444
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 11.0.0.AM1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: New_and_noteworthy, ui
> Fix For: 11.0.0.GA
>
> Attachments: RHDS_Installer_RHDAccountLoginScreen_Aug6-2017.jpg, about-background.png, about-update1.png, devsuite-installer-1.4.0-workflow.png, devsuite-installer-2.0.0-workflow.png, install-step-3-1.png, install-step-3-2.png, install-step-4.png, install-step-5-1.png, install-step-5-2.png, install-step-6-1.png, install-step-6.png, install-step1.png, install-step2.png
>
>
> As a user I would like to avoid entering login/password on a first page of installer, so I can explore and see what can be installed and then provide my credentials if I decided to proceed with installation.
> Current workflow is
> !devsuite-installer-1.4.0-workflow.png|thumbnail!
> should be transformed to
> !devsuite-installer-2.0.0-workflow.png|thumbnail!
> This would require to change starting page to show only generic information about DevSuite Installer and whole first page 'Account' should appear after confirmation page in case any of Red Hat Products is selected for installation.
> Here are screenshots for how it could look like for scenario when Red Hat Product Selected:
> !install-step1.png|thumbnail! !install-step2.png|thumbnail! !install-step-3-1.png|thumbnail! !install-step-4.png|thumbnail! !install-step-5-2.png|thumbnail! !install-step-6-1.png|thumbnail!
> and when community or 3rd party components only selected:
> !install-step1.png|thumbnail! !install-step2.png|thumbnail! !install-step-3-2.png|thumbnail! !install-step-5-1.png|thumbnail! !install-step-6.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4444) [DevSuite Installer] Move Account step after Confirmation step
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4444?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4444:
--------------------------------
Attachment: account-final-2.png
> [DevSuite Installer] Move Account step after Confirmation step
> --------------------------------------------------------------
>
> Key: JBDS-4444
> URL: https://issues.jboss.org/browse/JBDS-4444
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 11.0.0.AM1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: New_and_noteworthy, ui
> Fix For: 11.0.0.GA
>
> Attachments: RHDS_Installer_RHDAccountLoginScreen_Aug6-2017.jpg, about-background.png, about-update1.png, account-final-2.png, devsuite-installer-1.4.0-workflow.png, devsuite-installer-2.0.0-workflow.png, install-step-3-1.png, install-step-3-2.png, install-step-4.png, install-step-5-1.png, install-step-5-2.png, install-step-6-1.png, install-step-6.png, install-step1.png, install-step2.png
>
>
> As a user I would like to avoid entering login/password on a first page of installer, so I can explore and see what can be installed and then provide my credentials if I decided to proceed with installation.
> Current workflow is
> !devsuite-installer-1.4.0-workflow.png|thumbnail!
> should be transformed to
> !devsuite-installer-2.0.0-workflow.png|thumbnail!
> This would require to change starting page to show only generic information about DevSuite Installer and whole first page 'Account' should appear after confirmation page in case any of Red Hat Products is selected for installation.
> Here are screenshots for how it could look like for scenario when Red Hat Product Selected:
> !install-step1.png|thumbnail! !install-step2.png|thumbnail! !install-step-3-1.png|thumbnail! !install-step-4.png|thumbnail! !install-step-5-2.png|thumbnail! !install-step-6-1.png|thumbnail!
> and when community or 3rd party components only selected:
> !install-step1.png|thumbnail! !install-step2.png|thumbnail! !install-step-3-2.png|thumbnail! !install-step-5-1.png|thumbnail! !install-step-6.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24728) Server New and Noteworthy for 4.5.0.Final
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24728?page=com.atlassian.jira.plugi... ]
Rob Stryker closed JBIDE-24728.
-------------------------------
Resolution: Rejected
Nothing in server sadly
> Server New and Noteworthy for 4.5.0.Final
> -----------------------------------------------------
>
> Key: JBIDE-24728
> URL: https://issues.jboss.org/browse/JBIDE-24728
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: archives, jmx, server
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.5.0.Final
>
>
> Rob Stryker,
> Search for your component's New and Noteworthy issues:
> Queries:
> * [Completed Server JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...]
> * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...]
> If no N&N issues are found for Server, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
> Document the ones relevant for Server by submitting a pull request against:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> If your PR's commit comment is of the form... {code}JBIDE-24706 #comment Create N&N for Server 4.5.0.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied.
> If there is nothing new or noteworthy for Server for this milestone, please *reject* and *close* this issue.
> ----
> If there is nothing new or noteworthy for 4.5.0.Final since the AM3 release of Server, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents.
> If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.5.0.Final.adoc file here:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc.
> However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.5.0.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months