You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by Craig L Russell <cr...@oracle.com> on 2010/07/02 03:35:37 UTC

Please review and test JDO 3.0 staging release

at http://people.apache.org/~clr/dist

You should be able to see and download the JDO 3.0 artifacts that will  
be pushed to mirrors after approval.

After this review, the DB PMC will vote on the release artifacts to be  
published after the JCP process completes July 25.

Reminder: we only widely distribute the api jars, not the tck jars.  
The tck is only available by checking out the svn repository.

Thanks,

Craig

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!


Re: Please review and test JDO 3.0 staging release

Posted by Craig L Russell <cr...@oracle.com>.
Hi Andy,

I've updated the pom with the current version.

Thanks,

Craig

On Jul 2, 2010, at 12:38 AM, Andy Jefferson wrote:

> Hi Craig,
> > at http://people.apache.org/~clr/dist
> http://people.apache.org/~clr/dist/m1-ibiblio-rsync-repository/javax.jdo/poms/jdo-api-3.0.pom
> has
> <currentVersion>${jdo.currentVersion}</currentVersion>
> Ought to be 3.0 in that field
> -- 
> Andy
> DataNucleus (http://www.datanucleus.org)

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!


Re: Please review and test JDO 3.0 staging release

Posted by Andy Jefferson <an...@datanucleus.org>.
Hi Craig,

> at http://people.apache.org/~clr/dist

http://people.apache.org/~clr/dist/m1-ibiblio-rsync-
repository/javax.jdo/poms/jdo-api-3.0.pom

has
<currentVersion>${jdo.currentVersion}</currentVersion>

Ought to be 3.0 in that field


-- 
Andy
DataNucleus (http://www.datanucleus.org)

Re: Please review and test JDO 3.0 staging release

Posted by Matthew Adams <ma...@matthewadams.me>.
After the failure, I changed to the tck directory and did "maven
runtck.jdori" -- everything passed.  Then, I changed back to the root
directory of the trunk and issued the command "maven jdo3.clean jdo3.build"
and everything passed.  Maybe something's not quite initialized on a virgin
machine.  Mine was Mac OS X Snow Leopard w/Java 1.6.0_20 & Maven 1.1.  I'll
try it on a couple of other virgin machines when I get a chance.

-matthew

On Tue, Jul 6, 2010 at 8:23 PM, Michelle Caisse <mc...@sonic.net> wrote:

> I did a clean check-out of the trunk and did "maven jdo3.build".  All tests
> passed.
>
> -- Michelle
>
>
> On 07/06/2010 03:10 PM, Matthew Adams wrote:
>
>> Checked out trunk and built via command "maven jdo3.build" and got the
>> following error in
>> ./tck/target/logs/20100706-122110/derby-dsid-lifecycle-junit.txt:
>>
>> RUN HollowInstanceMaintainsPK.test
>> RUN MultiplePMsReturnInstancesRepresentingSamePC.test
>> RUN NontransactionalWriteThrows.testNontransactionalWriteThrows
>> RUN NontransactionalWriteDatastoreRollback.testDatastoreRollback
>> RUN NontransactionalWriteDatastoreCommit.testDatastoreCommit
>> RUN
>> NontransactionalWriteDatastoreCommitConflict.testDatastoreCommitConflict
>> RUN NontransactionalWriteOptimisticRollback.testOptimisticRollback
>> RUN NontransactionalWriteOptimisticCommit.testOptimisticCommit
>> RUN
>> NontransactionalWriteOptimisticCommitConflict.testOptimisticCommitConflict
>>
>> RUN ObjectIdNotModifiedWhenObjectIdInstanceModified.test
>> RUN PMReturnsIdenticalInstancesForEqualObjIds.test
>> RUN PMsCanSharePCClassesButNotPCInstances.testSharedPC
>> RUN PMsCanSharePCClassesButNotPCInstances.testNonSharedPC       FAILURE
>> RUN StateTransitions.test
>> RUN StateTransitionsReturnedObjects.test
>> RUN TransientTransactionalStateCommit.test
>> RUN TransientTransactionalStateRollback.test
>> Description: All lifecycle tests with standard mapping, no testdata.
>> Time: 005
>> There was 1 failure:
>> 1)
>>
>> testNonSharedPC(org.apache.jdo.tck.lifecycle.PMsCanSharePCClassesButNotPCInstances)junit.framework.AssertionFailedError:
>> Assertions A5.2-1,A5.2-2,A5.2-3 (PMsCanSharePCClassesButNotPCInstances)
>> failed:
>> Uncaught exception junit.framework.AssertionFailedError: Assertions
>> A5.2-1,A5.2-2,A5.2-3 (PMsCanSharePCClassesButNotPCInstances) failed:
>> Wrong number of objects in extent. Inserted=4 Expected=5 in thread
>> Thread[Inserter-0,5,]
>>     at org.apache.jdo.tck.JDO_Test.fail(JDO_Test.java:682)
>>     at
>>
>> org.apache.jdo.tck.lifecycle.PMsCanSharePCClassesButNotPCInstances.insertObjects(PMsCanSharePCClassesButNotPCInstances.java:150)
>>     at
>>
>> org.apache.jdo.tck.lifecycle.PMsCanSharePCClassesButNotPCInstances.testNonSharedPC(PMsCanSharePCClassesButNotPCInstances.java:104)
>>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>     at
>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>     at
>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>     at org.apache.jdo.tck.JDO_Test.runBare(JDO_Test.java:272)
>>     at
>> org.apache.jdo.tck.util.BatchTestRunner.doRun(BatchTestRunner.java:108)
>>     at
>> org.apache.jdo.tck.util.BatchTestRunner.start(BatchTestRunner.java:148)
>>     at
>> org.apache.jdo.tck.util.BatchTestRunner.main(BatchTestRunner.java:123)
>> FAILURES!!!
>> derby-dsid-lifecycle-junit.txt:
>>     ** Tests run: 017, Time: 005 seconds. Failures: 1, Errors: 0
>> Excluded tests: []
>>
>> Did I pick the wrong target?
>>
>> -matthew
>>
>> On Tue, Jul 6, 2010 at 2:28 PM, Michael Bouschen<mb...@spree.de>
>>  wrote:
>>
>>
>>
>>>  Hi Craig,
>>>
>>> I downloaded the sources, built everything from scratch with a clean
>>> local
>>> maven repository and could run the tck with the RI w/o errors/failures.
>>>
>>> Regards Michael
>>>
>>>
>>>
>>>  at http://people.apache.org/~clr/dist<http://people.apache.org/%7Eclr/dist>
>>> <http://people.apache.org/%7Eclr/dist>
>>>
>>>
>>> You should be able to see and download the JDO 3.0 artifacts that will
>>> be pushed to mirrors after approval.
>>>
>>> After this review, the DB PMC will vote on the release artifacts to be
>>> published after the JCP process completes July 25.
>>>
>>> Reminder: we only widely distribute the api jars, not the tck jars.
>>> The tck is only available by checking out the svn repository.
>>>
>>> Thanks,
>>>
>>> Craig
>>>
>>> Craig L Russell
>>> Architect, Oraclehttp://db.apache.org/jdo
>>> 408 276-5638 mailto:Craig.Russell@oracle.com<Cr...@oracle.com>
>>>
>>> P.S. A good JDO? O, Gasp!
>>>
>>>
>>>
>>>
>>>
>>> --
>>> *Michael Bouschen*
>>> *Prokurist*
>>>
>>> akquinet tech@spree GmbH
>>> Bülowstr. 66, D-10783 Berlin
>>>
>>> Fon:   +49 30 235 520-33
>>> Fax:   +49 30 217 520-12
>>> Email: michael.bouschen@akquinet.de
>>> Url:    www.akquinet.de
>>>
>>> akquinet tech@spree GmbH, Berlin
>>> Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
>>> Amtsgericht Berlin-Charlottenburg HRB 86780 B
>>> USt.-Id. Nr.: DE 225 964 680
>>>
>>> --
>>> *Michael Bouschen*
>>> *Prokurist*
>>>
>>> akquinet tech@spree GmbH
>>> Bülowstr. 66, D-10783 Berlin
>>>
>>> Fon:   +49 30 235 520-33
>>> Fax:   +49 30 217 520-12
>>> Email: michael.bouschen@akquinet.de
>>> Url:    www.akquinet.de
>>>
>>> akquinet tech@spree GmbH, Berlin
>>> Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
>>> Amtsgericht Berlin-Charlottenburg HRB 86780 B
>>> USt.-Id. Nr.: DE 225 964 680
>>>
>>>
>>>
>>
>>
>>
>>
>
>


-- 
mailto:matthew@matthewadams.me
skype:matthewadams12
yahoo:matthewadams
aol:matthewadams12
google-talk:matthewadams12@gmail.com<go...@gmail.com>
msn:matthew@matthewadams.me <ms...@matthewadams.me>
http://matthewadams.me
http://www.linkedin.com/in/matthewadams

Re: Please review and test JDO 3.0 staging release

Posted by Michelle Caisse <mc...@sonic.net>.
I did a clean check-out of the trunk and did "maven jdo3.build".  All 
tests passed.

-- Michelle

On 07/06/2010 03:10 PM, Matthew Adams wrote:
> Checked out trunk and built via command "maven jdo3.build" and got the
> following error in
> ./tck/target/logs/20100706-122110/derby-dsid-lifecycle-junit.txt:
>
> RUN HollowInstanceMaintainsPK.test
> RUN MultiplePMsReturnInstancesRepresentingSamePC.test
> RUN NontransactionalWriteThrows.testNontransactionalWriteThrows
> RUN NontransactionalWriteDatastoreRollback.testDatastoreRollback
> RUN NontransactionalWriteDatastoreCommit.testDatastoreCommit
> RUN
> NontransactionalWriteDatastoreCommitConflict.testDatastoreCommitConflict
> RUN NontransactionalWriteOptimisticRollback.testOptimisticRollback
> RUN NontransactionalWriteOptimisticCommit.testOptimisticCommit
> RUN
> NontransactionalWriteOptimisticCommitConflict.testOptimisticCommitConflict
>
> RUN ObjectIdNotModifiedWhenObjectIdInstanceModified.test
> RUN PMReturnsIdenticalInstancesForEqualObjIds.test
> RUN PMsCanSharePCClassesButNotPCInstances.testSharedPC
> RUN PMsCanSharePCClassesButNotPCInstances.testNonSharedPC       FAILURE
> RUN StateTransitions.test
> RUN StateTransitionsReturnedObjects.test
> RUN TransientTransactionalStateCommit.test
> RUN TransientTransactionalStateRollback.test
> Description: All lifecycle tests with standard mapping, no testdata.
> Time: 005
> There was 1 failure:
> 1)
> testNonSharedPC(org.apache.jdo.tck.lifecycle.PMsCanSharePCClassesButNotPCInstances)junit.framework.AssertionFailedError:
> Assertions A5.2-1,A5.2-2,A5.2-3 (PMsCanSharePCClassesButNotPCInstances)
> failed:
> Uncaught exception junit.framework.AssertionFailedError: Assertions
> A5.2-1,A5.2-2,A5.2-3 (PMsCanSharePCClassesButNotPCInstances) failed:
> Wrong number of objects in extent. Inserted=4 Expected=5 in thread
> Thread[Inserter-0,5,]
>      at org.apache.jdo.tck.JDO_Test.fail(JDO_Test.java:682)
>      at
> org.apache.jdo.tck.lifecycle.PMsCanSharePCClassesButNotPCInstances.insertObjects(PMsCanSharePCClassesButNotPCInstances.java:150)
>      at
> org.apache.jdo.tck.lifecycle.PMsCanSharePCClassesButNotPCInstances.testNonSharedPC(PMsCanSharePCClassesButNotPCInstances.java:104)
>      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>      at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>      at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>      at org.apache.jdo.tck.JDO_Test.runBare(JDO_Test.java:272)
>      at
> org.apache.jdo.tck.util.BatchTestRunner.doRun(BatchTestRunner.java:108)
>      at
> org.apache.jdo.tck.util.BatchTestRunner.start(BatchTestRunner.java:148)
>      at
> org.apache.jdo.tck.util.BatchTestRunner.main(BatchTestRunner.java:123)
> FAILURES!!!
> derby-dsid-lifecycle-junit.txt:
>      ** Tests run: 017, Time: 005 seconds. Failures: 1, Errors: 0
> Excluded tests: []
>
> Did I pick the wrong target?
>
> -matthew
>
> On Tue, Jul 6, 2010 at 2:28 PM, Michael Bouschen<mb...@spree.de>  wrote:
>
>    
>>   Hi Craig,
>>
>> I downloaded the sources, built everything from scratch with a clean local
>> maven repository and could run the tck with the RI w/o errors/failures.
>>
>> Regards Michael
>>
>>
>>
>>   at http://people.apache.org/~clr/dist<http://people.apache.org/%7Eclr/dist>
>>
>> You should be able to see and download the JDO 3.0 artifacts that will
>> be pushed to mirrors after approval.
>>
>> After this review, the DB PMC will vote on the release artifacts to be
>> published after the JCP process completes July 25.
>>
>> Reminder: we only widely distribute the api jars, not the tck jars.
>> The tck is only available by checking out the svn repository.
>>
>> Thanks,
>>
>> Craig
>>
>> Craig L Russell
>> Architect, Oraclehttp://db.apache.org/jdo
>> 408 276-5638 mailto:Craig.Russell@oracle.com<Cr...@oracle.com>
>> P.S. A good JDO? O, Gasp!
>>
>>
>>
>>
>>
>> --
>> *Michael Bouschen*
>> *Prokurist*
>>
>> akquinet tech@spree GmbH
>> Bülowstr. 66, D-10783 Berlin
>>
>> Fon:   +49 30 235 520-33
>> Fax:   +49 30 217 520-12
>> Email: michael.bouschen@akquinet.de
>> Url:    www.akquinet.de
>>
>> akquinet tech@spree GmbH, Berlin
>> Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
>> Amtsgericht Berlin-Charlottenburg HRB 86780 B
>> USt.-Id. Nr.: DE 225 964 680
>>
>> --
>> *Michael Bouschen*
>> *Prokurist*
>>
>> akquinet tech@spree GmbH
>> Bülowstr. 66, D-10783 Berlin
>>
>> Fon:   +49 30 235 520-33
>> Fax:   +49 30 217 520-12
>> Email: michael.bouschen@akquinet.de
>> Url:    www.akquinet.de
>>
>> akquinet tech@spree GmbH, Berlin
>> Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
>> Amtsgericht Berlin-Charlottenburg HRB 86780 B
>> USt.-Id. Nr.: DE 225 964 680
>>
>>      
>
>
>    


