June 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12078) Error when creating an application to merge into an existing project

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-12078: ------------------------------------- Summary: Error when creating an application to merge into an existing project Key: JBIDE-12078 URL: https://issues.jboss.org/browse/JBIDE-12078 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.CR1 Reporter: Xavier Coulon Assignee: Xavier Coulon Priority: Blocker Fix For: 3.3.0.CR1 When trying to create an application and merge it into an existing project, the "git cloning settings" page reports an error, while it should not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
6
0 / 0

[JBoss JIRA] (JBIDE-11168) Command 'cd #' not working on windows

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-11168: ---------------------------------- Summary: Command 'cd #' not working on windows Key: JBIDE-11168 URL: https://issues.jboss.org/browse/JBIDE-11168 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 3.3.0.Beta1 Environment: jbdevstudio-product-universal-5.0.0.v201203010100M-H88-Beta1, winXP Reporter: Pavol Srna Assignee: Koen Aers Fix For: 3.3.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
14
0 / 0

[JBoss JIRA] (JBIDE-11727) explore providing an .project_example.xml file in root of quickstarts distributions for easy loading/detection in jboss tools

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11727: ------------------------------------------- Summary: explore providing an .project_example.xml file in root of quickstarts distributions for easy loading/detection in jboss tools Key: JBIDE-11727 URL: https://issues.jboss.org/browse/JBIDE-11727 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Reporter: Max Rydahl Andersen Assignee: Snjezana Peco Fix For: 3.3.0.CR1, 3.3.x in JBIDE-10652 and other situations we have discussed being able to detect that an installation/directory has quickstarts present and have those detected and configured in JBoss Tools as possible examples to use. Need to see if project examples mechanism handle this (i.e. in a distribution the examples would be unzipped/exploded, but when hosted online it would be a zip...can we align this or would it be better with two descriptors?) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
15
0 / 0

[JBoss JIRA] (JBIDE-12063) Runtime detection is not available when installed separately

by Martin Malina (JIRA)

Martin Malina created JBIDE-12063: ------------------------------------- Summary: Runtime detection is not available when installed separately Key: JBIDE-12063 URL: https://issues.jboss.org/browse/JBIDE-12063 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime detection Affects Versions: 3.3.0.CR1 Environment: jbosstools-3.3_stable_branch.aggregate-Update-2012-05-27_14-14-33-H161.zip Reporter: Martin Malina Assignee: Snjezana Peco Fix For: 3.3.0.CR1 Feel free to set the fix version accordingly, but this seems quite serious. When you try to install only these three features on a clean Eclipse Indigo SR2 JEE: JBossAS Tools Seam Tools JBoss Runtime AS Detector finish the installation, restart Eclipse and then go to Preferences -> JBoss Tools, there is no JBoss Tools Runtime Detection available. The runtime detection feature can be seen in the installation details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
5
0 / 0

