[jbosstools-issues] [JBoss JIRA] (JBIDE-22811) Dont log exception when getting hibernate version

[Rastislav Wagner (JIRA)]

Rastislav Wagner created JBIDE-22811:
----------------------------------------

             Summary: Dont log exception when getting hibernate version
                 Key: JBIDE-22811
                 URL: https://issues.jboss.org/browse/JBIDE-22811
             Project: Tools (JBoss Tools)
          Issue Type: Enhancement
          Components: hibernate
    Affects Versions: 4.4.1.AM2
            Reporter: Rastislav Wagner
             Fix For: 4.4.1.AM3


This is a follow up on JBIDE-21769

Create JPA project and set Platform to Hibernate, JPA implementation to Disable library Configuration.
When you open Hibernate Configrations view an exception is logged in error log

{code}
java.lang.NullPointerException
	at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.lookupHibernateVersion(JPAPostInstallFasetListener.java:222)
	at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.buildConsoleConfiguration(JPAPostInstallFasetListener.java:182)
	at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.handleEvent(JPAPostInstallFasetListener.java:79)
	at org.eclipse.wst.common.project.facet.core.events.internal.DelayedClassLoadingListener.handleEvent(DelayedClassLoadingListener.java:62)
	at org.eclipse.wst.common.project.facet.core.events.internal.ProjectListenerRegistry.notifyListeners(ProjectListenerRegistry.java:76)
	at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.notifyListeners(FacetedProject.java:1327)
	at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:454)
	at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181)
	at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117)
	at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$5.run(FacetedProject.java:1099)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
	at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChanges(FacetedProject.java:1109)
	at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.commitChanges(FacetedProjectWorkingCopy.java:2020)
	at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard.performFinish(ModifyFacetedProjectWizard.java:400)
	at org.eclipse.wst.web.ui.internal.wizards.NewProjectDataModelFacetWizard.performFinish(NewProjectDataModelFacetWizard.java:282)
	at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$3.run(ModifyFacetedProjectWizard.java:331)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
	at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$4.run(ModifyFacetedProjectWizard.java:345)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)

{code}

I dont think its necessary to log it.
 - nothing went wrong, JPA project just doesnt specify hibernate version
 - AERI kicks in and user might think this is an actual bug in code



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)