[
https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12900559#action_12900559
]
Michelle Caisse commented on JDO-647:
-------------------------------------
api test fails when running tests with maven2 (mvn clean compile test; OR maven
clean build; mvn test). Test failure occurs with both original pom.xml and new
pom.xml attached to this issue.
-------------------------------------------------------------------------------
Test set: javax.jdo.JDOHelperTest
-------------------------------------------------------------------------------
Tests run: 35, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.023 sec <<<
FAILURE!
testGetPMFNullResource(javax.jdo.JDOHelperTest) Time elapsed: 0.005 sec <<<
FAILURE!
junit.framework.AssertionFailedError: Null resource name should result in
JDOFatalUserException
at junit.framework.Assert.fail(Assert.java:47)
at
javax.jdo.JDOHelperTest.testGetPMFNullResource(JDOHelperTest.java:199)
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
1,1 All
> Run TCK using Maven2 for consistency
> ------------------------------------
>
> Key: JDO-647
> URL: https://issues.apache.org/jira/browse/JDO-647
> Project: JDO
> Issue Type: Improvement
> Components: tck
> Affects Versions: JDO 3
> Reporter: Andy Jefferson
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1
>
> Attachments: api_pom.diff, pom.xml, pom.xml
>
>
> Since api2 now builds using Maven2 it makes a heck of a lot of sense to
> build/run the TCK using that too. It also means that the DataNucleus M1 repo
> (which only exists for use of this TCK) can be deleted. Please consider
> upgrading to Maven2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
