April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22191) Support list of applciation creation

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22191?page=com.atlassian.jira.plugi... ] Aurélien Pupier updated JBIDE-22191: ------------------------------------ Description: 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... was: Currently, if we provide a Local template, which is a list of templates, there is a popup with an error. You can use the template used by Fuse to reproduce: https://raw.githubusercontent.com/jboss-fuse/application-templates/master... > Support list of applciation creation > ------------------------------------ > > 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 > 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)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22190) Support "URL" templates to create a new application

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBIDE-22190: --------------------------------------- Summary: Support "URL" templates to create a new application Key: JBIDE-22190 URL: https://issues.jboss.org/browse/JBIDE-22190 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Reporter: Aurélien Pupier Currently, we can choose on the server template or to use a local template. it would be nice to be able to use an URL template too. My current use case: I want to create a Fuse Integration Service application based on a template which is available on github at https://raw.githubusercontent.com/jboss-fuse/application-templates/master... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-718) Getting Started / Readme for new CDK users

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-718?page=com.atlassian.jira.plug... ] Martin Malina commented on TOOLSDOC-718: ---------------------------------------- [~akazakov], step 3) from Rob didn't take the installer into consideration at all. The workflow was "create your own cdk server adapter". The password passing was from the tooling to the vagrant up command which is valid. I think the fact that the installer will create a cdk server adapter for you should be described in the installer getting started doc (but sure, it could be mentioned here also). > Getting Started / Readme for new CDK users > ------------------------------------------- > > Key: TOOLSDOC-718 > URL: https://issues.jboss.org/browse/TOOLSDOC-718 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 9.1 CR1 > Reporter: Nick Boldt > Assignee: Misha Ali > Labels: Havoc > Fix For: 9.1 GA > > > See JBDS-3738. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3726) Installer - Installer fails to overwrite/move an existing JDK

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3726?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3726. ----------------------------- Verified with B130. > Installer - Installer fails to overwrite/move an existing JDK > ------------------------------------------------------------- > > Key: JBDS-3726 > URL: https://issues.jboss.org/browse/JBDS-3726 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Windows 10 > Build: 0.0.2-20160324-14 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: Havoc > Fix For: 9.1.0.GA > > > Attempting to overwrite a JDK that was installed by a previous installer run fails with this (permissions) error: > Mon, 28 Mar 2016 18:39:41 GMT-INFO: jdk - Extract C:\Users\jbossqa\AppData\Local\Temp\7zS1C02.tmp\jdk.zip to c:\DeveloperPlatform SUCCESS > Mon, 28 Mar 2016 18:39:41 GMT-INFO: jdk - Rename c:\DeveloperPlatform\zulu8.13.0.5-jdk8.0.72-win_x64to c:\DeveloperPlatform\jdk8 > Mon, 28 Mar 2016 18:39:41 GMT-ERROR: jdk - Error: EPERM: operation not permitted, rename 'c:\DeveloperPlatform\zulu8.13.0.5-jdk8.0.72-win_x64' -> 'c:\DeveloperPlatform\jdk8' > Mon, 28 Mar 2016 18:39:41 GMT-ERROR: jdk failed to install: Error: EPERM: operation not permitted, rename 'c:\DeveloperPlatform\zulu8.13.0.5-jdk8.0.72-win_x64' -> 'c:\DeveloperPlatform\jdk8' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3836) Installation refused with no reason given

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-3836?page=com.atlassian.jira.plugin.... ] Pavol Srna updated JBDS-3836: ----------------------------- Description: Installer says that 1 component has been found that *meets* the requirement, but it prevents the installation. I don't see a real reason given why the installation is disabled. > Installation refused with no reason given > ----------------------------------------- > > Key: JBDS-3836 > URL: https://issues.jboss.org/browse/JBDS-3836 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Srna > Priority: Critical > Labels: havoc > Attachments: screen-installer.png > > > Installer says that 1 component has been found that *meets* the requirement, but it prevents the installation. I don't see a real reason given why the installation is disabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3836) Installation refused with no reason given

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-3836?page=com.atlassian.jira.plugin.... ] Pavol Srna updated JBDS-3836: ----------------------------- Attachment: screen-installer.png > Installation refused with no reason given > ----------------------------------------- > > Key: JBDS-3836 > URL: https://issues.jboss.org/browse/JBDS-3836 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Srna > Priority: Critical > Labels: havoc > Attachments: screen-installer.png > > > Installer says that 1 component has been found that *meets* the requirement, but it prevents the installation. I don't see a real reason given why the installation is disabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3836) Installation refused with no reason given