Re: Please review and test JDO 3.0 staging release

Posted by Craig L Russell <cr...@oracle.com>.
Hi Matthew,

I have never seen this error.

Craig

On Jul 6, 2010, at 3:10 PM, Matthew Adams wrote:

> Checked out trunk and built via command "maven jdo3.build" and got  
> the following error in ./tck/target/logs/20100706-122110/derby-dsid- 
> lifecycle-junit.txt:
>
> RUN HollowInstanceMaintainsPK.test
> RUN MultiplePMsReturnInstancesRepresentingSamePC.test
> RUN NontransactionalWriteThrows.testNontransactionalWriteThrows
> RUN NontransactionalWriteDatastoreRollback.testDatastoreRollback
> RUN NontransactionalWriteDatastoreCommit.testDatastoreCommit
> RUN  
> NontransactionalWriteDatastoreCommitConflict 
> .testDatastoreCommitConflict
> RUN NontransactionalWriteOptimisticRollback.testOptimisticRollback
> RUN NontransactionalWriteOptimisticCommit.testOptimisticCommit
> RUN  
> NontransactionalWriteOptimisticCommitConflict 
> .testOptimisticCommitConflict
> RUN ObjectIdNotModifiedWhenObjectIdInstanceModified.test
> RUN PMReturnsIdenticalInstancesForEqualObjIds.test
> RUN PMsCanSharePCClassesButNotPCInstances.testSharedPC
> RUN PMsCanSharePCClassesButNotPCInstances.testNonSharedPC        
> FAILURE
> RUN StateTransitions.test
> RUN StateTransitionsReturnedObjects.test
> RUN TransientTransactionalStateCommit.test
> RUN TransientTransactionalStateRollback.test
> Description: All lifecycle tests with standard mapping, no testdata.
> Time: 005
> There was 1 failure:
> 1)  
> testNonSharedPC 
> (org 
> .apache 
> .jdo 
> .tck 
> .lifecycle 
> .PMsCanSharePCClassesButNotPCInstances 
> )junit.framework.AssertionFailedError: Assertions  
> A5.2-1,A5.2-2,A5.2-3 (PMsCanSharePCClassesButNotPCInstances) failed:
> Uncaught exception junit.framework.AssertionFailedError: Assertions  
> A5.2-1,A5.2-2,A5.2-3 (PMsCanSharePCClassesButNotPCInstances) failed:
> Wrong number of objects in extent. Inserted=4 Expected=5 in thread  
> Thread[Inserter-0,5,]
>     at org.apache.jdo.tck.JDO_Test.fail(JDO_Test.java:682)
>     at  
> org 
> .apache 
> .jdo 
> .tck 
> .lifecycle 
> .PMsCanSharePCClassesButNotPCInstances 
> .insertObjects(PMsCanSharePCClassesButNotPCInstances.java:150)
>     at  
> org 
> .apache 
> .jdo 
> .tck 
> .lifecycle 
> .PMsCanSharePCClassesButNotPCInstances 
> .testNonSharedPC(PMsCanSharePCClassesButNotPCInstances.java:104)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at  
> sun 
> .reflect 
> .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     at  
> sun 
> .reflect 
> .DelegatingMethodAccessorImpl 
> .invoke(DelegatingMethodAccessorImpl.java:25)
>     at org.apache.jdo.tck.JDO_Test.runBare(JDO_Test.java:272)
>     at  
> org.apache.jdo.tck.util.BatchTestRunner.doRun(BatchTestRunner.java: 
> 108)
>     at  
> org.apache.jdo.tck.util.BatchTestRunner.start(BatchTestRunner.java: 
> 148)
>     at  
> org.apache.jdo.tck.util.BatchTestRunner.main(BatchTestRunner.java:123)
> FAILURES!!!
> derby-dsid-lifecycle-junit.txt:
>     ** Tests run: 017, Time: 005 seconds. Failures: 1, Errors: 0
> Excluded tests: []
>
> Did I pick the wrong target?
>
> -matthew
>
> On Tue, Jul 6, 2010 at 2:28 PM, Michael Bouschen <mb...@spree.de>  
> wrote:
> Hi Craig,
>
> I downloaded the sources, built everything from scratch with a clean  
> local maven repository and could run the tck with the RI w/o errors/ 
> failures.
>
> Regards Michael
>
>
>
>> at http://people.apache.org/~clr/dist
>>
>> You should be able to see and download the JDO 3.0 artifacts that  
>> will
>> be pushed to mirrors after approval.
>>
>> After this review, the DB PMC will vote on the release artifacts to  
>> be
>> published after the JCP process completes July 25.
>>
>> Reminder: we only widely distribute the api jars, not the tck jars.
>> The tck is only available by checking out the svn repository.
>>
>> Thanks,
>>
>> Craig
>>
>> Craig L Russell
>> Architect, Oracle
>> http://db.apache.org/jdo
>> 408 276-5638 mailto:Craig.Russell@oracle.com
>> P.S. A good JDO? O, Gasp!
>>
>>
>
>
> -- 
> Michael Bouschen
> Prokurist
>
> akquinet tech@spree GmbH
> Bülowstr. 66, D-10783 Berlin
>
> Fon:   +49 30 235 520-33
> Fax:   +49 30 217 520-12
> Email: michael.bouschen@akquinet.de
> Url:    www.akquinet.de
>
> akquinet tech@spree GmbH, Berlin
> Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
> Amtsgericht Berlin-Charlottenburg HRB 86780 B
> USt.-Id. Nr.: DE 225 964 680
>
> -- 
> Michael Bouschen
> Prokurist
>
> akquinet tech@spree GmbH
> Bülowstr. 66, D-10783 Berlin
>
> Fon:   +49 30 235 520-33
> Fax:   +49 30 217 520-12
> Email: michael.bouschen@akquinet.de
> Url:    www.akquinet.de
>
> akquinet tech@spree GmbH, Berlin
> Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
> Amtsgericht Berlin-Charlottenburg HRB 86780 B
> USt.-Id. Nr.: DE 225 964 680
>
>
>
> -- 
> mailto:matthew@matthewadams.me
> skype:matthewadams12
> yahoo:matthewadams
> aol:matthewadams12
> google-talk:matthewadams12@gmail.com
> msn:matthew@matthewadams.me
> http://matthewadams.me
> http://www.linkedin.com/in/matthewadams
>

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!


