Bug 980900 - deltaspike-beanbuilder and kitchensink-deltaspike show JPA warning in JBDS 7
deltaspike-beanbuilder and kitchensink-deltaspike show JPA warning in JBDS 7
Status: CLOSED INSUFFICIENT_DATA
Product: JBoss Enterprise WFK Platform 2
Classification: JBoss
Component: DeltaSpike (Show other bugs)
2.3.0
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Jason Porter
Ron Šmeral
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-03 09:23 EDT by Ron Šmeral
Modified: 2016-10-31 21:37 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-08-09 09:17:34 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker WFK2-142 Minor Closed deltaspike-beanbuilder and kitchensink-deltaspike show JPA warning in JBDS 7 2014-08-25 07:41:27 EDT

  None (edit)
Description Ron Šmeral 2013-07-03 09:23:06 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.