August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16300) Create Hibernate XML Mapping file(s) dialog skips target project selection step

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16300?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-16300: ------------------------------ Fix Version/s: 4.2.x (was: 4.2.0.CR1) > Create Hibernate XML Mapping file(s) dialog skips target project selection step > ------------------------------------------------------------------------------- > > Key: JBIDE-16300 > URL: https://issues.jboss.org/browse/JBIDE-16300 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.1.1.Final > Reporter: Denis Golovin > Assignee: Koen Aers > Fix For: 4.2.x > > > See steps to reproduce. Now wizard doesn't show workspace resources tree to select target project after at leas one class is added to the list on first step. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16300) Create Hibernate XML Mapping file(s) dialog skips target project selection step

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16300?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-16300: ----------------------------------- Hey [~dgolovin], I don't fully understand what behavior you expect here. If you have no classes selected, the wizard seems to create an empty *.hbm.xml file for which you can determine the location. If you have classes selected, the wizard creates a <className>.hbm.xml file in the same folder (package) as the class itself. Does it make sense to have these files generated somewhere else? > Create Hibernate XML Mapping file(s) dialog skips target project selection step > ------------------------------------------------------------------------------- > > Key: JBIDE-16300 > URL: https://issues.jboss.org/browse/JBIDE-16300 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.1.1.Final > Reporter: Denis Golovin > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > > See steps to reproduce. Now wizard doesn't show workspace resources tree to select target project after at leas one class is added to the list on first step. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16300) Create Hibernate XML Mapping file(s) dialog skips target project selection step

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16300?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-16300: --------------------------------- Assignee: Koen Aers > Create Hibernate XML Mapping file(s) dialog skips target project selection step > ------------------------------------------------------------------------------- > > Key: JBIDE-16300 > URL: https://issues.jboss.org/browse/JBIDE-16300 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.1.1.Final > Reporter: Denis Golovin > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > > See steps to reproduce. Now wizard doesn't show workspace resources tree to select target project after at leas one class is added to the list on first step. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17274) Support JPA 2.1 in Hibernate Tools

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17274?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-17274. ------------------------------- Resolution: Done > Support JPA 2.1 in Hibernate Tools > ---------------------------------- > > Key: JBIDE-17274 > URL: https://issues.jboss.org/browse/JBIDE-17274 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.2.0.CR1 > > > Until now Hibernate tools "survived" that Hibernate 3.5+ could load hibernate 3 and 4 projects metadata without problems. > With JPA 2.1 this changed and it requires Hibernate 4.3+ to load these metadata. > We could update hibernate tools to use hibernate 4.3 to load the metadata but in doing so we would gain support for JPA 2.1 but at least loose support for loading Hibernate 3.3-4.2+ projects that uses custom user types (there could be more combinations that fails - figuring out how much requires a lot of work, but for now at least we know the usertypes are not binary compatible anymore). > To fix this a rethink/reimplementation is needed of how hibernate tools works. > It basicallly needs to become completely independent of hibernate binaries/classes. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17274) Support JPA 2.1 in Hibernate Tools

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17274?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-17274: ----------------------------------- Hibernate 4.3 support is now working and hence also JPA 2.1 support. There can be remaining problems but they should be tracked under their own JIRA ticket. > Support JPA 2.1 in Hibernate Tools > ---------------------------------- > > Key: JBIDE-17274 > URL: https://issues.jboss.org/browse/JBIDE-17274 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.2.0.CR1 > > > Until now Hibernate tools "survived" that Hibernate 3.5+ could load hibernate 3 and 4 projects metadata without problems. > With JPA 2.1 this changed and it requires Hibernate 4.3+ to load these metadata. > We could update hibernate tools to use hibernate 4.3 to load the metadata but in doing so we would gain support for JPA 2.1 but at least loose support for loading Hibernate 3.3-4.2+ projects that uses custom user types (there could be more combinations that fails - figuring out how much requires a lot of work, but for now at least we know the usertypes are not binary compatible anymore). > To fix this a rethink/reimplementation is needed of how hibernate tools works. > It basicallly needs to become completely independent of hibernate binaries/classes. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14662) Hibernate configuration view should gracefully handle error caused by multiple persistence.xml

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14662?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-14662. ------------------------------- Resolution: Cannot Reproduce Bug > Hibernate configuration view should gracefully handle error caused by multiple persistence.xml > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-14662 > URL: https://issues.jboss.org/browse/JBIDE-14662 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, hibernate > Affects Versions: 4.1.0.Beta1 > Environment: JBDS 7.0.0.Beta1a,64 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > > When importing HTML5 project form Central, Hibernate console isn't properly configured and cannot be expanded and used without errors. > {code} > javax.persistence.PersistenceException: No name provided and several persistence units found > at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:337) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.hibernate.console.ConfigurationFactory.buildJPAConfiguration(ConfigurationFactory.java:218) > at org.hibernate.console.ConfigurationFactory.buildConfiguration(ConfigurationFactory.java:161) > at org.hibernate.console.ConfigurationFactory.createConfiguration(ConfigurationFactory.java:96) > at org.hibernate.console.ConsoleConfiguration$3.execute(ConsoleConfiguration.java:240) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:107) > at org.hibernate.console.ConsoleConfiguration.buildWith(ConsoleConfiguration.java:237) > at org.hibernate.console.ConsoleConfiguration.build(ConsoleConfiguration.java:188) > at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:42) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:100) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106) > at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14662) Hibernate configuration view should gracefully handle error caused by multiple persistence.xml

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14662?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-14662: ----------------------------------- I cannot reproduce this anymore. Maybe the issue was fixed implicitly by the recent JPA 2.1 refactoring. Please reopen if the problem persists. > Hibernate configuration view should gracefully handle error caused by multiple persistence.xml > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-14662 > URL: https://issues.jboss.org/browse/JBIDE-14662 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, hibernate > Affects Versions: 4.1.0.Beta1 > Environment: JBDS 7.0.0.Beta1a,64 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > > When importing HTML5 project form Central, Hibernate console isn't properly configured and cannot be expanded and used without errors. > {code} > javax.persistence.PersistenceException: No name provided and several persistence units found > at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:337) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.hibernate.console.ConfigurationFactory.buildJPAConfiguration(ConfigurationFactory.java:218) > at org.hibernate.console.ConfigurationFactory.buildConfiguration(ConfigurationFactory.java:161) > at org.hibernate.console.ConfigurationFactory.createConfiguration(ConfigurationFactory.java:96) > at org.hibernate.console.ConsoleConfiguration$3.execute(ConsoleConfiguration.java:240) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:107) > at org.hibernate.console.ConsoleConfiguration.buildWith(ConsoleConfiguration.java:237) > at org.hibernate.console.ConsoleConfiguration.build(ConsoleConfiguration.java:188) > at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:42) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:100) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106) > at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18184) Cannot run Cordova project from JBDS (AeroGear QS)

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18184?page=com.atlassian.jira.plugi... ] Gorkem Ercan resolved JBIDE-18184. ---------------------------------- Assignee: Gorkem Ercan Fix Version/s: 4.2.0.CR1 Resolution: Duplicate Issue > Cannot run Cordova project from JBDS (AeroGear QS) > -------------------------------------------------- > > Key: JBIDE-18184 > URL: https://issues.jboss.org/browse/JBIDE-18184 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Environment: Hybrid Mobile Tools 1.0.0.Beta3, JBDS 8.0.0.Beta3, AeroGear 1.0.0.ER1 Quickstarts > Reporter: Petr Stribny > Assignee: Gorkem Ercan > Fix For: 4.2.0.CR1 > > > I can't use "Run on Android device/emulator" options in JBDS for our AeroGear Cordova quickstarts 1.0.0.ER1 (e.g. Helloworld AeroGear Cordova QS). > IDE fails silently. > Log: > {noformat} > !MESSAGE Unhandled event loop exception > !STACK 0 > java.lang.NumberFormatException: For input string: "L" > at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:492) > at java.lang.Integer.parseInt(Integer.java:527) > at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidSDKManager$TargetListParser.getSDKList(AndroidSDKManager.java:194) > at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidSDKManager.listTargets(AndroidSDKManager.java:353) > at org.jboss.tools.aerogear.android.ui.AndroidEmulatorLaunchShortcut.validateBuildToolsReady(AndroidEmulatorLaunchShortcut.java:32) > at org.jboss.tools.aerogear.hybrid.ui.launch.HybridProjectLaunchShortcut.launch(HybridProjectLaunchShortcut.java:64) > at org.jboss.tools.aerogear.hybrid.ui.launch.HybridProjectLaunchShortcut.launch(HybridProjectLaunchShortcut.java:50) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.launch(LaunchShortcutExtension.java:431) > at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.run(LaunchShortcutAction.java:74) > at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.runWithEvent(LaunchShortcutAction.java:123) > 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$5.handleEvent(ActionContributionItem.java:420) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1182) > at org.eclipse.jface.action.ActionContributionItem$9.handleEvent(ActionContributionItem.java:1293) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > 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:382) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17886) Visual Editor: Links is not blocked when page content is fulfilled with javascript

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17886?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-17886: ------------------------------------------- Labels: respin-a (was: ) > Visual Editor: Links is not blocked when page content is fulfilled with javascript > ---------------------------------------------------------------------------------- > > Key: JBIDE-17886 > URL: https://issues.jboss.org/browse/JBIDE-17886 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta3 > Environment: Windows, Linux(xulrunner or webkit) > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Labels: respin-a > Fix For: 4.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17886) Visual Editor: Links is not blocked when page content is fulfilled with javascript

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17886?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-17886: ------------------------------------------------ will be fixed in respin-a. > Visual Editor: Links is not blocked when page content is fulfilled with javascript > ---------------------------------------------------------------------------------- > > Key: JBIDE-17886 > URL: https://issues.jboss.org/browse/JBIDE-17886 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta3 > Environment: Windows, Linux(xulrunner or webkit) > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Labels: respin-a > Fix For: 4.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 August 2014