[JBoss JIRA] (JBIDE-20099) enable a logstream for Openshift Pods
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20099?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20099:
------------------------------------------
setting 4.3.0.Beta2 as fixVersion for now since I would think that this is most likely even more important than proper port forwarding?
[~maxandersen] WDYT?
> enable a logstream for Openshift Pods
> -------------------------------------
>
> Key: JBIDE-20099
> URL: https://issues.jboss.org/browse/JBIDE-20099
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Diógenes Rettori
> Assignee: Jeff Cantrill
> Fix For: 4.3.0.Beta2
>
>
> enable the eclipse console to show
> oc get logs <pod>
> oc get build-logs <build>
> You click on the pod, then right-click show logs, or double click go to logs...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19798) include buildinfo.json files inside source zips
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19798?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19798:
---------------------------------------
Currently the link is http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... (since master is now Beta2).
And yes, it contains buildinfo/buildinfo.json, so closing.
> include buildinfo.json files inside source zips
> -----------------------------------------------
>
> Key: JBIDE-19798
> URL: https://issues.jboss.org/browse/JBIDE-19798
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
> Max asked: {quote}
> [W]here are the build-info.json files to provide the info you were initially partially encoding into the file names ?
> {quote}
> I replied: {quote}
> Adding json files will take more work as they're produced in a different mojo (GenerateRepositoryFacadeMojo.java, not FetchSourcesFromManifests.java), and I'm a bit hesitant to have one mojo depend on another.
> Do you want that the FetchSourcesFromManifests will also FetchJSONFromUpstreamLatestBuildsFolders (hoping that no respins have happened between the start of the aggregate job and the time when the fetch starts) ? Or should I just include target/fullSite/all/repo/buildinfo.json into target/fullSite/all/jbosstools-src.zip ?
> It's already included in the generated update site + update site zip, so I don't have a problem adding it to the src.zip too... except for the fact that we'll have cross-mojo dependencies. This will mean that the aggregate builds (JBT & JBDS) will depend on BOTH mojos, and that they can only be configured to run in a SPECIFIC order. Is that acceptable?
> {quote}
> (From JBIDE-19756)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19798) include buildinfo.json files inside source zips
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19798?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-19798.
---------------------------------
> include buildinfo.json files inside source zips
> -----------------------------------------------
>
> Key: JBIDE-19798
> URL: https://issues.jboss.org/browse/JBIDE-19798
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
> Max asked: {quote}
> [W]here are the build-info.json files to provide the info you were initially partially encoding into the file names ?
> {quote}
> I replied: {quote}
> Adding json files will take more work as they're produced in a different mojo (GenerateRepositoryFacadeMojo.java, not FetchSourcesFromManifests.java), and I'm a bit hesitant to have one mojo depend on another.
> Do you want that the FetchSourcesFromManifests will also FetchJSONFromUpstreamLatestBuildsFolders (hoping that no respins have happened between the start of the aggregate job and the time when the fetch starts) ? Or should I just include target/fullSite/all/repo/buildinfo.json into target/fullSite/all/jbosstools-src.zip ?
> It's already included in the generated update site + update site zip, so I don't have a problem adding it to the src.zip too... except for the fact that we'll have cross-mojo dependencies. This will mean that the aggregate builds (JBT & JBDS) will depend on BOTH mojos, and that they can only be configured to run in a SPECIFIC order. Is that acceptable?
> {quote}
> (From JBIDE-19756)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3462) remove /development/ and /staging/ URLs from JBDS artifacts
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3462?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-3462:
-------------------------------------
I think this is fine with us (QE). All I ever did on this page was download the build artifacts (installer, eap installer).
But you're only talking about the internal pages, right?
What about this?
https://devstudio.jboss.com/updates/8.0/
The page is similar.
But it seems we no longer have this for 9.0.
https://devstudio.jboss.com/updates/9.0 redirects to https://devstudio.jboss.com/9.0/stable/ which contains Alpha2 update site (or something)
https://devstudio.jboss.com/updates/9.0-development/ redirects to https://devstudio.jboss.com/9.0/development/ which contains Beta1, but with no nice web page.
> remove /development/ and /staging/ URLs from JBDS artifacts
> -----------------------------------------------------------
>
> Key: JBDS-3462
> URL: https://issues.jboss.org/browse/JBDS-3462
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> There's a TODO in the JBDS 9 release guide which says:
> {quote}
> when releasing GA make sure to :%s/development/stable/g and :%s/9.0-staging/9.0/g{quote}
> Here are a couple files which still need to be tweaked so they don't have to change between milestone releases and GA:
> {code}
> ./results/build.xml **
> 224- <!-- <antcall target="create.results.html">
> 225- <param name="update.site.qualifier" value="${update.site.qualifier}"/>
> 226: <param name="PREFIX" value="/earlyaccess/builds/development/${update.site.version}.${BUILD_ALIAS}"/>
> {code}
> {code}
> ./results/index-internal-template.html **
> 102- </div>
> 103- <div align="right">
> 104: <a class="blue" style="align: right;" href="http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site...">JBT Git Revisions</a>
> 105- </div>
> {code}
> {code}
> ./sources/build.xml **
> 176- </target>
> 177-
> 178: <!-- NOTE: after staging a build, latest/all/ folder no longer exists so need to override to find upstream or build fails.
> 179: mvn install -Djbosstools-site=http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.3.Final-build-core/2015-03-01_13-40-40-B357/all/
> 180- -->
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19323) java.lang.NullPointerException and no results after HQL query execution when JDBC sting is incorrect
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19323?page=com.atlassian.jira.plugi... ]
Jiri Peterka updated JBIDE-19323:
---------------------------------
Summary: java.lang.NullPointerException and no results after HQL query execution when JDBC sting is incorrect (was: java.lang.NullPointerException and no results after HQL query execution)
Description:
There should be some more user friendly message, not just NPE when JDBC string is not correct
{code}
!ENTRY org.eclipse.ui 4 0 2015-02-19 10:39:33.217
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.NullPointerException
at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1886)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildSessionFactory(ConfigurationProxy.java:117)
at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:285)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:280)
at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:81)
at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4480)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1413)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3818)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
at org.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
{code}
was:
New for 4.3.x, works with 4.2.x.
{code}
!ENTRY org.eclipse.ui 4 0 2015-02-19 10:39:33.217
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.NullPointerException
at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1886)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildSessionFactory(ConfigurationProxy.java:117)
at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:285)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:280)
at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:81)
at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4480)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1413)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3818)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
at org.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
{code}
Steps to Reproduce:
STEP: Create maven project with Hibernate 4.3 and h2 depdencencies (or you can import the one below)
https://github.com/jbosstools/jbosstools-integration-tests/tree/master/te...
STEP: Convert to JPA 2.1 Hibernate Faceted project
STEP: Do some mistake in JDBC string
STEP: Generate JPA Entities from Tables (sakila db was used - https://github.com/maxandersen/sakila-h2)
STEP: Open HQL Editor
STEP: Run from Actor query
ASSERT: Query should be executed and result should be shown in Hibernate Query Result view
was:
STEP: Create maven project with Hibernate 4.3 and h2 depdencencies (or you can import the one below)
https://github.com/jbosstools/jbosstools-integration-tests/tree/master/te...
STEP: Convert to JPA 2.1 Hibernate Faceted project
STEP: Generate JPA Entities from Tables (sakila db was used - https://github.com/maxandersen/sakila-h2)
STEP: Open HQL Editor
STEP: Run from Actor query
ASSERT: Query should be executed and result should be shown in Hibernate Query Result view
> java.lang.NullPointerException and no results after HQL query execution when JDBC sting is incorrect
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19323
> URL: https://issues.jboss.org/browse/JBIDE-19323
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.0.Alpha1
> Reporter: Jiri Peterka
> Assignee: Jiri Peterka
> Priority: Minor
> Fix For: 4.3.0.Beta2
>
>
> There should be some more user friendly message, not just NPE when JDBC string is not correct
> {code}
> !ENTRY org.eclipse.ui 4 0 2015-02-19 10:39:33.217
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.NullPointerException
> at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1886)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
> at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildSessionFactory(ConfigurationProxy.java:117)
> at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:285)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:280)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:81)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4480)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1413)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3818)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19323) java.lang.NullPointerException and no results after HQL query execution when JDBC sting is incorrect
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19323?page=com.atlassian.jira.plugi... ]
Jiri Peterka reassigned JBIDE-19323:
------------------------------------
Assignee: Koen Aers (was: Jiri Peterka)
> java.lang.NullPointerException and no results after HQL query execution when JDBC sting is incorrect
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19323
> URL: https://issues.jboss.org/browse/JBIDE-19323
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.0.Alpha1
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Priority: Minor
> Fix For: 4.3.0.Beta2
>
>
> There should be some more user friendly message, not just NPE when JDBC string is not correct
> {code}
> !ENTRY org.eclipse.ui 4 0 2015-02-19 10:39:33.217
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.NullPointerException
> at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1886)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
> at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildSessionFactory(ConfigurationProxy.java:117)
> at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:285)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:280)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:81)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4480)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1413)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3818)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months