Re: Please review and test JDO 3.0 staging release

Posted by Matthew Adams <ma...@matthewadams.me>.
Checked out trunk and built via command "maven jdo3.build" and got the
following error in
./tck/target/logs/20100706-122110/derby-dsid-lifecycle-junit.txt:

RUN HollowInstanceMaintainsPK.test
RUN MultiplePMsReturnInstancesRepresentingSamePC.test
RUN NontransactionalWriteThrows.testNontransactionalWriteThrows
RUN NontransactionalWriteDatastoreRollback.testDatastoreRollback
RUN NontransactionalWriteDatastoreCommit.testDatastoreCommit
RUN
NontransactionalWriteDatastoreCommitConflict.testDatastoreCommitConflict
RUN NontransactionalWriteOptimisticRollback.testOptimisticRollback
RUN NontransactionalWriteOptimisticCommit.testOptimisticCommit
RUN
NontransactionalWriteOptimisticCommitConflict.testOptimisticCommitConflict

RUN ObjectIdNotModifiedWhenObjectIdInstanceModified.test
RUN PMReturnsIdenticalInstancesForEqualObjIds.test
RUN PMsCanSharePCClassesButNotPCInstances.testSharedPC
RUN PMsCanSharePCClassesButNotPCInstances.testNonSharedPC       FAILURE
RUN StateTransitions.test
RUN StateTransitionsReturnedObjects.test
RUN TransientTransactionalStateCommit.test
RUN TransientTransactionalStateRollback.test
Description: All lifecycle tests with standard mapping, no testdata.
Time: 005
There was 1 failure:
1)
testNonSharedPC(org.apache.jdo.tck.lifecycle.PMsCanSharePCClassesButNotPCInstances)junit.framework.AssertionFailedError:
Assertions A5.2-1,A5.2-2,A5.2-3 (PMsCanSharePCClassesButNotPCInstances)
failed:
Uncaught exception junit.framework.AssertionFailedError: Assertions
A5.2-1,A5.2-2,A5.2-3 (PMsCanSharePCClassesButNotPCInstances) failed:
Wrong number of objects in extent. Inserted=4 Expected=5 in thread
Thread[Inserter-0,5,]
    at org.apache.jdo.tck.JDO_Test.fail(JDO_Test.java:682)
    at
