Description of problem: deltaspike-beanbuilder and kitchensink-deltaspike quickstarts show a warning (JPA problem) when imported in JBDS 7: "No connection specified for project. No database-specific validation will be performed." Version-Release number of selected component (if applicable): WFK 2.3.0.CR2 JBDS 7.0.0.Beta2b How reproducible: Import the quickstarts into JBDS. Actual results: Warning is shown: "No connection specified for project. No database-specific validation will be performed." Expected results: ? (This warning provides only very little valuable information, and might drown out other more valuable warnings. Not sure what's the "expected result".) Additional info: In deltaspike-beanmanagerprovider, this was resolved by adding <m2e.jpa.activation>false</m2e.jpa.activation> to the pom.xml, which disables the JPA facet of the project altogether. IMHO it's not reasonable to disable the JPA facet just to get rid of a warning. The JPA facet might still be useful. It would be more appropriate to maybe document the behaviour in README and leave the "<m2e.jpa.activation>false</m2e.jpa.activation>" in pom.xml, commented out, with a note about what it does.