May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21979) Update Hibernate Tools dependency in org.jboss.tools.hibernate.runtime.v_5_1 to version 5.1.0.Alpha2

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21979?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-21979. ------------------------------------ > Update Hibernate Tools dependency in org.jboss.tools.hibernate.runtime.v_5_1 to version 5.1.0.Alpha2 > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-21979 > URL: https://issues.jboss.org/browse/JBIDE-21979 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21980) Remove MetadataHelper class from org.jboss.tools.hibernate.runtime.v_5_1 and org.jboss.tools.hibernate.runtime.v_5_1.test

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21980?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-21980. ------------------------------------ verified in Devstudio 10.0.0.Alpha3-v20160529-2224-B5466 > Remove MetadataHelper class from org.jboss.tools.hibernate.runtime.v_5_1 and org.jboss.tools.hibernate.runtime.v_5_1.test > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21980 > URL: https://issues.jboss.org/browse/JBIDE-21980 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Fix For: 4.4.0.Alpha1 > > > This functionality is now included in core Hibernate Tools 5.1.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22037) HQL queries doesn't work with Hibernate 5

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22037?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-22037. ------------------------------------ verified in Devstudio 10.0.0.Alpha3-v20160529-2224-B5466 > HQL queries doesn't work with Hibernate 5 > ----------------------------------------- > > Key: JBIDE-22037 > URL: https://issues.jboss.org/browse/JBIDE-22037 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Rastislav Wagner > Assignee: Koen Aers > Fix For: 4.4.0.Alpha1 > > > {code} > org.hibernate.hql.internal.ast.QuerySyntaxException: Actor is not mapped [from Actor] > at org.hibernate.hql.internal.ast.QuerySyntaxException.generateQueryException(QuerySyntaxException.java:79) > at org.hibernate.QueryException.wrapWithQueryString(QueryException.java:103) > at org.hibernate.hql.internal.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:218) > at org.hibernate.hql.internal.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:142) > at org.hibernate.engine.query.spi.HQLQueryPlan.<init>(HQLQueryPlan.java:115) > at org.hibernate.engine.query.spi.HQLQueryPlan.<init>(HQLQueryPlan.java:76) > at org.hibernate.engine.query.spi.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:150) > at org.hibernate.internal.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:302) > at org.hibernate.internal.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:240) > at org.hibernate.internal.SessionImpl.createQuery(SessionImpl.java:1894) > 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:497) > at org.jboss.tools.hibernate.runtime.common.Util.invokeMethod(Util.java:43) > at org.jboss.tools.hibernate.runtime.common.AbstractSessionFacade.createQuery(AbstractSessionFacade.java:47) > at org.hibernate.eclipse.console.common.HQLQueryPage.setSession(HQLQueryPage.java:133) > at org.hibernate.eclipse.console.common.HibernateExtension$2.execute(HibernateExtension.java:115) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.eclipse.console.common.HibernateExtension.execute(HibernateExtension.java:189) > at org.hibernate.eclipse.console.common.HibernateExtension.executeHQLQuery(HibernateExtension.java:111) > at org.hibernate.console.ConsoleConfiguration.executeHQLQuery(ConsoleConfiguration.java:306) > at org.hibernate.eclipse.hqleditor.HQLEditor.executeQuery(HQLEditor.java:447) > at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:88) > 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:4481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > 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:497) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Caused by: org.hibernate.hql.internal.ast.QuerySyntaxException: Actor is not mapped > at org.hibernate.hql.internal.ast.util.SessionFactoryHelper.requireClassPersister(SessionFactoryHelper.java:171) > at org.hibernate.hql.internal.ast.tree.FromElementFactory.addFromElement(FromElementFactory.java:91) > at org.hibernate.hql.internal.ast.tree.FromClause.addFromElement(FromClause.java:76) > at org.hibernate.hql.internal.ast.HqlSqlWalker.createFromElement(HqlSqlWalker.java:321) > at org.hibernate.hql.internal.antlr.HqlSqlBaseWalker.fromElement(HqlSqlBaseWalker.java:3701) > at org.hibernate.hql.internal.antlr.HqlSqlBaseWalker.fromElementList(HqlSqlBaseWalker.java:3590) > at org.hibernate.hql.internal.antlr.HqlSqlBaseWalker.fromClause(HqlSqlBaseWalker.java:716) > at org.hibernate.hql.internal.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:572) > at org.hibernate.hql.internal.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:309) > at org.hibernate.hql.internal.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:257) > at org.hibernate.hql.internal.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:262) > at org.hibernate.hql.internal.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:190) > ... 54 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22459) Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22459?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-22459: --------------------------------------------- from [~lkrzyzanek]: {quote} regarding API: Any client were supposed to use “sys_type=quickstart”. Don’t know why you used that hack “query=(sys_type…”. The sys_type works in V1 from beginning. In v2 we put more security in query parameter. Hopefully you’ll be able to manage the slight change of query. {quote} We use the query the team behind dcp provided us with :) The query is possible to override since we provide the value via {code}http://download.jboss.org/jbosstools/configuration/ide-config.properties{code}. What is worse is if you change the output format. Then we are somewhat screwed. > Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22459 > URL: https://issues.jboss.org/browse/JBIDE-22459 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > > ~1 year ago we made Central use DCP for querying the quickstart list to let users start easily with the examples/quickstrats. > In the context of EAP 7 coming out there are new quickstarts. > In a perfect world the following have happend: > EAP 7 Quickstarts added to DCP > Central in both devstudio 9 and 10 can see both EAP 6 and EAP 7 quickstarts > What seem to have happened instead is: > if EAP 7 quickstarts are added to DCP EAP 6 quickstarts are no longer available > DCP has changed its format/approach and not sure what the impact of this is > (can devstudio 9 still work ? must devstudio 10 change ? will we ever have multiple version support ?) > This bug is to gather the facts and figure out what we do about them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21283) Update Central to Spring IDE 3.7.3 release when available (replaces CI build)

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21283?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-21283. ------------------------------ Verified in JBDS 10.0.0.Alpha3-v20160529-2224-B5466 > Update Central to Spring IDE 3.7.3 release when available (replaces CI build) > ----------------------------------------------------------------------------- > > Key: JBIDE-21283 > URL: https://issues.jboss.org/browse/JBIDE-21283 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central, target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha2 > > > [~mlippert] said: {quote} > Sorry for the inconvenience regarding the weaving hook versions, the AJDT build uses a specific self-built version of that instead of the one that is included in the Mars and Neon repos. However, this will change in the near future. We are switching to a new build and had to made a few additional changes (as a heads-up): > org.eclipse.equinox.weaving.aspectj(.source) will be moved to the AJDT project, therefore no longer in Neon (from M5 on, I think) > org.eclipse.equinox.weaving.sdk(.feature.group) will be moved to the AJDT project as well, also no longer in the Neon repo (from M5 on as well) > Both will have higher version numbers and being distributed as part of the AJDT build (instead of Equinox). > I think this will affect the AJDT versions for Eclipse 4.5 + 4.6, so you might come across a similar situation with the Mars repositories (two different versions of the weaving.sdk feature, two different versions of the weaving.hook bundle). > {quote} > Then [~dgolovin] said: {quote}Didn't test it, but it seems good to be applied and get Spring IDE back to Central. But it is a nightly build, isn't it? We should remember to update it to released version at some point. Could you create issue for that?{quote} > So here's that tracker issue, to ensure we get a working SpringIDE 3.7.3 for Neon once it's released, along with a working version of AJDT. May require TWO mirrors instead of one, as we used to have for Mars. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21223) Version of AngularJS in Central is older than version used in jbosstools-jst

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21223?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-21223. ------------------------------ Verified in JBDS 10.0.0.Alpha3-v20160529-2224-B5466 > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21223 > URL: https://issues.jboss.org/browse/JBIDE-21223 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xm... > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/... > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xm... > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22233) Update Hibernate 4.3 runtime dependency to Hibernate Tools 4.3.3.Final and Hibernate Core 4.3.11.Final

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22233?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-22233. ------------------------------------ verified in Devstudio 10.0.0.Alpha3-v20160529-2224-B5466 > Update Hibernate 4.3 runtime dependency to Hibernate Tools 4.3.3.Final and Hibernate Core 4.3.11.Final > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22233 > URL: https://issues.jboss.org/browse/JBIDE-22233 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge, hibernate > Reporter: Koen Aers > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22418) Update AERI Eclipse IDE Client to 2.0