org.apache.jdo.tck.lifecycle.PMsCanSharePCClassesButNotPCInstances.insertObjects(PMsCanSharePCClassesButNotPCInstances.java:150)
    at
org.apache.jdo.tck.lifecycle.PMsCanSharePCClassesButNotPCInstances.testNonSharedPC(PMsCanSharePCClassesButNotPCInstances.java:104)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at org.apache.jdo.tck.JDO_Test.runBare(JDO_Test.java:272)
    at
org.apache.jdo.tck.util.BatchTestRunner.doRun(BatchTestRunner.java:108)
    at
org.apache.jdo.tck.util.BatchTestRunner.start(BatchTestRunner.java:148)
    at
org.apache.jdo.tck.util.BatchTestRunner.main(BatchTestRunner.java:123)
FAILURES!!!
derby-dsid-lifecycle-junit.txt:
    ** Tests run: 017, Time: 005 seconds. Failures: 1, Errors: 0
Excluded tests: []

Did I pick the wrong target?

-matthew

On Tue, Jul 6, 2010 at 2:28 PM, Michael Bouschen <mb...@spree.de> wrote:

>  Hi Craig,
>
> I downloaded the sources, built everything from scratch with a clean local
> maven repository and could run the tck with the RI w/o errors/failures.
>
> Regards Michael
>
>
>
>  at http://people.apache.org/~clr/dist <http://people.apache.org/%7Eclr/dist>
>
> You should be able to see and download the JDO 3.0 artifacts that will
> be pushed to mirrors after approval.
>
> After this review, the DB PMC will vote on the release artifacts to be
> published after the JCP process completes July 25.
>
> Reminder: we only widely distribute the api jars, not the tck jars.
> The tck is only available by checking out the svn repository.
>
> Thanks,
>
> Craig
>
> Craig L Russell
> Architect, Oraclehttp://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@oracle.com <Cr...@oracle.com>
> P.S. A good JDO? O, Gasp!
>
>
>
>
>
> --
> *Michael Bouschen*
> *Prokurist*
>
> akquinet tech@spree GmbH
> Bülowstr. 66, D-10783 Berlin
>
> Fon:   +49 30 235 520-33
> Fax:   +49 30 217 520-12
> Email: michael.bouschen@akquinet.de
> Url:    www.akquinet.de
>
> akquinet tech@spree GmbH, Berlin
> Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
> Amtsgericht Berlin-Charlottenburg HRB 86780 B
> USt.-Id. Nr.: DE 225 964 680
>
> --
> *Michael Bouschen*
> *Prokurist*
>
> akquinet tech@spree GmbH
> Bülowstr. 66, D-10783 Berlin
>
> Fon:   +49 30 235 520-33
> Fax:   +49 30 217 520-12
> Email: michael.bouschen@akquinet.de
> Url:    www.akquinet.de
>
> akquinet tech@spree GmbH, Berlin
> Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
> Amtsgericht Berlin-Charlottenburg HRB 86780 B
> USt.-Id. Nr.: DE 225 964 680
>



