[
https://issues.jboss.org/browse/JBIDE-12343?page=com.atlassian.jira.plugi...
]
Dmitry Geraskov resolved JBIDE-12343.
-------------------------------------
Resolution: Done
Now instead of JpaProject build we check if the JpaFacet installed and get properties we
are interested in through JptJpaPlugin (it uses persitent properties for them, so also
don't need project to be build).
JPA: Wrong message "Project must be a JPA project"
--------------------------------------------------
Key: JBIDE-12343
URL:
https://issues.jboss.org/browse/JBIDE-12343
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.Final
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Priority: Critical
Labels: regression
Fix For: 3.4.0.M1
This message appears even for projects which actually JPA. It could signal about wrong
mechanism which we use to get JPAProject instance.
Test case:
1. Create JPAProject with Hibernate platform
2. Double click on it ConsoleConfiguration
FAILURE: wrong message appears
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira