[ https://issues.apache.org/jira/browse/OPENJPA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignacio Andreu updated OPENJPA-283:
-----------------------------------
Attachment: OpenJPA-283.patch
I add the patch to solve the problem
> Build not successful executing mvn package
> ------------------------------------------
>
> Key: OPENJPA-283
> URL: https://issues.apache.org/jira/browse/OPENJPA-283
> Project: OpenJPA
> Issue Type: Bug
> Components: build / infrastructure
> Environment: Mac OS X 10.4.9, Java 1.5.0_06-64, Maven 2.0.6
> Reporter: Ignacio Andreu
> Attachments: OpenJPA-283.patch
>
>
> Running the "mvn package" into the Apache OpenJPA project I found an error, the stack
error is the next:
> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.491 sec <<<
FAILURE!
> testEMClose(org.apache.openjpa.persistence.relations.TestLRS) Time elapsed: 0.083 sec
<<< FAILURE!
> junit.framework.AssertionFailedError: expected:<3> but was:<6>
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.failNotEquals(Assert.java:282)
> at junit.framework.Assert.assertEquals(Assert.java:64)
> at junit.framework.Assert.assertEquals(Assert.java:201)
> at junit.framework.Assert.assertEquals(Assert.java:207)
> at org.apache.openjpa.persistence.relations.TestLRS.assertLRS(TestLRS.java:92)
> at org.apache.openjpa.persistence.relations.TestLRS.testEMClose(TestLRS.java:72)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at junit.framework.TestCase.runTest(TestCase.java:154)
> at junit.framework.TestCase.runBare(TestCase.java:127)
> 0 test INFO [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 0 test INFO [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the database to
attempt to determine what type of database dictionary to use. To prevent this connection
in the future, set your openjpa.jdbc.DBDictionary configuration property to the appropriate
value for your database (see the documentation for available values).
> 2 test INFO [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary"
(Apache Derby 10.2.2.0 - (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:118)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:210)
> at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:135)
> at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:122)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225)
> at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747)
> Running org.apache.openjpa.conf.TestBadAutoDetachProperty
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.069 sec, Cle,,,,
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|