May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19535) Cannot generate ddl when hibernate console is NOT used

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19535?page=com.atlassian.jira.plugi... ] Jiri Peterka commented on JBIDE-19535: -------------------------------------- Yes, it 4.3 and JPA 2.1 doesn't work for me when console is not used. 4.0,3.5 and 3.5 is ok with JPA 2.0. I'll check with latest nightly and update this JIRA. > Cannot generate ddl when hibernate console is NOT used > ------------------------------------------------------ > > Key: JBIDE-19535 > URL: https://issues.jboss.org/browse/JBIDE-19535 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.3.Beta1 > Environment: JBDS 8.1.0.GA > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Critical > Fix For: 4.3.0.Beta1 > > > Cannot generate ddl when hibernate console is NOT used. It actually works when Hibernate 3.5, 3.6, 4.0 is used but not for 4.3. Found by extended automated tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19750) Install grinder w/ SWTBot 2.2.1.201402241301 fails to run on RHEL7: No more handles!

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19750?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19750: ------------------------------------ That's odd. The job jbosstools-install-p2director.install-tests.matrix_master sets this value via shell script. Maybe it needs to be set up as an environment variable instead, injected via your INSTALL_PLAN.properties file? {code} export MOZILLA_FIVE_HOME=/qa/tools/opt/firefox-5 export SWT_GTK3=0{code} > Install grinder w/ SWTBot 2.2.1.201402241301 fails to run on RHEL7: No more handles! > ------------------------------------------------------------------------------------ > > Key: JBIDE-19750 > URL: https://issues.jboss.org/browse/JBIDE-19750 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Mickael Istria > > {code} > 16:48:30 Installing org.eclipse.swtbot.eclipse.test.junit.feature.group 2.2.1.201402241301. > ... > 13:39:08 !MESSAGE Internal browser is not available: No more handles [Browser style SWT.MOZILLA and Java system property org.eclipse.swt.browser.DefaultType=mozilla are not supported with GTK 3 as XULRunner is not ported for GTK 3 yet] > 13:43:18 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 253.079 sec > 13:43:18 > 13:43:18 Testcase: testInstall took 252.166 sec > {code} - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > I tried to run using `-Dorg.eclipse.swt.browser.DefaultType=webkit` as a script param for `testInstall.groovy` but it must not have passed through to the eclipse install process, as the above error suggests. > Wondering if ... > a) passing through a different *swt.browser.DefaultType*, &/or > b) using a newer SWTBot (which works with Luna [1] now?) > ... might help. > [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=464619 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19443) java.lang.NoClassDefFoundError in Reveng editor when using Hibernate 3.6

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19443?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-19443. ------------------------------- Resolution: Done This seems to work normally. But I recall having fixed this earlier. Could it be that the issue wasn't closed properly? Feel free to reopen if the issue is still present. > java.lang.NoClassDefFoundError in Reveng editor when using Hibernate 3.6 > ------------------------------------------------------------------------ > > Key: JBIDE-19443 > URL: https://issues.jboss.org/browse/JBIDE-19443 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.3.Beta1 > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Critical > Fix For: 4.3.0.Beta1 > > > java.lang.NoClassDefFoundError: Could not initialize class org.hibernate.cfg.reveng.OverrideRepository > at org.jboss.tools.hibernate.proxy.ServiceProxy.newOverrideRepository(ServiceProxy.java:198) > at org.hibernate.eclipse.mapper.editors.ReverseEngineeringEditor.getLazyDatabaseSchema(ReverseEngineeringEditor.java:207) > at org.hibernate.eclipse.mapper.editors.reveng.TablePropertiesBlock.doAdd(TablePropertiesBlock.java:172) > at org.hibernate.eclipse.mapper.editors.reveng.TablePropertiesBlock$1.widgetSelected(TablePropertiesBlock.java:128) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409) > 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.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) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19750) Install grinder w/ SWTBot 2.2.1.201402241301 fails to run on RHEL7: No more handles!

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19750?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19750: ---------------------------------------- On install-grinder, the browser was set to webkit. So I tried to set it to Mozilla. {code} !ENTRY org.eclipse.ui.browser 2 0 2015-05-04 11:40:28.722 11:40:28 !MESSAGE Internal browser is not available: No more handles [Unknown Mozilla path (MOZILLA_FIVE_HOME not set)] {code} Do you know which value should we pass here? And actually, what's supposed to work on our CI slaves? Webkit or Mozilla? > Install grinder w/ SWTBot 2.2.1.201402241301 fails to run on RHEL7: No more handles! > ------------------------------------------------------------------------------------ > > Key: JBIDE-19750 > URL: https://issues.jboss.org/browse/JBIDE-19750 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Mickael Istria > > {code} > 16:48:30 Installing org.eclipse.swtbot.eclipse.test.junit.feature.group 2.2.1.201402241301. > ... > 13:39:08 !MESSAGE Internal browser is not available: No more handles [Browser style SWT.MOZILLA and Java system property org.eclipse.swt.browser.DefaultType=mozilla are not supported with GTK 3 as XULRunner is not ported for GTK 3 yet] > 13:43:18 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 253.079 sec > 13:43:18 > 13:43:18 Testcase: testInstall took 252.166 sec > {code} - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > I tried to run using `-Dorg.eclipse.swt.browser.DefaultType=webkit` as a script param for `testInstall.groovy` but it must not have passed through to the eclipse install process, as the above error suggests. > Wondering if ... > a) passing through a different *swt.browser.DefaultType*, &/or > b) using a newer SWTBot (which works with Luna [1] now?) > ... might help. > [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=464619 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19431) Cannot generate ddl when hibernate console is used

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19431?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-19431: ----------------------------------- Just like I reported in JBIDE-19535, Hibernate versions lower than 4.3 are not supposed to work together with JPA version 2.1 so some of the behavior is normal. What is not normal is that when creating a JPA 2.0 project the ddl generation also doesn't work. But this needs further investigation. > Cannot generate ddl when hibernate console is used > -------------------------------------------------- > > Key: JBIDE-19431 > URL: https://issues.jboss.org/browse/JBIDE-19431 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.3.Beta1 > Environment: JBDS 8.1.0.Beta1 > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Critical > Fix For: 4.3.0.Beta1 > > > Cannot generate ddl when hibernate console is used. I will investigate further, it worked for 4.3 (and didn't work for lower hibernate versions) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19535) Cannot generate ddl when hibernate console is NOT used

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19535?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-19535: ----------------------------------- I have been playing with the tools to try and reproduce this, but my findings are different. With Hibernate 4.3 on my box everything works as expected. I cannot use Hibernate 3.5, 3.6 and 4.0 but that is normal since these Hibernate versions are not supposed to work with JPA versions above 2.0. I think however that the usability should be better and not just throw an exception in the user's face. Are you sure that this does not work with Hibernate 4.3? > Cannot generate ddl when hibernate console is NOT used > ------------------------------------------------------ > > Key: JBIDE-19535 > URL: https://issues.jboss.org/browse/JBIDE-19535 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.3.Beta1 > Environment: JBDS 8.1.0.GA > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Critical > Fix For: 4.3.0.Beta1 > > > Cannot generate ddl when hibernate console is NOT used. It actually works when Hibernate 3.5, 3.6, 4.0 is used but not for 4.3. Found by extended automated tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19256) Autocomplete shows white on white using default RHEL7 theme

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19256?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19256. ------------------------------- Verified with JBDS 9.0.0.Alpha2 > Autocomplete shows white on white using default RHEL7 theme > ----------------------------------------------------------- > > Key: JBIDE-19256 > URL: https://issues.jboss.org/browse/JBIDE-19256 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Affects Versions: 4.2.0.Final > Environment: JBDS 8.0.0, RHEL 7 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.3.0.Alpha1 > > > I can't see code completion in Eclipse while using default Adawaita theme in RHEL7. See attached screenshot > Tracked in upstream by https://bugs.eclipse.org/bugs/show_bug.cgi?id=439884 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19759) Application wizard: cannot launch v3 application wizard via File->New->OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19759?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19759: ------------------------------------- Attachment: empty-v2-wizard-page.png > Application wizard: cannot launch v3 application wizard via File->New->OpenShift > -------------------------------------------------------------------------------- > > Key: JBIDE-19759 > URL: https://issues.jboss.org/browse/JBIDE-19759 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > Attachments: empty-v2-wizard-page.png > > > If you launch the application wizard via File->New->OpenShift you can only create OpenShift v2 applications. I should get v3 pages if I select a v3 connection in the 1st wizard page with the connection credentials. Currently if I select a v2 connection I can create v2 applications. If I select a v3 connection the wizard is non-functional. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19759) Application wizard: cannot launch v3 application wizard via File->New->OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19759?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19759: ------------------------------------- Steps to Reproduce: # EXEC: launch application wizard via File->New->OpenShift->OpenShift application # ASSERT: connection page shows up # EXEC: use an existing/create a new OpenShift v3 connetion and hit "Next" Result: !empty-v2-wizard-page.png! upcoming page is a v2 page and is all blank (which is expected and no errors) Expected result: upcoming page should be a v3 page that allows me to create a v3 project was: # EXEC: launch application wizard via File->New->OpenShift->OpenShift application # ASSERT: connection page shows up # EXEC: use an existing/create a new OpenShift v3 connetion and hit "Next" # ASSERT: upcoming > Application wizard: cannot launch v3 application wizard via File->New->OpenShift > -------------------------------------------------------------------------------- > > Key: JBIDE-19759 > URL: https://issues.jboss.org/browse/JBIDE-19759 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > > If you launch the application wizard via File->New->OpenShift you can only create OpenShift v2 applications. I should get v3 pages if I select a v3 connection in the 1st wizard page with the connection credentials. Currently if I select a v2 connection I can create v2 applications. If I select a v3 connection the wizard is non-functional. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19759) Application wizard: cannot launch v3 application wizard via File->New->OpenShift

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-19759: ---------------------------------------- Summary: Application wizard: cannot launch v3 application wizard via File->New->OpenShift Key: JBIDE-19759 URL: https://issues.jboss.org/browse/JBIDE-19759 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Andre Dietisheim Fix For: 4.3.0.Beta1 If you launch the application wizard via File->New->OpenShift you can only create OpenShift v2 applications. I should get v3 pages if I select a v3 connection in the 1st wizard page with the connection credentials. Currently if I select a v2 connection I can create v2 applications. If I select a v3 connection the wizard is non-functional. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 2015