-- 
mailto:matthew@matthewadams.me
skype:matthewadams12
yahoo:matthewadams
aol:matthewadams12
google-talk:matthewadams12@gmail.com<go...@gmail.com>
msn:matthew@matthewadams.me <ms...@matthewadams.me>
http://matthewadams.me
http://www.linkedin.com/in/matthewadams

Re: Please review and test JDO 3.0 staging release

Posted by Michelle Caisse <mc...@sonic.net>.
I downloaded the tck, modified my jdo-tck-3.0/project.properties with 
the repository name

maven.repo.remote =\
http://people.apache.org/~clr/dist/m1-ibiblio-rsync-repository,\
...

and did maven build. All tests passed.

-- Michelle

On 07/06/2010 02:28 PM, Michael Bouschen wrote:
> Hi Craig,
>
> I downloaded the sources, built everything from scratch with a clean 
> local maven repository and could run the tck with the RI w/o 
> errors/failures.
>
> Regards Michael
>
>
>> at http://people.apache.org/~clr/dist
>>
>> You should be able to see and download the JDO 3.0 artifacts that 
>> will  be pushed to mirrors after approval.
>>
>> After this review, the DB PMC will vote on the release artifacts to 
>> be  published after the JCP process completes July 25.
>>
>> Reminder: we only widely distribute the api jars, not the tck jars.  
>> The tck is only available by checking out the svn repository.
>>
>> Thanks,
>>
>> Craig
>>
>> Craig L Russell
>> Architect, Oracle
>> http://db.apache.org/jdo
>> 408 276-5638 mailto:Craig.Russell@oracle.com
>> P.S. A good JDO? O, Gasp!
>>
>
>