[JBoss JIRA] (JBIDE-12014) Credentials page appears twice when creating new application and user is not connected

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-12014: ------------------------------------- Summary: Credentials page appears twice when creating new application and user is not connected Key: JBIDE-12014 URL: https://issues.jboss.org/browse/JBIDE-12014 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta3 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 3.3.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-12008) openshift users' credentials auto-verified on model load (too eager)

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-12008: ----------------------------------- Summary: openshift users' credentials auto-verified on model load (too eager) Key: JBIDE-12008 URL: https://issues.jboss.org/browse/JBIDE-12008 Project: Tools (JBoss Tools) Issue Type: Task Components: openshift Affects Versions: 3.3.0.CR1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.CR1 If you have a workspace with 2 users already in it, do the following: 1) Close the express console view 2) restart the workbench 3) wiat for workspace to be fully started 4) open the express console It will take several seconds and freeze UI. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-11603) Support REST API version negotiation

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-11603: ---------------------------------------- Summary: Support REST API version negotiation Key: JBIDE-11603 URL: https://issues.jboss.org/browse/JBIDE-11603 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 3.3.0.Beta3 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta3 The latest REST api supports version negotiation: The client may indicate what service (protocol) version he'd like to use and the service would then use this version to talk to the client: Mail by Lili Nader on the 4.21.2012 {quote} The rest api will return the latest version unless a version is explicitly requested by specifying it in HTTP Accept header in this format "Accept: application/xml; version=1.0" For example: curl -i -k https://localhost/broker/rest/api -H "Accept: application/xml; version=1.0" The api also returns a list of supported versions (right now the only supported version is 1.0): <?xml version="1.0" encoding="UTF-8"?> <response> <version>2.0</version> <supported-api-versions> <supported-api-version>1.0</supported-api-version> </supported-api-versions> </response> If the version requested in not supported then it will return a HTTP Status 406 and an error message as shown below. For example: curl -i -k https://localhost/broker/rest/api -H "Accept: application/xml; version=2.2" HTTP/1.1 406 Not Acceptable <?xml version="1.0" encoding="UTF-8"?> <response> <version>1.0</version> <messages> <message> <field nil="true"></field> <text>Requested API version 2.2 is not supported. Supported versions are 1.0</text> <exit-code/> <severity>error</severity> </message> </messages> <status>not_acceptable</status> <supported-api-versions> <supported-api-version>1.0</supported-api-version> </supported-api-versions> </response> {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
8
0 / 0

[JBoss JIRA] (JBIDE-11958) OpenShift wizard: fields are not in synch when importing app

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-11958: -------------------------------------- Summary: OpenShift wizard: fields are not in synch when importing app Key: JBIDE-11958 URL: https://issues.jboss.org/browse/JBIDE-11958 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.CR1 Reporter: Stefan Bunciak Assignee: Andre Dietisheim Fix For: 3.3.0.CR1 Fields 'use existing project' and git cloning 'location' are not in synch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
6
0 / 0

