May 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10066) Make sure you typed the name correctly, and then try again

by Burr Sutter (Created) (JIRA)

Make sure you typed the name correctly, and then try again ---------------------------------------------------------- Key: JBIDE-10066 URL: https://issues.jboss.org/browse/JBIDE-10066 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Environment: JBoss Tools 3.3.M4 http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.M4/ Reporter: Burr Sutter Assignee: Koen Aers Attachments: entity.png Following the Forge Samples at https://docs.jboss.org/author/display/FORGE/Samples new-project --named example --topLevelPackage com.example persistence setup --provider HIBERNATE --container JBOSS_AS7 entity --named SampleEntity field string --named sampleField field temporal --named createdOn --type TIMESTAMP ls when you type "entity --named SampleEntity" the result is the attached screenshot. -- 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, 11 months

5
4
0 / 0

[JBoss JIRA] (JBIDE-11609) Wrong provider and plugin name for org.jboss.tools.common.mylyn plugin

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-11609: --------------------------------------- Summary: Wrong provider and plugin name for org.jboss.tools.common.mylyn plugin Key: JBIDE-11609 URL: https://issues.jboss.org/browse/JBIDE-11609 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 3.3.0.Beta3 Environment: JBT nighlty build from 21st April Reporter: Lucia Jelinkova Assignee: Alexey Kazakov Fix For: 3.3.0.Beta3 Attachments: common.mylyn.jpg When I open Help -> About Eclipse -> Installation details an select "Plug-ins" tab, there is wrong provider and plugin name for plugin org.jboss.tools.common.mylyn (see attachment). -- 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, 11 months

3
4
0 / 0

[JBoss JIRA] (JBIDE-9915) Cmd+4 Quick Access Does not Work on Windows and Linux

by Koen Aers (Created) (JIRA)

Cmd+4 Quick Access Does not Work on Windows and Linux ----------------------------------------------------- Key: JBIDE-9915 URL: https://issues.jboss.org/browse/JBIDE-9915 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Reporter: Koen Aers Assignee: Koen Aers Fix For: 3.3.0.M4 -- 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, 11 months

4
3
0 / 0

[JBoss JIRA] (JBIDE-11431) Cannot log into user account, invalid json being reported

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-11431: ---------------------------------------- Summary: Cannot log into user account, invalid json being reported Key: JBIDE-11431 URL: https://issues.jboss.org/browse/JBIDE-11431 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta3 in a mail from Nam Duong on the 27th of March: {quote} Hi, I am getting the following errors when trying to login to my openshift account in Eclipse, talked to Nam Duong and it was suggested to email you the error I got. Could not check user credentials: Could not unmarshall response "{"messages":"","broker_c":["namespace","rhlogin","ssh","app_uuid","debug","alter","cartridge","cart_type","action","app_name","api"],"api":"1.1.3","api_c":["placeholder"],"exit_code":0,"result":"","debug":"","data":{"app_info":{"test1":{"framework":"php-5.3","embedded":{"mysql-5.1":{"info":"Connection URL: mysql://127.12.203.1:3306/\n"},"phpmyadmin-3.4":{"info":"URL: https://test1-cpc.rhcloud.com/phpmyadmin/\n"}},"aliases":null,"creation_time":"2012-03-26T11:11:29-04:00","uuid":"f86f404f81d94838a05816fd7fbabf30"}},"user_info":{"ssh_type":null,"consumed_gears":1,"rhc_domain":"rhcloud.com","system_ssh_keys":null,"vip":false,"max_gears":5,"namespace":"cpc","ssh_key":null,"ssh_keys":{"uk":{"type":"ssh-rsa","key":"AAAAB3NzaC1yc2EAAAADAQABAAABAQC789Mv+LVq2LLu+1f5FobFjYJIGYfMqiVsG3a0WwHz5fVGvccqsP3Oity7L5K9jKBP+o1sZwOL2x8ZOf8WsE0ZLXPgMIQURKUgES9uu3Of+PuWm0D3lylnxkMgT9bPolDjZxqBfZojrfl2oZ3Z+jdqUJg4a+1gReQHob4vM66Y0XCdWDEQDNiZpNQwCwmah8mE4F0CVO1ivd6wJpZtFstvjiQoB/7J2w7Po9BmNVzJMiUY3xiVLGuRhSEBO2DqLibrpB3kvD1cXUhqK0dwI5r5maMBeaaBTpPlcqD+1BbLplbDlJ+L5/90T9v58dBsYIKO3i6BkrbJn40dlGqmvo8f"}},"rhlogin":"kan.li(a)accenture.com","uuid":"eb6b8d6d25ab4961926215908a3fd474","env_vars":null}}}". {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, 11 months