by Pavol Srna (JIRA)

Pavol Srna created JBDS-3836: -------------------------------- Summary: Installation refused with no reason given Key: JBDS-3836 URL: https://issues.jboss.org/browse/JBDS-3836 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 9.1.0.CR1 Reporter: Pavol Srna Priority: Critical -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3836) Installation refused with no reason given

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3836?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3836: ----------------------------- > Installation refused with no reason given > ----------------------------------------- > > Key: JBDS-3836 > URL: https://issues.jboss.org/browse/JBDS-3836 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Srna > Priority: Critical > Labels: havoc > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3795) Cant start CDK

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3795?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-3795. ------------------------------- I believe all is done here. And I just checked and the current all-in-one installer works perfectly for me - that contains JBDS 9.1.0.GA and CDK 2.0. > Cant start CDK > -------------- > > Key: JBDS-3795 > URL: https://issues.jboss.org/browse/JBDS-3795 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer > Affects Versions: 9.1.0.CR1 > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Blocker > Labels: havoc, respin-c > Fix For: 9.1.0.CR1 > > Attachments: screenshot-1.png > > > CDK server adapter is not started when using JBDS + CDK April 8th build even after updating vagrant-service-manager to 1.0.1. > "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments." > I can access the OS console: https://10.1.2.2:8443/console > The console output looks OK too: > {code} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'cdkv2'... > [KProgress: 10% > [KProgress: 20% > [KProgress: 90% > [K==> default: Matching MAC address for NAT networking... > ==> default: Setting the name of the VM: rhel-ose_default_1460496916213_82608 > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 => 2222 (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2222 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Connection timeout. Retrying... > default: Warning: Remote connection disconnect. Retrying... > default: > default: Vagrant insecure key detected. Vagrant will automatically replace > default: this with a newly generated keypair for better security. > default: > default: Inserting generated public key within guest... > default: Removing insecure key from the guest if it's present... > default: Key inserted! Disconnecting and reconnecting using new SSH key... > ==> default: Machine booted and ready! > ==> default: Checking for guest additions in VM... > default: No guest additions were detected on the base box for this VM! Guest > default: additions are required for forwarded ports, shared folders, host only > default: networking, and more. If SSH fails on this machine, please install > default: the guest additions and repackage the box to continue. > default: > default: This is not an error message; everything may continue to work properly, > default: in which case you may ignore this message. > ==> default: Configuring and enabling network interfaces... > ==> default: Registering box with vagrant-registration... > ==> default: Copying TLS certificates to C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > ==> default: Rsyncing folder: /cygdrive/c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant > ==> default: Running provisioner: shell... > default: Running: inline script > ==> default: Running provisioner: shell... > default: Running: inline script > ==> default: > ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory. > ==> default: To modify the number of cores and/or available memory set the environment variables > ==> default: VM_CPU respectively VM_MEMORY. > ==> default: > ==> default: You can now access the OpenShift console on: https://10.1.2.2:8443/console > ==> default: > ==> default: To use OpenShift CLI, run: > ==> default: $ vagrant ssh > ==> default: $ oc login 10.1.2.2:8443 > ==> default: > ==> default: Configured users are (<username>/<password>): > ==> default: openshift-dev/devel > ==> default: admin/admin > ==> default: > ==> default: If you have the oc client library on your host, you can also login from your host. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21820) Update service-manager parsing for cygwin

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21820?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21820. --------------------------------- Verified in JBDS 9.1.0.GA. > Update service-manager parsing for cygwin > ----------------------------------------- > > Key: JBIDE-21820 > URL: https://issues.jboss.org/browse/JBIDE-21820 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.3.1.Beta2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Labels: respin-c > Fix For: 4.3.1.CR1 > > > Link to https://github.com/projectatomic/vagrant-service-manager/issues/10 > If the service-manager issue ever gets solved, we'll need to update our parsing code to check for cygwin. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2016