Re: Please review and test JDO 3.0 staging release

Posted by Michael Bouschen <mb...@spree.de>.
Hi Craig,

I downloaded the sources, built everything from scratch with a clean 
local maven repository and could run the tck with the RI w/o 
errors/failures.

Regards Michael


> at http://people.apache.org/~clr/dist
>
> You should be able to see and download the JDO 3.0 artifacts that will  
> be pushed to mirrors after approval.
>
> After this review, the DB PMC will vote on the release artifacts to be  
> published after the JCP process completes July 25.
>
> Reminder: we only widely distribute the api jars, not the tck jars.  
> The tck is only available by checking out the svn repository.
>
> Thanks,
>
> Craig
>
> Craig L Russell
> Architect, Oracle
> http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@oracle.com
> P.S. A good JDO? O, Gasp!
>
>   


-- 
*Michael Bouschen*
*Prokurist*

akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin

Fon:   +49 30 235 520-33
Fax:   +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url:    www.akquinet.de <http://www.akquinet.de>

akquinet tech@spree GmbH, Berlin
Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
Amtsgericht Berlin-Charlottenburg HRB 86780 B
USt.-Id. Nr.: DE 225 964 680

-- 
*Michael Bouschen*
*Prokurist*

akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin

Fon:   +49 30 235 520-33
Fax:   +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url:    www.akquinet.de <http://www.akquinet.de>

akquinet tech@spree GmbH, Berlin
Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
Amtsgericht Berlin-Charlottenburg HRB 86780 B
USt.-Id. Nr.: DE 225 964 680