October 2016 - jbosstools-issues - Jboss List Archives

[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: ------------------------------ Sprint: devex #122 October 2016 (was: devex #121 October 2016) > 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.AM2 > > > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-8371) Query Parameters View: apply parameter value on focus lost

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8371?page=com.atlassian.jira.plugin... ] Koen Aers updated JBIDE-8371: ----------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Query Parameters View: apply parameter value on focus lost > ---------------------------------------------------------- > > Key: JBIDE-8371 > URL: https://issues.jboss.org/browse/JBIDE-8371 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 3.2.0.CR1 > Reporter: Dmitry Geraskov > Assignee: Koen Aers > Fix For: 4.4.2.AM2 > > > Test case: > 1. create query in HQL Editor: > from test.Message m where m.id = :id > 2. propulate the parameter in Parameters view > 3. change type to valid(integer) > 4. enter the value, but do not press Enter > 5. Run the query. > The value is not applied and considered as null. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23066) Generating hbm.xml files always happens using the 3.5 runtime

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23066?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-23066: ------------------------------ Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Generating hbm.xml files always happens using the 3.5 runtime > ------------------------------------------------------------- > > Key: JBIDE-23066 > URL: https://issues.jboss.org/browse/JBIDE-23066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.1.Final > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.2.AM2 > > > This issue is related to JBIDE-22997 and JBIDE-23059. After implementing JBIDE-23059 the phenomenon described in JBIDE-22997 disappeared but the hbm.xml files are now always generated using the 3.5 runtime, even when the project is a hibernate project with a console configuration using another version. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23370) Update RedDeer in TP for JBT 4.4.2.AM3

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23370?page=com.atlassian.jira.plugi... ] Rastislav Wagner commented on JBIDE-23370: ------------------------------------------ We want to update asap and we will release reddeer final Nov 18. > 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

1
0
0 / 0

