[JBoss JIRA] (JBIDE-11335) InvalidNameOpenShiftException while trying to add cartridge "jenkins-client-1.4" to New OpenShift Express Application
by Daniel Azarov (JIRA)
Daniel Azarov created JBIDE-11335:
-------------------------------------
Summary: InvalidNameOpenShiftException while trying to add cartridge "jenkins-client-1.4" to New OpenShift Express Application
Key: JBIDE-11335
URL: https://issues.jboss.org/browse/JBIDE-11335
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Daniel Azarov
Assignee: Andre Dietisheim
Attachments: NewJenkinsApplication.png, NewOpenShiftExpressApplication.png, ProblemOccurred.png
Test case:
1. Open wizard New OpenShift Express Application
!NewOpenShiftExpressApplication.png!
2. Click to checkbox for cartridge "jenkins-client-1.4"
!NewJenkinsApplication.png!
3. Type "testJenkins" then press "Ok"
FAIL:
!ProblemOccurred.png!
{code}
com.openshift.express.client.InvalidNameOpenShiftException: Application name "testJenkins" contains uppercase letters (only lowercase allowed)
at com.openshift.express.client.OpenShiftService.validateApplicationName(OpenShiftService.java:215)
at com.openshift.express.client.OpenShiftService.createApplication(OpenShiftService.java:200)
at com.openshift.express.client.OpenShiftService.createApplication(OpenShiftService.java:193)
at com.openshift.express.internal.client.InternalUser.createApplication(InternalUser.java:197)
at org.jboss.tools.openshift.express.internal.core.console.UserDelegate.createApplication(UserDelegate.java:117)
at org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizardModel.createApplication(OpenShiftExpressApplicationWizardModel.java:352)
at org.jboss.tools.openshift.express.internal.ui.wizard.ApplicationConfigurationWizardPageModel.createJenkinsApplication(ApplicationConfigurationWizardPageModel.java:294)
at org.jboss.tools.openshift.express.internal.ui.wizard.ApplicationConfigurationWizardPage$6.run(ApplicationConfigurationWizardPage.java:515)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{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, 11 months
[JBoss JIRA] (JBIDE-11522) loader constraint violation: when resolving overridden method
by Jiri Peterka (JIRA)
Jiri Peterka created JBIDE-11522:
------------------------------------
Summary: loader constraint violation: when resolving overridden method
Key: JBIDE-11522
URL: https://issues.jboss.org/browse/JBIDE-11522
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.Beta3
Environment: JBT 3.3.Beta3-trunk
Reporter: Jiri Peterka
Assignee: Dmitry Geraskov
Fix For: 3.3.0.Beta3
java.lang.LinkageError: loader constraint violation: when resolving overridden method "org.jboss.tools.hibernate3_5.HQLQueryPage.setSession(Lorg/hibernate/Session;)V" the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, org/jboss/tools/hibernate3_5/HQLQueryPage, and its superclass loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader), have different Class objects for the type org/hibernate/Session used in the signature
at org.jboss.tools.hibernate3_5.HibernateExtension3_5$1.execute(HibernateExtension3_5.java:74)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
at org.jboss.tools.hibernate3_5.HibernateExtension3_5.execute(HibernateExtension3_5.java:199)
at org.jboss.tools.hibernate3_5.HibernateExtension3_5.executeHQLQuery(HibernateExtension3_5.java:71)
at org.hibernate.console.ConsoleConfiguration.executeHQLQuery(ConsoleConfiguration.java:299)
at org.hibernate.eclipse.hqleditor.HQLEditor.executeQuery(HQLEditor.java:447)
at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:85)
at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59)
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$6.handleEvent(ActionContributionItem.java:452)
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)
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
[JBoss JIRA] (JBIDE-11567) Provide a way to add runtime detection path using SWTBot
by Lucia Jelinkova (JIRA)
Lucia Jelinkova created JBIDE-11567:
---------------------------------------
Summary: Provide a way to add runtime detection path using SWTBot
Key: JBIDE-11567
URL: https://issues.jboss.org/browse/JBIDE-11567
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime detection
Affects Versions: 3.3.0.Beta2
Reporter: Lucia Jelinkova
Assignee: Snjezana Peco
I've started to develop UI automated tests for runtime detection using SWTBot. The problem is that when clicking the Add button on JBoss Tools Runtime Detection preferences page there is a native file dialog shown that cannot be operated by SWTBot.
Would it be possible to display a dialog similar to the one displayed by Edit button? There is the possibility to provide the path into the text field (that can be done by SWTBot) or to Browse the file system (used by normal users).
--
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