January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10667) Error when creating OpenShift application and going 'back'

by Isaac Rooskov (JIRA)

Isaac Rooskov created JBIDE-10667: ------------------------------------- Summary: Error when creating OpenShift application and going 'back' Key: JBIDE-10667 URL: https://issues.jboss.org/browse/JBIDE-10667 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M5 Reporter: Isaac Rooskov Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 When creating an OpenShift application, after setting the name, application type and pressing the next button you are greeted with a screen to select the cartridges to be embedded into the application. The error here is that the 'back' button is still allowed to be pressed. Pressing the back button will generate the attached error.This occurs because when the user presses the next button mentioned above, the application is created, so upon pressing the 'back button on the embed cartridges screen the wizard seems to become confused since if the user could go back and then press 'next' again to get to the embed cartridges screen, it wouldn't work unless the application name was changed. -- 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

14 years, 1 month

3
3
0 / 0

[JBoss JIRA] (JBIDE-10191) System properties are ignored

by Andre Dietisheim (Created) (JIRA)

System properties are ignored ----------------------------- Key: JBIDE-10191 URL: https://issues.jboss.org/browse/JBIDE-10191 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.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

14 years, 1 month

4
3
0 / 0

[JBoss JIRA] (JBDS-1982) Uninstaller demands administrator login on windows even if it was installed by regular user

by Radim Hopp (Created) (JIRA)

Uninstaller demands administrator login on windows even if it was installed by regular user ------------------------------------------------------------------------------------------- Key: JBDS-1982 URL: https://issues.jboss.org/browse/JBDS-1982 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 5.0.0.M5 Environment: Windows 7 Reporter: Radim Hopp Priority: Critical Fix For: 5.0.0.M5 When trying to uninstall JBDS using uninstaller, user is prompted for administrator password with message "Do you want to allow the following program to make changes to this computer?" Program location "\\path\to\javaw.exe" "-Dizpack.mode=privileged" "-jar" "\\path\to\Uninstaller.jar" Without admin rights, the uninstaller won't execute. -- 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

14 years, 1 month

13
21
0 / 0

[JBoss JIRA] (JBIDE-10557) SWTException before code completion in HQL Editor with Hibernate 4

by Jiri Peterka (Created) (JIRA)

SWTException before code completion in HQL Editor with Hibernate 4 ------------------------------------------------------------------ Key: JBIDE-10557 URL: https://issues.jboss.org/browse/JBIDE-10557 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 3.3.0.M5 Environment: JBDS 5.0.M5a, H62, L64,HSQLDB 1.8 Reporter: Jiri Peterka Assignee: Dmitry Geraskov Fix For: 3.3.0.Beta1 org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.LinkageError: loader constraint violation: when resolving method "org.hibernate.eclipse.console.workbench.HibernateWorkbenchHelper.getImage(Lorg/hibernate/mapping/Property;)Lorg/eclipse/swt/graphics/Image;" the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, org/jboss/tools/hibernate4_0/console/EclipseHQLCompletionRequestor, and the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) for resolved class, org/hibernate/eclipse/console/workbench/HibernateWorkbenchHelper, have different Class objects for the type org/hibernate/mapping/Property used in the signature) at org.eclipse.swt.SWT.error(SWT.java:4282) at org.eclipse.swt.SWT.error(SWT.java:4197) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) 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:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) Caused by: java.lang.LinkageError: loader constraint violation: when resolving method "org.hibernate.eclipse.console.workbench.HibernateWorkbenchHelper.getImage(Lorg/hibernate/mapping/Property;)Lorg/eclipse/swt/graphics/Image;" the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, org/jboss/tools/hibernate4_0/console/EclipseHQLCompletionRequestor, and the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) for resolved class, org/hibernate/eclipse/console/workbench/HibernateWorkbenchHelper, have different Class objects for the type org/hibernate/mapping/Property used in the signature at org.jboss.tools.hibernate4_0.console.EclipseHQLCompletionRequestor.getImage(EclipseHQLCompletionRequestor.java:120) at org.jboss.tools.hibernate4_0.console.EclipseHQLCompletionRequestor.accept(EclipseHQLCompletionRequestor.java:59) at org.hibernate.tool.ide.completion.ConfigurationCompletion.addPropertiesToList(ConfigurationCompletion.java:187) at org.hibernate.tool.ide.completion.ConfigurationCompletion.getMatchingProperties(ConfigurationCompletion.java:80) at org.hibernate.tool.ide.completion.HQLCodeAssist.codeComplete(HQLCodeAssist.java:66) at org.jboss.tools.hibernate4_0.console.ConsoleExtension4_0.hqlCodeComplete(ConsoleExtension4_0.java:93) at org.hibernate.eclipse.hqleditor.HQLCompletionProcessor.computeProposals(HQLCompletionProcessor.java:122) at org.hibernate.eclipse.hqleditor.HQLCompletionProcessor.computeCompletionProposals(HQLCompletionProcessor.java:82) at org.hibernate.eclipse.hqleditor.HQLCompletionProcessor.computeCompletionProposals(HQLCompletionProcessor.java:65) at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1830) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:556) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:553) at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:488) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:482) at org.eclipse.jface.text.contentassist.ContentAssistant$2.run(ContentAssistant.java:377) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) ... 23 more -- 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

