Eclipse detects new projects as JPA projects
rdwallis opened this issue · 6 comments
Causes missing persistence.xml errors.
Partial work around:
Create an empty persistence.xml file in src/main/resources/META-INF
Delete the persistence.xml file from src/main/java/META-INF
Oops, wrong project. I've notice GPE doing this in Eclipse.
Haha no worries. Will blame this on GPE anyway :)
I think this could be fixed upstream. I've already added some better detection logic for the jpa path when using maven.
Oh good do you have an eta on release? Or should I update the gwtp templates to include the empty persistence.xml file?
Might want to try the preview release, I did add a gatekeeper, if the jdo-jpa artifact doesn't get added to the pom.xml, then the jpa/jdo builder is removed and jpa facet turned off.
Ok just checked and I added an empty persistence.xml file to the gwtp
project template a while ago to fix the JPA problem. Might be causing
issues now if that problem has been fixed.
On Mon, May 11, 2015 at 8:23 PM, Brandon Donnelson <notifications@github.com
wrote:
Might want to try the preview release, I did add a gatekeeper, if the
jdo-jpa artifact doesn't get added to the pom.xml, then the jpa/jdo builder
is removed and jpa facet turned off.—
Reply to this email directly or view it on GitHub
#114 (comment)
.