by Marcel Bruch (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22418?page=com.atlassian.jira.plugi... ] Marcel Bruch commented on JBIDE-22418: -------------------------------------- ok. I'll do a v1.101 (mars) and a v2.0 (neon) release and keep the (separate) v1.101 update site around for some time. > Update AERI Eclipse IDE Client to 2.0 > ------------------------------------- > > Key: JBIDE-22418 > URL: https://issues.jboss.org/browse/JBIDE-22418 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aeri > Reporter: Marcel Bruch > Assignee: Marcel Bruch > > I'm about to release 2.0.0 for Neon.0. > [~nickboldt], what is the earliest release of JBIDE / Devstudio that will pick up 2.0.0? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22459) Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central

by Libor Krzyžanek (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22459?page=com.atlassian.jira.plugi... ] Libor Krzyžanek commented on JBIDE-22459: ----------------------------------------- If it's cached then it's OK. > Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22459 > URL: https://issues.jboss.org/browse/JBIDE-22459 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > > ~1 year ago we made Central use DCP for querying the quickstart list to let users start easily with the examples/quickstrats. > In the context of EAP 7 coming out there are new quickstarts. > In a perfect world the following have happend: > EAP 7 Quickstarts added to DCP > Central in both devstudio 9 and 10 can see both EAP 6 and EAP 7 quickstarts > What seem to have happened instead is: > if EAP 7 quickstarts are added to DCP EAP 6 quickstarts are no longer available > DCP has changed its format/approach and not sure what the impact of this is > (can devstudio 9 still work ? must devstudio 10 change ? will we ever have multiple version support ?) > This bug is to gather the facts and figure out what we do about them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-224) DockerException in DockerConnection.listContainers [EBZ#494871]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-224: --------------------------------------- Summary: DockerException in DockerConnection.listContainers [EBZ#494871] Key: ERT-224 URL: https://issues.jboss.org/browse/ERT-224 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot The following problem was reported via the automated error reporting: Message: Timeout: GET https://192.168.99.101:2376/containers/json?all=1 org.eclipse.linuxtools.docker.core.DockerException: Timeout: GET https://192.168.99.101:2376/containers/json?all=1 at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listContainers(DockerConnection.java:635) at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getContainers(DockerConnection.java:483) at org.eclipse.linuxtools.internal.docker.ui.views.DockerContainersContentProvider$1.run(DockerContainersContentProvider.java:64) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Bundles: | org.eclipse.core.jobs | 3.8.0.v20160209-0147 | 3.8.0.v20160209-0147 | | org.eclipse.linuxtools.docker.core | 2.0.0.201605161002 | 2.0.0.201605161002 | | org.eclipse.linuxtools.docker.ui | 2.0.0.201605161002 | 2.0.0.201605161002 | Operating Systems: | Windows | 6.1.0 | 6.1.0 | The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/57449... for the latest data. Thank you for your assistance. Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 May 2016