[JBoss JIRA] (JBDS-3838) Cannot install CDK. Installer prompts to setup VAGRANT_HOME if there is space in path and then it ignores it and fails
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-3838?page=com.atlassian.jira.plugin.... ]
Pavol Srna commented on JBDS-3838:
----------------------------------
To clarify why is this a blocker. For the majority of windows users their user home contains a space, because it is a default when you choose first name and last name during windows installation. The vagrant default path is userhome ...something. There is a workaround where you set the VAGRANT_HOME property, but this does not work for me - the installer ignores it. I have not been successful to complete the standard installation.
> Cannot install CDK. Installer prompts to setup VAGRANT_HOME if there is space in path and then it ignores it and fails
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3838
> URL: https://issues.jboss.org/browse/JBDS-3838
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Pavol Srna
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.GA
>
> Attachments: install.log, vagrant.log, vbox.log
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-22151) Failed to install JBT in Eclipse
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22151?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22151:
-------------------------------------
openshift tooling defines a *minimal* version of jetty 9.2.13 https://github.com/jbosstools/jbosstools-openshift/search?utf8=%E2%9C%93&...
So given it's an open ended constraint, why would it fail? Is p2 drunk?
I'm fine bumping the constraint to 9.3, but my understanding is it shouldn't be necessary.
> Failed to install JBT in Eclipse
> --------------------------------
>
> Key: JBIDE-22151
> URL: https://issues.jboss.org/browse/JBIDE-22151
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, openshift
> Affects Versions: 4.4.0.Alpha1
> Environment: Operating System: have tried Fedora 17 and 22
> jbt version: 3.2.0.Alpha1-v20160409-1043-B1241
> eclipse:
> Version: Neon Milestone 6 (4.6.0M6)
> Build id: 20160329-0659
> Reporter: Chunyun Chen
> Assignee: Fred Bricon
> Fix For: 4.4.0.Alpha1
>
> Attachments: jbt_installation_1.png, jbt_installation_2.png
>
>
> Will meet below dependency errors when installing jbt in eclipse:
> "
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.feature.feature.group 3.2.0.Alpha1-v20160409-1043-B1241)
> Missing requirement: Openshift 3 Client 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.client 3.2.0.Alpha1-v20160409-1043-B1241) requires 'bundle org.eclipse.jetty.websocket.client 9.2.13' but it could not be found
> Cannot satisfy dependency:
> From: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.feature.feature.group 3.2.0.Alpha1-v20160409-1043-B1241)
> To: org.jboss.tools.openshift.client [3.2.0.Alpha1-v20160409-1043-B1241]
> "
--
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 Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3806?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-3806:
-----------------------------------
I don't think this should be a blocker. Plus it looks like I'm the only one seeing it, so I'd just let it slip.
> 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
[JBoss JIRA] (JBIDE-22191) Support list of application creation with JSON
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22191?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-22191:
---------------------------------------
What we should be doing is checking to see if the supplied file is a template and advise the use accordingly. I have not tried, but I suspect the CLI would not have any way of properly handling a list of templates, even if that is allowed. The only think it MIGHT do is instantiate them all.
> Support list of application creation with JSON
> ----------------------------------------------
>
> Key: JBIDE-22191
> URL: https://issues.jboss.org/browse/JBIDE-22191
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Aurélien Pupier
> Fix For: 4.4.x
>
> Attachments: screenshot-1.png
>
>
> Currently, if we provide a Local template, which is a list of templates, there is a popup with an error.
> {noformat}
> java.lang.ClassCastException: com.openshift.internal.restclient.model.List cannot be cast to com.openshift.restclient.model.template.ITemplate
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.getLocalTemplate(NewApplicationWizardModel.java:107)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.updateSelectedTemplate(NewApplicationWizardModel.java:86)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.update(NewApplicationWizardModel.java:78)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.setLocalTemplateFileName(NewApplicationWizardModel.java:315)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateListPage.setLocalTemplate(TemplateListPage.java:511)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateListPage.access$6(TemplateListPage.java:506)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateListPage$14.widgetSelected(TemplateListPage.java:696)
> 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:4362)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4180)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3769)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:279)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270)
> at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34)
> 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(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> {noformat}
> You can use the template used by Fuse to reproduce: https://raw.githubusercontent.com/jboss-fuse/application-templates/master...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-21652) We should make OS 3 application status more visible for users
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21652?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21652:
--------------------------------
Fix Version/s: 4.4.x
(was: 4.4.0.Alpha1)
> We should make OS 3 application status more visible for users
> -------------------------------------------------------------
>
> Key: JBIDE-21652
> URL: https://issues.jboss.org/browse/JBIDE-21652
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Alexey Kazakov
> Fix For: 4.4.x
>
>
> Currently it can be confusing for users when an application is not available because it's building.
> We should think about our options, how we could improve visibility of the application status in both OS Explorer and Servers view (for OS server adapters).
> For example we could add a status line for an "application" node (or even for a project?) and show "Building..." or something if any of its services is building. We also could use a red font for such statuses. An gif icon would be ideal but I'm not sure it's technically possible.
> OS Server adapter is a separate story but we need to add status for it too. Maybe it's worth a separate issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-21081) Application wizard: canceling the 'Create Application From Template Job' leaves created resources in place
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21081?page=com.atlassian.jira.plugi... ]
Fred Bricon closed JBIDE-21081.
-------------------------------
Fix Version/s: (was: 4.4.0.Alpha1)
Resolution: Duplicate Issue
Closing as duplicate of JBIDE-21462
> Application wizard: canceling the 'Create Application From Template Job' leaves created resources in place
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21081
> URL: https://issues.jboss.org/browse/JBIDE-21081
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Jan Richter
> Labels: application_wizard, openshift_v3
>
> After clicking finish in the Application wizard, a progress bar with a button to cancel the operation appears. Once clicked, depending on the user's speed, it either does nothing at all, or it returns the user back to the Application wizard.
> However, the app always gets created on Openshift. So if the user is returned to the wizard, a dialog appears saying the app was created. In the end the user might end up with an open wizard with the same data that their newly created application has.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months