[JBoss JIRA] (JBIDE-11962) Unchecking 'remember password' has no effect when connecting user from Openshift Explorer

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-11962: ------------------------------------- Summary: Unchecking 'remember password' has no effect when connecting user from Openshift Explorer Key: JBIDE-11962 URL: https://issues.jboss.org/browse/JBIDE-11962 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta3 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 3.3.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-11954) OpenShift import wizard throws exception with preselected gear

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-11954: -------------------------------------- Summary: OpenShift import wizard throws exception with preselected gear Key: JBIDE-11954 URL: https://issues.jboss.org/browse/JBIDE-11954 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.CR1 Reporter: Stefan Bunciak Assignee: Andre Dietisheim Fix For: 3.3.0.CR1 {code} java.lang.ClassCastException: com.openshift.internal.client.GearProfile cannot be cast to java.lang.String at org.eclipse.jface.internal.databinding.swt.ComboItemsProperty$1.handleReplace(ComboItemsProperty.java:57) at org.eclipse.core.databinding.observable.list.ListDiff.accept(ListDiff.java:123) at org.eclipse.jface.internal.databinding.swt.ComboItemsProperty.doUpdateStringList(ComboItemsProperty.java:26) at org.eclipse.jface.internal.databinding.swt.ControlStringListProperty.doUpdateList(ControlStringListProperty.java:38) at org.eclipse.core.databinding.property.list.ListProperty.updateList(ListProperty.java:105) at org.eclipse.core.internal.databinding.property.list.SimplePropertyObservableList.updateList(SimplePropertyObservableList.java:176) at org.eclipse.core.internal.databinding.property.list.SimplePropertyObservableList.set(SimplePropertyObservableList.java:428) at org.eclipse.core.databinding.observable.list.DecoratingObservableList.set(DecoratingObservableList.java:192) at org.eclipse.core.databinding.UpdateListStrategy.doReplace(UpdateListStrategy.java:304) at org.eclipse.core.databinding.ListBinding$6.handleReplace(ListBinding.java:205) at org.eclipse.core.databinding.observable.list.ListDiff.accept(ListDiff.java:123) at org.eclipse.core.databinding.ListBinding$5.run(ListBinding.java:165) at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:148) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:152) at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:170) at org.eclipse.core.databinding.ListBinding.doUpdate(ListBinding.java:152) at org.eclipse.core.databinding.ListBinding.access$2(ListBinding.java:145) at org.eclipse.core.databinding.ListBinding$2.handleListChange(ListBinding.java:55) at org.eclipse.core.databinding.observable.list.ListChangeEvent.dispatch(ListChangeEvent.java:61) at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119) at org.eclipse.core.databinding.observable.list.DecoratingObservableList.fireListChange(DecoratingObservableList.java:59) at org.eclipse.core.databinding.observable.list.DecoratingObservableList.handleListChange(DecoratingObservableList.java:97) at org.eclipse.core.databinding.observable.list.DecoratingObservableList$1.handleListChange(DecoratingObservableList.java:71) at org.eclipse.core.databinding.observable.list.ListChangeEvent.dispatch(ListChangeEvent.java:61) at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119) at org.eclipse.core.databinding.observable.list.DecoratingObservableList.fireListChange(DecoratingObservableList.java:59) at org.eclipse.core.databinding.observable.list.DecoratingObservableList.handleListChange(DecoratingObservableList.java:97) at org.eclipse.core.databinding.observable.list.DecoratingObservableList$1.handleListChange(DecoratingObservableList.java:71) at org.eclipse.core.databinding.observable.list.ListChangeEvent.dispatch(ListChangeEvent.java:61) at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119) at org.eclipse.core.databinding.observable.ChangeSupport.fireEvent(ChangeSupport.java:39) at org.eclipse.core.databinding.observable.list.AbstractObservableList.fireListChange(AbstractObservableList.java:114) at org.eclipse.core.internal.databinding.property.list.SimplePropertyObservableList.notifyIfChanged(SimplePropertyObservableList.java:567) at org.eclipse.core.internal.databinding.property.list.SimplePropertyObservableList.access$3(SimplePropertyObservableList.java:559) at org.eclipse.core.internal.databinding.property.list.SimplePropertyObservableList$2.run(SimplePropertyObservableList.java:78) at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:148) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:152) at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:170) at org.eclipse.core.internal.databinding.property.list.SimplePropertyObservableList$1.handleEvent(SimplePropertyObservableList.java:74) at org.eclipse.core.databinding.property.NativePropertyListener.fireChange(NativePropertyListener.java:63) at org.eclipse.core.internal.databinding.beans.BeanPropertyListener.propertyChange(BeanPropertyListener.java:49) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:347) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:276) at org.jboss.tools.common.databinding.ObservablePojo.firePropertyChange(ObservablePojo.java:29) at org.jboss.tools.common.ui.databinding.ObservableUIPojo.access$0(ObservableUIPojo.java:1) at org.jboss.tools.common.ui.databinding.ObservableUIPojo$1.run(ObservableUIPojo.java:27) at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:164) at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:158) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212) at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1029) at org.jboss.tools.common.ui.WizardUtils.runInWizard(WizardUtils.java:119) at org.jboss.tools.common.ui.WizardUtils.runInWizard(WizardUtils.java:83) at org.jboss.tools.common.ui.WizardUtils.runInWizard(WizardUtils.java:173) at org.jboss.tools.common.ui.WizardUtils.runInWizard(WizardUtils.java:168) at org.jboss.tools.openshift.express.internal.ui.wizard.ApplicationConfigurationWizardPage.loadOpenshiftResources(ApplicationConfigurationWizardPage.java:735) at org.jboss.tools.openshift.express.internal.ui.wizard.ApplicationConfigurationWizardPage$9$1.run(ApplicationConfigurationWizardPage.java:635) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.jboss.tools.openshift.express.internal.ui.action.ImportApplicationAction.run(ImportApplicationAction.java:48) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
8
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 June 2012