-
1. Re: Hibernate Configurations/HQL Editor Not Detecting JPA Configurations
maxandersen Aug 17, 2015 6:42 AM (in response to abrand)Do you have JPA facet enabled on the project ?
That said, I can't think of a reason why we should *require* your project to be JPA to create a console configuration so would be good to know a bit more about what steps you are specifically doing ?
-
2. Re: Hibernate Configurations/HQL Editor Not Detecting JPA Configurations
abrand Aug 17, 2015 9:22 AM (in response to maxandersen)Do you have JPA facet enabled on the project ?
No, JPA facet is not enabled on the project.
That said, I can't think of a reason why we should *require* your project to be JPA to create a console configuration so would be good to know a bit more about what steps you are specifically doing ?
Let me clarify, hibernate tool does not *require* my project to be JPA to create a console configuration -- it does give me the option of using hibernate configuration(s). With that explained, since my project is JPA based I thought it would be easiest/best to use the JPA configurations to setup the console configuration/HQL editor.
In the configuration window, under the "Main" tab, I select "type" of JPA (jdk 1.5+), hibernate version 4.3, my project path, and JPA configured connection, and lastly the persistence unit I want to work with. The combination of these choices results in the error: Project 'myproject' must be a JPA project.
-
3. Re: Hibernate Configurations/HQL Editor Not Detecting JPA Configurations
maxandersen Aug 18, 2015 8:12 AM (in response to abrand)Does it work if you go and enable JPA facet on the project ?
Can you open a jira with this, it definitely does not sound right we should *require* JPA facet on this - if there is a reason the error message should at least explain why/how.