May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21512) Enable hibernate-search by default (set hibernate.search.autoregister_listeners to true)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21512?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21512: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Enable hibernate-search by default (set hibernate.search.autoregister_listeners to true) > ---------------------------------------------------------------------------------------- > > Key: JBIDE-21512 > URL: https://issues.jboss.org/browse/JBIDE-21512 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 4.3.x > Reporter: Dmitry Bocharov > Assignee: Koen Aers > Priority: Optional > Fix For: 4.4.0.Alpha2 > > > The _hibernate.search.autoregister_listeners_ property was set to _false _by default in [ConfigurationFactory] (https://github.com/jbosstools/jbosstools-hibernate/blob/12928b28d3769b266...), if not set to true by use in xml configuration. > The reason is descibed in the comments some lines above. I also linked the appropriate JIRAs. > The idea is to set this property to _true _, because in order to use the curently being created [hibernate-search plugin] (https://github.com/bdshadow/org.jboss.tools.hibernate.search) the user has to set it to true in the configuration, while this property isn't obligatory by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21766) NPE when trying to generate mapping files on project with no console config

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21766?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21766: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > NPE when trying to generate mapping files on project with no console config > --------------------------------------------------------------------------- > > Key: JBIDE-21766 > URL: https://issues.jboss.org/browse/JBIDE-21766 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Rastislav Wagner > Assignee: Koen Aers > Fix For: 4.4.0.Alpha2 > > > {code} > java.lang.NullPointerException > at org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor.getService(ConfigurationActor.java:127) > at org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor.createConfiguration(ConfigurationActor.java:134) > at org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor.createConfigurations(ConfigurationActor.java:117) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.createConfigurations(NewHibernateMappingFileWizard.java:559) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.getPlaces2Gen(NewHibernateMappingFileWizard.java:316) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.handlePageChanging(NewHibernateMappingFileWizard.java:172) > at org.eclipse.jface.wizard.WizardDialog$10.run(WizardDialog.java:1554) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.wizard.WizardDialog.firePageChanging(WizardDialog.java:1551) > at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:899) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1186) > at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:885) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:425) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > 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: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.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:160) > 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: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) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21769) Default hibernate configuration is set to 4.3 - should be 5.0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21769?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21769: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Default hibernate configuration is set to 4.3 - should be 5.0 > ------------------------------------------------------------- > > Key: JBIDE-21769 > URL: https://issues.jboss.org/browse/JBIDE-21769 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Rastislav Wagner > Assignee: Koen Aers > Fix For: 4.4.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21745) Unable to download EAP 7 Beta runtime using username without "@redhat.com"

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21745?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21745: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Unable to download EAP 7 Beta runtime using username without "@redhat.com" > -------------------------------------------------------------------------- > > Key: JBIDE-21745 > URL: https://issues.jboss.org/browse/JBIDE-21745 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Final, 4.3.1.CR1 > Environment: JBDS 9.1.0.CR1, JBDS 9.0.0.GA > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > Trying to download EAP 7 Beta using login without "@redhat.com" fails on license agreement page. > Instead of license agreement being displayed, just message saying "It is no longer possible to accept terms and conditions in the wizard. Please, use following link instead!" is shown. Given link redirects to Red Hat Developers portal login. After successful login, message is shown: > {noformat} > You Entered All Necessary Information > Thank you for filling all necessary information. Now you can go back to Eclipse and retry your download of /jboss-eap-7.0.0.Beta.zip. > {noformat} > But even after that I'm unable to download that runtime with the same credentials. > Using login with "@redhat.com" I'm able to download the runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21743) no declaration can be found for element "context:component-scan" in spring-kitchensink-basic quickstart

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21743?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21743: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > no declaration can be found for element "context:component-scan" in spring-kitchensink-basic quickstart > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21743 > URL: https://issues.jboss.org/browse/JBIDE-21743 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: project-examples > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha2 > > > Importing "spring-kitchensink-basic" EAP7 quickstart raises an error: > {noformat}Description Resource Path Location Type > cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'context:component-scan'. jboss-as-spring-mvc-context.xml /jboss-spring-kitchensink-basic/src/main/webapp/WEB-INF line 26 XML Problem > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22176) [thym] Implement Engines Management in config.xml editor

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22176?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22176: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > [thym] Implement Engines Management in config.xml editor > -------------------------------------------------------- > > Key: JBIDE-22176 > URL: https://issues.jboss.org/browse/JBIDE-22176 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Fix For: 4.4.0.Alpha2 > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=491580 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22175) Warnings in JBDS after importing kitchensink-jsp quickstart

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22175?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22175: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Warnings in JBDS after importing kitchensink-jsp quickstart > ----------------------------------------------------------- > > Key: JBIDE-22175 > URL: https://issues.jboss.org/browse/JBIDE-22175 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, upstream > Reporter: Sande Gilda > Assignee: Victor Rubezhny > Fix For: 4.4.0.Alpha2 > > > After importing the quickstart into JBDS, the following warnings are produced > * The tag handler class for "c:forEach" (org.apache.taglibs.standard.tag.rt.core.ForEachTag) was not found on the Java Build Path > * The tag handler class for "c:out" (org.apache.taglibs.standard.tag.rt.core.OutTag) was not found on the Java Build Path -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22173) write validation tests to ensure published content has been correctly published

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22173?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22173: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > write validation tests to ensure published content has been correctly published > ------------------------------------------------------------------------------- > > Key: JBIDE-22173 > URL: https://issues.jboss.org/browse/JBIDE-22173 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, install-tests > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Fix For: 4.4.0.Alpha2 > > > Once we're done running stage.sh, we need a way to automatically review the content has been correctly published. > Today, we do this: > {code} > versionWithRespin=4.3.1.CR1b # a, b, c... > tmpfile=/tmp/jbosstools-staging__verify.txt > for site in site coretests-site central-site earlyaccess-site discovery.central discovery.earlyaccess; do > if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi > echo "http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-${ver... " >> $tmpfile > echo "http://download.jboss.org/jbosstools/mars/staging/updates/${sitename}/${v... " >> $tmpfile > done > for site in browsersim-standalone; do > if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi > echo "http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-${ver... " >> $tmpfile > done > echo "" >> $tmpfile > cat $tmpfile > firefox `cat $tmpfile` > rm -fr $tmpfile > # verify changes > echo "Check 6 URLs:" > firefox \ > http://download.jboss.org/jbosstools/mars/staging/updates/discovery.centr... \ > http://download.jboss.org/jbosstools/mars/staging/updates/discovery.early... \ > http://download.jboss.org/jbosstools/mars/staging/updates/compositeConten... \ > http://download.jboss.org/jbosstools/mars/staging/updates/core/compositeC... \ > http://download.jboss.org/jbosstools/mars/staging/updates/core/ \ > http://download.jboss.org/jbosstools/mars/staging/updates/ > {code} > or > {code} > versionWithRespin=9.1.0.CR1b # a, b, c... > tmpfile=/tmp/jbosstools-staging__verify.txt > for site in central earlyaccess discovery.central discovery.earlyaccess; do > if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi > echo "https://devstudio.redhat.com/9.0/staging/builds/devstudio-${versionWithRe... " >> $tmpfile > echo "https://devstudio.redhat.com/9.0/staging/updates/${sitename}/${versionWit... " >> $tmpfile > done > echo "https://devstudio.redhat.com/9.0/staging/builds/devstudio-${versionWithRe... " >> $tmpfile > echo "http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-${vers... " >> $tmpfile > echo "https://devstudio.redhat.com/9.0/staging/builds/#_____(5_folders_w/_${ver... " >> $tmpfile > echo "https://devstudio.redhat.com/9.0/staging/updates/core/#_____(6_zips,_6_su... " >> $tmpfile > echo "" >> $tmpfile > cat $tmpfile > firefox `cat $tmpfile` > popd >/dev/null > rm -fr $tmpfile > # verify changes > echo "Check 4 URLs:" > firefox \ > https://devstudio.redhat.com/9.0/staging/updates/discovery.central/${vers... \ > https://devstudio.redhat.com/9.0/staging/updates/discovery.earlyaccess/${... \ > https://devstudio.redhat.com/9.0/staging/updates/compositeContent.xml \ > https://devstudio.redhat.com/9.0/staging/updates/ > {code} > But ideally we could fetch those pages via curl and sed to check if the content we expect has been correctly published. > Need to pseudocode the rules to verify, then figure out how to sed/grep the html to ensure what we need is present. > May also need to forgive gently -- try again 3 times at 2 min intervals before raising an alarm. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22168) Solve the test problems on Windows

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22168?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22168: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Solve the test problems on Windows > ---------------------------------- > > Key: JBIDE-22168 > URL: https://issues.jboss.org/browse/JBIDE-22168 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Fix For: 4.4.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22108) xcodeproj is shown as a directory in Project Explorer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22108?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22108: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > xcodeproj is shown as a directory in Project Explorer > ----------------------------------------------------- > > Key: JBIDE-22108 > URL: https://issues.jboss.org/browse/JBIDE-22108 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Fix For: 4.4.0.Alpha2 > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=491074 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016