[JBoss JIRA] (JBIDE-23370) Update RedDeer in TP for JBT 4.4.2.AM3
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23370?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23370:
------------------------------------
I'm ready whenever you provide me a URL from which to mirror. Won't make changes until after AM2 is released, however.
If you want things to go even faster, you could provide a PR for this file:
https://github.com/jbosstools/jbosstools-target-platforms/blob/4.60.x/jbo...
(BTW, nowhere in this JIRA does it even state the new version of RedDeer you want to include. Details!) :D
> Update RedDeer in TP for JBT 4.4.2.AM3
> --------------------------------------
>
> Key: JBIDE-23370
> URL: https://issues.jboss.org/browse/JBIDE-23370
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.4.2.AM2
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM3
>
>
> Due to some changes/fixes in RedDeer that we'd like to use in tests, we'd like to update the RedDeer bits in our TP.
> This was requested by [~rawagner] and we understand that it's just past code freeze for AM2, so this will probably have to wait until after AM2 is released.
> We will want to update RedDeer in the TP to include the latest from
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> I will simply create a snapshot with the rsync script and then give you the url. But it's a bit premature to do it now since it may be a week or two before you actually update the TP.
> So please let me know when you're ready for this task and then I can create the update site immediately.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-19323) java.lang.NullPointerException and no results after HQL query execution when JDBC sting is incorrect
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19323?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-19323:
------------------------------
Fix Version/s: 4.4.2.AM3
> 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
> Fix For: 4.4.2.AM3
>
>
> 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.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-19323) java.lang.NullPointerException and no results after HQL query execution when JDBC sting is incorrect
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19323?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-19323:
------------------------------
Fix Version/s: (was: 4.4.2.AM2)
> 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
>
> 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.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23149) Reverse engineering strategy cannot be set to custom class if generation target is Hibernate 5.x
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23149?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-23149:
------------------------------
Fix Version/s: 4.4.2.AM3
(was: 4.4.2.AM2)
> Reverse engineering strategy cannot be set to custom class if generation target is Hibernate 5.x
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23149
> URL: https://issues.jboss.org/browse/JBIDE-23149
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.4.0.Final
> Reporter: Antal Varga
> Assignee: Koen Aers
> Fix For: 4.4.2.AM3
>
> Attachments: BaseReverseEngineeringStrategy.java, RMAReverseEngineeringStrategy.java
>
>
> The reason for that is the change in ServiceImpl.java in org.jboss.tools.hibernate.runtime.v_5_0*.jar or later.
> private Object newReverseEngineeringStrategy(String className, Object delegate) {...}
> tries to load class using the class loader of the delegate object at first which is *org.hibernate.cfg.reveng.OverrideRepository* and resides in *hibernate-tools-x.yy.jar*.
> The main problem is that while in case of the earlier Hibernate generation targets (e.g. 4.3) the reverse engineering strategy class loading was done by *org.hibernate.util.xpl.ReflectHelper* (and worked well), this option
> happens only as a fallback case now *BUT this only happens if the constructor has not been found* (only NoSuchMethodException is caught).
> Therefore a reverse engineering strategy can only be loaded if it is loaded by the classloader of the hibernate-tools-x.yy.jar or one of its parent loaders (OSGI can make the things more complicated).
> *I think the solution would be to catch ClassNotFoundException as well and try to load reverse engineering class using ReflectHelper in this case.*
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23384) Include integration-tests in staging and stable update sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23384?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23384:
------------------------------------
Assuming you just want me to add integration-tests to the pile of things I already copy over (jbt core, jb coretests, devstudio), this should be easy enough to do as part of the staging/release process.
> Include integration-tests in staging and stable update sites
> ------------------------------------------------------------
>
> Key: JBIDE-23384
> URL: https://issues.jboss.org/browse/JBIDE-23384
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: updatesite
> Affects Versions: 4.4.2.AM2
> Reporter: Martin Malina
> Assignee: Nick Boldt
>
> This will allow us the use case of running integration tests against the latest release of devstudio. This use case is required by EAP QE running our tests against their EAP development builds.
> Currently we have this repo:
> http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-t...
> We're referencing it from our root pom:
> https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po...
> And set up a repository definition for it.
> This allows us to run an individual test bundle.
> This is mostly useful to satisfy test dependencies - tests depend on RedDeer as a whole which is in the target platform. But most tests also have a RedDeer extension in the plugins directory:
> https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl...
> With that, let's move on to why it would be useful to have a stable repo for this, e.g. http://download.jboss.org/jbosstools/neon/stable/updates/integration-tests/
> Imagine you want to run integration tests against the latest stable build. If you just checkout the integration tests and run a test plugin (using mvn verify), it will use everything from the latest nightly repos.
> So to use latest stable release (jbt 4.4.1.Final / devstudio 10.1.0.GA), you need a couple of things:
> 1. Checkout the corresponding branch of the integration tests - jbosstools-4.4.1.x in this case
> 2. Make sure the proper devstudio is used to test against:
> https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te...
> -Ddevstudio.repository=https://devstudio.redhat.com/10.0/stable/updates
> This also includes the TP, so RedDeer should be the correct version
> 3. Make sure the proper integration-tests repo is used for dependencies
> Now this is what we currently don't have. Our root pom will set up the snapshots repo:
> https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po...
> So that's why I would like to have a stable repo of this which I could use.
> There is a workaround - run "mvn install" on the whole integration-tests repo before you run your test. This will install the correct version in your local repo and that may be then used by your test. But maven will probably still prefer the newer versions from the snapshots repo that is set up in the pom.
> To give you an example what can break when you use the newest org.jboss.ide.eclipse.as.reddeer plugin, but run the EAP tests against devstudio 10.1.0.GA:
> The EAP 7 server adapter had 7.0 in the type name in 10.1.0.GA, but in current master it's 7.x (to accommodate for the upcoming EAP 7.1). So if you want to test EAP 7.0.1 CP candidate build against devstudio 10.1.0.GA it will fail on this.
> Sorry for the lengthy explanation, but I hope it's now clear why I'm requesting this.
> Also, I'd be happy to hear if you have some suggestions how to do it differently.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23149) Reverse engineering strategy cannot be set to custom class if generation target is Hibernate 5.x
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23149?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-23149:
------------------------------
Sprint: devex #122 October 2016 (was: devex #121 October 2016)
> Reverse engineering strategy cannot be set to custom class if generation target is Hibernate 5.x
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23149
> URL: https://issues.jboss.org/browse/JBIDE-23149
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.4.0.Final
> Reporter: Antal Varga
> Assignee: Koen Aers
> Fix For: 4.4.2.AM2
>
> Attachments: BaseReverseEngineeringStrategy.java, RMAReverseEngineeringStrategy.java
>
>
> The reason for that is the change in ServiceImpl.java in org.jboss.tools.hibernate.runtime.v_5_0*.jar or later.
> private Object newReverseEngineeringStrategy(String className, Object delegate) {...}
> tries to load class using the class loader of the delegate object at first which is *org.hibernate.cfg.reveng.OverrideRepository* and resides in *hibernate-tools-x.yy.jar*.
> The main problem is that while in case of the earlier Hibernate generation targets (e.g. 4.3) the reverse engineering strategy class loading was done by *org.hibernate.util.xpl.ReflectHelper* (and worked well), this option
> happens only as a fallback case now *BUT this only happens if the constructor has not been found* (only NoSuchMethodException is caught).
> Therefore a reverse engineering strategy can only be loaded if it is loaded by the classloader of the hibernate-tools-x.yy.jar or one of its parent loaders (OSGI can make the things more complicated).
> *I think the solution would be to catch ClassNotFoundException as well and try to load reverse engineering class using ReflectHelper in this case.*
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23370) Update RedDeer in TP for JBT 4.4.2.AM3
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23370?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-23370:
---------------------------------------
[~nickboldt], ok, so what I requested originally still stands. Let me know when you're ready and I will provide a snapshot build.
Later we'll create a new JIRA to update to a new Final version of RedDeer for JBT 4.4.2.Final.
> Update RedDeer in TP for JBT 4.4.2.AM3
> --------------------------------------
>
> Key: JBIDE-23370
> URL: https://issues.jboss.org/browse/JBIDE-23370
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.4.2.AM2
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM3
>
>
> Due to some changes/fixes in RedDeer that we'd like to use in tests, we'd like to update the RedDeer bits in our TP.
> This was requested by [~rawagner] and we understand that it's just past code freeze for AM2, so this will probably have to wait until after AM2 is released.
> We will want to update RedDeer in the TP to include the latest from
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> I will simply create a snapshot with the rsync script and then give you the url. But it's a bit premature to do it now since it may be a week or two before you actually update the TP.
> So please let me know when you're ready for this task and then I can create the update site immediately.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months