[JBoss JIRA] (JBTIS-934) Wrong core version in JBTIS TP 4.4.0.CR1-SNAPSHOT

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-934?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky edited comment on JBTIS-934 at 10/18/16 9:24 AM: ------------------------------------------------------------------- I have no idea what was wrong. The whole day all tests were failing due to the above error (locally and all jobs on jenkins) and now it is working. So, it seems that you can keep the TP 4.4.2.AM1. was (Author: apodhrad): I have no idea what was wrong. The whole day all tests failed due to the above error (locally and all jobs jenkins) and now it is working. So, it seems that you can keep the TP 4.4.2.AM1. > Wrong core version in JBTIS TP 4.4.0.CR1-SNAPSHOT > ------------------------------------------------- > > Key: JBTIS-934 > URL: https://issues.jboss.org/browse/JBTIS-934 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.4.0.CR1-TP > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > > I noticed that JBTIS TP 4.4.0.CR1-SNAPSHOT at > https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... > defines the following repository > http://download.jboss.org/jbosstools/neon/staging/updates/core/4.4.2.AM1/ > which is supposed for JBT 4.4.2 / Devstudio 10.2.0 (which will be released later than Devstudio-IS 10.0.0.GA). > I think that there should be the stable one which is 4.4.1.Final. Please correct me if I'm wrong. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-934) Wrong core version in JBTIS TP 4.4.0.CR1-SNAPSHOT

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-934?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-934: ----------------------------------------- I have no idea what was wrong. The whole day all tests failed due to the above error (locally and all jobs jenkins) and now it is working. So, it seems that you can keep the TP 4.4.2.AM1. > Wrong core version in JBTIS TP 4.4.0.CR1-SNAPSHOT > ------------------------------------------------- > > Key: JBTIS-934 > URL: https://issues.jboss.org/browse/JBTIS-934 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.4.0.CR1-TP > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > > I noticed that JBTIS TP 4.4.0.CR1-SNAPSHOT at > https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... > defines the following repository > http://download.jboss.org/jbosstools/neon/staging/updates/core/4.4.2.AM1/ > which is supposed for JBT 4.4.2 / Devstudio 10.2.0 (which will be released later than Devstudio-IS 10.0.0.GA). > I think that there should be the stable one which is 4.4.1.Final. Please correct me if I'm wrong. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[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: --------------------------------------- [~rawagner], what do you propose? My understanding was that we probably want to update asap/now to a snapshot for AM3 and then a Final (we would need to release RedDeer) in time for 4.4.2.Final. Am I right? > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-19933: ------------------------------- Sprint: devex #122 October 2016 > Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it > --------------------------------------------------------------------------------------- > > Key: JBIDE-19933 > URL: https://issues.jboss.org/browse/JBIDE-19933 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.2.Final > > > When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master). > Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch. > It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point. > For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22305?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22305: ------------------------------- Sprint: devex #115 May 2016, devex #116 June 2016, devex #122 October 2016 (was: devex #115 May 2016, devex #116 June 2016) > automate process for fetching latest target platform mirrors > ------------------------------------------------------------ > > Key: JBIDE-22305 > URL: https://issues.jboss.org/browse/JBIDE-22305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.2.AM2 > > Attachments: git.diff.txt > > > Rather than manually pulling requirements, it would be hella sweet if there was a job config into which we could just list all the URLs to mirror and their matching project names. > Then this job would scrape the *.target files for the current list of URLs used, grep out the /requirements/<reqname>/<version>, fetch a new mirror for each new version*, and dump an updated copy of the .target file into the job's workspace. > Thus for webtools we might simply define: > webtools,S-3.8.0M7-20160503010110,http://download.eclipse.org/webtools/do... > and we'd end up with: > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8.... > * Since we already have a http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... job we can just pass parameters to that to invoke the mirroring steps. Would be even better if we could run multiple calls in parallel as neon and wtp can take >2hr > 1. matrix job. each config is a trio of reqname/version/URL which is passed to a process akin to that of the jbosstools-requirements job to perform the mirror; process is now scripted here: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... > 2. when all children are done, a downstream job can runs TP update & validation against new .target files > * fetch http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > * parse that into a list of URLs > * each URL contains REQ_NAME/VERSION, which can then be matched up with similar lines in .target files > * run p2diff between old/new URLs in .target to generate list of changes and verify new site contains all the same IUs > * resulting edited .target files will remain in the workspace, and we can then run > * https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... > * when done if success: > * ideally, generate a PR and attach link in email to jbosstools-dev@ > * if can't generate PR, then attach patch in email to nickboldt & mistria to apply locally in jbosstools-target-platforms to create a PR > * email should includes boilerplate text to send mail to list announcing new change for review -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23093) use consistent variables across all jenkins jobs for streams, TP versions, etc.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23093?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23093: ------------------------------- Sprint: devex #120 September 2016, devex #122 October 2016 (was: devex #120 September 2016) > use consistent variables across all jenkins jobs for streams, TP versions, etc. > ------------------------------------------------------------------------------- > > Key: JBIDE-23093 > URL: https://issues.jboss.org/browse/JBIDE-23093 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > We have a number of inconsistencies between jobs / pom.xml: > * TARGET_PLATFORM_CENTRAL_MAX vs. JBTCENTRALTARGET_VERSION > * TARGET_PLATFORM_VERSION vs. TARGET_PLATFORM_VERSION_MIN > * TARGET_PLATFORM_VERSION_MAXIMUM vs. TARGET_PLATFORM_VERSION_MAX > * stream_jbt vs. jbosstools_site_stream > * version_jbt, versionWithRespin_jbt, JBT_buildversion > * version_ds, vesionWithResin_ds, JBDS_buildversion > * devstudioReleaseVersion, JBDSVersion > Should standardize these. > Can script relationship between version_* and versionWithRespin_*: > {code} > version_jbt=$(echo ${versionWithRespin_jbt} | sed -e '/[abcdwxyz]$/ s/$^.*$$.$$/\1/') > version_ds=$(echo ${versionWithRespin_ds} | sed -e '/[abcdwxyz]$/ s/$^.*$$.$$/\1/') > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
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 October 2016