This content has been marked as final.
Show 3 replies
-
1. Re: Persistence metadata change
alrubinger May 27, 2008 4:30 AM (in response to alesj)"alesj" wrote:
For a simple test, to see if things at least work, I ran ALR's service-test.jar.
Let's try running with one of the JPA tests, anything from the EJB3 Core TestSuite under the "entity" heading should do.
S,
ALR -
2. Re: Persistence metadata change
alesj May 27, 2008 4:47 AM (in response to alesj)"ALRubinger" wrote:
Let's try running with one of the JPA tests, anything from the EJB3 Core TestSuite under the "entity" heading should do.
In AS5 testsuite?
Or EJB3 project testsuite?
If 2nd, shouldn't this be part of 'mvn install'?
I ran that, catching any FAILURE text, ... nothing there.
It's not really a business logic change/update.
The relevant tests for this are probably the one's in metadata, which test if PMD is capable of mapping to the actual persistence.xml file. -
3. Re: Persistence metadata change
alrubinger May 27, 2008 4:52 AM (in response to alesj)EJB3 Project TestSuite.
"mvn install" should execute quickly, and we're using it for all of our Unit Tests. The TestSuite I mention is more of an integration suite, and takes about 90 minutes to run fully. So you see why we exclude it by default. :)
If the metadata tests cover the change, that's good enough for me. Carlo will have different opinions as he'd like to verify jboss-metadata results in EJB3 (to ensure that we're consuming a valid component).
S,
ALR