2
23
0 / 0

[JBoss JIRA] (JBIDE-11418) OpenShift Express: Unable to verify user credentials with a user doesn't have registered domain

by Attila Nagy (JIRA)

Attila Nagy created JBIDE-11418: ----------------------------------- Summary: OpenShift Express: Unable to verify user credentials with a user doesn't have registered domain Key: JBIDE-11418 URL: https://issues.jboss.org/browse/JBIDE-11418 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta3 Reporter: Attila Nagy Assignee: Andre Dietisheim When I try to log on with a user which doesn't have a register domain namespace, the verification fails and the wizard returns the following error-message: Could not check user credentials: Could not unmarshall response "{"api_c":["placeholder"],"result":"","exit_code":0,"api":"1.1.3","data":{"user_info":{"domains":[],"max_gears":5,"vip":false,"ssh_keys":{},"uuid":"ab2cae3fb9f2462a83f83cfa26f1fb64","rhlogin":"anagy+2012032703(a)redhat.com","consumed_gears":0,"ssh_type":"","rhc_domain":"dev.rhcloud.com","ssh_key":""},"app_info":{}},"broker_c":["namespace","rhlogin","ssh","app_uuid","debug","alter","cartridge","cart_type","action","app_name","api"],"messages":"","debug":""}". -- 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, 11 months

3
15
0 / 0

[JBoss JIRA] (JBIDE-11510) Implement in EL open-on, content assist, and validation of bean properties accessed by []

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-11510: --------------------------------------------- Summary: Implement in EL open-on, content assist, and validation of bean properties accessed by [] Key: JBIDE-11510 URL: https://issues.jboss.org/browse/JBIDE-11510 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core, jsp/jsf/xml source editing Affects Versions: 3.3.0.Beta1 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.Beta3 See Expression Language Specification, Version 2.1, Section 1.6 "Operators [] and .". EXECUTE: Create CDI or JSF bean with name 'user' and property 'address'. EXECUTE: Write in a page the EL #{user['ad']} and save. ASSERT: Validation creates marker "'ad' cannot be resolved". ASSERT: Content assist at 'ad|' suggest proposal 'address'. EXECUTE: Write in a page the EL #{user['address']} and save. ASSERT: Open-on at token 'address' opens Java element that represents property 'address'. -- 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, 11 months

3
5
0 / 0

[JBoss JIRA] (JBIDE-11428) Updates to the OpenShift Express Console

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-11428: ----------------------------------- Summary: Updates to the OpenShift Express Console Key: JBIDE-11428 URL: https://issues.jboss.org/browse/JBIDE-11428 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Reporter: Burr Sutter Assignee: Andre Dietisheim Attachments: Screen Shot 2012-03-28 at 10.11.47 AM.png 1) Add to JBoss Perspective 2) OpenShift Express Console - is not really a "Console" 3) Add URL for each application - the URL is one of the most important data elements I need to know and it is currently "hidden" in Properties 4) Add the last updated date time - I would like to know when this application was last "pushed", lasted updated And we need to think through the relationship of the OpenShift Express tab and the Servers tab where I need the "server adapter" in order to publish changes. This is a bit confusing, we need to think about adding Publish to the OpenShift tab. -- 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, 11 months

4
9
0 / 0