14 years, 1 month

4
7
0 / 0

[JBoss JIRA] (JBIDE-10193) Tests start second workbench window

by Viacheslav Kabanovich (Created) (JIRA)

Tests start second workbench window ----------------------------------- Key: JBIDE-10193 URL: https://issues.jboss.org/browse/JBIDE-10193 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI, JSF, Seam 2 Affects Versions: 3.3.0.M4 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.Beta1 Class JBossPerspectiveTest opens perspective by method IWorkbenchWindow.openPage() that creates new window. It is better to call IWorkbench.showPerspective() that displays perspective in current window. -- 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

14 years, 1 month

4
3
0 / 0

[JBoss JIRA] (JBIDE-10432) Text Field "Existing Project" is not decorated if the user did not select any project.

by Andre Dietisheim (Created) (JIRA)

Text Field "Existing Project" is not decorated if the user did not select any project. --------------------------------------------------------------------------------------- Key: JBIDE-10432 URL: https://issues.jboss.org/browse/JBIDE-10432 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M5 Reporter: Andre Dietisheim Assignee: Andre Dietisheim 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

14 years, 1 month

4
3
0 / 0

[JBoss JIRA] (JBIDE-10391) an existing .gitignore should get merged

by Andre Dietisheim (Created) (JIRA)

an existing .gitignore should get merged ---------------------------------------- Key: JBIDE-10391 URL: https://issues.jboss.org/browse/JBIDE-10391 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 We currently create a .gitingore file if there's none so far in the workspace project that shall be "OpenShift enabled". If the project already has a .gitingore file, we just leave it alone. We should enhance this and just add the missing entries (merge the existing content). -- 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

14 years, 1 month

4
13
0 / 0

[JBoss JIRA] (JBIDE-10093) Provide capability to save password

by Pavol Srna (Created) (JIRA)

Provide capability to save password ------------------------------------ Key: JBIDE-10093 URL: https://issues.jboss.org/browse/JBIDE-10093 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 3.3.0.M4 Reporter: Pavol Srna Assignee: Andre Dietisheim 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

14 years, 1 month

8
7
0 / 0

[JBoss JIRA] (JBIDE-10700) Display openshift server details in editor

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-10700: ----------------------------------- Summary: Display openshift server details in editor Key: JBIDE-10700 URL: https://issues.jboss.org/browse/JBIDE-10700 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers, openshift Affects Versions: 3.3.0.M5 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.Beta1 Openshift express editor is basically empty. Not good. -- 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

14 years, 1 month

4
6
0 / 0

[JBoss JIRA] (JBIDE-10271) Make the Forge "cd" Command Aware of the Eclipse Workspace

by Koen Aers (Created) (JIRA)

Make the Forge "cd" Command Aware of the Eclipse Workspace ---------------------------------------------------------- Key: JBIDE-10271 URL: https://issues.jboss.org/browse/JBIDE-10271 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: forge Reporter: Koen Aers Assignee: Koen Aers Fix For: 3.3.0.Beta1 Like the special character '~' in Forge represents the user's home folder, another special character ('#'?) can indicate the root of the workspace. Thus it would be possible to issue "cd #" to navigate to the workspace root. -- 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

14 years, 1 month

3
6
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 January 2012