[JBoss JIRA] (JBIDE-10977) validation of app name is checking project names on first page instead of existing app names

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-10977: ------------------------------------------- Summary: validation of app name is checking project names on first page instead of existing app names Key: JBIDE-10977 URL: https://issues.jboss.org/browse/JBIDE-10977 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Max Rydahl Andersen Assignee: Andre Dietisheim Fix For: 3.3.0.CR1 ASSERT: you do not have any openshift apps named "test" EXECUTE: create a java project named "test" EXECUTE: start openshift wizard, type in new application "test" ASSERT: you can press next and select existing app Currently it complains about project named "test" which shouldn't prevent creation of the app since I can choose to use the existing project named "test" to merge with or even if the project being checked out has a different name. Shouldn't it just be a warning ? -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-11164) Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-11164: ------------------------------------ Summary: Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor Key: JBIDE-11164 URL: https://issues.jboss.org/browse/JBIDE-11164 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 3.3.0.Beta1 Environment: jbosstools-3.3_stable_branch.aggregate-Update-2012-02-29_14-32-12-H100.zip,L64 Reporter: Jiri Peterka Assignee: Snjezana Peco Priority: Minor Fix For: 3.3.0.Beta2 !ENTRY org.eclipse.ui.workbench 4 0 2012-03-05 13:27:01.277 !MESSAGE Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor !STACK 0 java.lang.RuntimeException: Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor at org.eclipse.ui.internal.WorkbenchPartReference$1.widgetDisposed(WorkbenchPartReference.java:171) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:123) 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.Widget.sendEvent(Widget.java:1282) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1263) at org.eclipse.swt.widgets.Widget.release(Widget.java:1080) at org.eclipse.swt.widgets.Control.release(Control.java:3488) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1294) at org.eclipse.swt.widgets.Widget.release(Widget.java:1083) at org.eclipse.swt.widgets.Control.release(Control.java:3488) at org.eclipse.swt.widgets.Widget.dispose(Widget.java:462) at org.eclipse.ui.internal.EditorSashContainer.disposeParent(EditorSashContainer.java:195) at org.eclipse.ui.internal.PartSashContainer.dispose(PartSashContainer.java:599) at org.eclipse.ui.internal.EditorSashContainer.dispose(EditorSashContainer.java:187) at org.eclipse.ui.internal.EditorAreaHelper.dispose(EditorAreaHelper.java:125) at org.eclipse.ui.internal.WorkbenchPage.dispose(WorkbenchPage.java:1898) at org.eclipse.ui.internal.WorkbenchWindow.closeAllPages(WorkbenchWindow.java:894) at org.eclipse.ui.internal.WorkbenchWindow.hardClose(WorkbenchWindow.java:1729) at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:730) at org.eclipse.ui.internal.WorkbenchWindow.access$0(WorkbenchWindow.java:715) at org.eclipse.ui.internal.WorkbenchWindow$6.run(WorkbenchWindow.java:867) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:865) at org.eclipse.jface.window.WindowManager.close(WindowManager.java:109) at org.eclipse.ui.internal.Workbench$18.run(Workbench.java:1114) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:1111) at org.eclipse.ui.internal.Workbench.access$15(Workbench.java:1040) at org.eclipse.ui.internal.Workbench$25.run(Workbench.java:1284) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.Workbench.close(Workbench.java:1282) at org.eclipse.ui.internal.Workbench.close(Workbench.java:1254) at org.eclipse.ui.internal.testing.WorkbenchTestable$2.run(WorkbenchTestable.java:124) 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.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.swtbot.eclipse.core.UITestApplication.start(UITestApplication.java:54) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) -- 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, 11 months

3
4
0 / 0

[JBoss JIRA] (JBIDE-11193) openshift express console - should be in jboss perspective by default

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11193: ------------------------------------------- Summary: openshift express console - should be in jboss perspective by default Key: JBIDE-11193 URL: https://issues.jboss.org/browse/JBIDE-11193 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Reporter: Max Rydahl Andersen Assignee: Andre Dietisheim Fix For: 3.3.0.Beta2 isn't it time openshift console becomes visible by default in jboss perspective? -- 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, 11 months

5
10
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 May 2012