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 Michael Bouschen <mi...@akquinet.de> on 2013/04/04 22:16:41 UTC

JDO TCK Conference Call Friday April 5, 9 am Pacific Daylight Time

Hi,

We will have our regular meeting Friday, April 5 at 9 am Pacific 
Daylight Time (PDT) to discuss JDO TCK issues and status.

Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)

To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#

Agenda:
1. Query method Date.getDay: should JDO support Date.getDate instead?
2. News on JDO-717 "copyjdorijars does not cleanup target directory" 
https://issues.apache.org/jira/browse/JDO-717
3. News on JDO-678 "Ability to set properties on PersistenceManager" 
https://issues.apache.org/jira/browse/JDO-678
4. News on spec update?
5. Other issues

Action Items from weeks past:
[Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 
about JDOHelper methods. In process.
[Aug 17 2012] AI Craig comment on JIRA JDO-589 Autocommit or 
nontransactional action
[Sep 23 2011] AI Michael document when changing dependencies (to 
DataNucleus) it's necessary to rebuild the exectck project before 
running tck.

Regards Michael
-- 
*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
Web: www.akquinet.de <http://www.akquinet.de>

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

Re: Minutes: JDO TCK Conference Call Friday April 5, 9 am Pacific Daylight Time

Posted by Michael Bouschen <mi...@akquinet.de>.
Hi,
> [...]
>
> 5. Other issues
>
> While looking at JDO-678, it was necessary to access the nightly repository for datanucleus. We can change the pom in the copyjdorijars project to include the datanucleus repository where nightly snapshots are found. This will make it easier in future to use datanucleus snapshots. Since snapshots are only updated by mvn once in a while, and users can explicitly request snapshots to be loaded via mvn -U option, and datanucleus is the JDO RI, this change seems useful.

I checked in an update to the copyjdorijar pom.xml adding the 
datanucleus nightly repository.

Regards Michael


-- 
*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
Web: www.akquinet.de <http://www.akquinet.de>

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

Re: Minutes: JDO TCK Conference Call Friday April 5, 9 am Pacific Daylight Time

Posted by Michelle Caisse <mc...@sonic.net>.
This test case is failing consistently for me. I've run it 5 times over 
two days. I'm in GMT - 8, Mountain Standard Time.

-- Michelle

On 4/5/2013 7:10 PM, Craig L Russell wrote:
> ...
>
> a) The test case failure may be a time zone issue. The test case is written so as to use the East Coast time zone (GMT - 5:00). There are intermittent failures running the test with GMT - 8:00. But no failures running GMT + 1. AI Craig code review the test case.
>
>

Minutes: JDO TCK Conference Call Friday April 5, 9 am Pacific Daylight Time

Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell

Agenda:

1. Query method Date.getDay: should JDO support Date.getDate instead?

There are two issues, as Michael noted in his email. 

a) The test case failure may be a time zone issue. The test case is written so as to use the East Coast time zone (GMT - 5:00). There are intermittent failures running the test with GMT - 8:00. But no failures running GMT + 1. AI Craig code review the test case.

b) The other issue is a specification issue. It's clear reading the description of getDay that this is not the api that was intended. It should be changed to getDate instead. This is probably not a backward compatibility issue since the new query api is included in 3.1. 

It may be that we should include the time portion of the birth date and hire date in the test case. AI Michael file a JIRA. 

2. News on JDO-717 "copyjdorijars does not clean up target directory" https://issues.apache.org/jira/browse/JDO-717

no news

3. News on JDO-678 "Ability to set properties on PersistenceManager" https://issues.apache.org/jira/browse/JDO-678

Almost done. Still need to test the case-insensitive setProperty and update the specification to cover the transaction apis.

In the specification, should we enumerate the apis that are equivalent to setProperty or simply note that there are three places where properties and options are described: pmf, pm, and transaction?

4. News on spec update?

See items 1 and 3 above.

5. Other issues

While looking at JDO-678, it was necessary to access the nightly repository for datanucleus. We can change the pom in the copyjdorijars project to include the datanucleus repository where nightly snapshots are found. This will make it easier in future to use datanucleus snapshots. Since snapshots are only updated by mvn once in a while, and users can explicitly request snapshots to be loaded via mvn -U option, and datanucleus is the JDO RI, this change seems useful.

Action Items from weeks past:
[Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about JDOHelper methods. In process.
[Aug 17 2012] AI Craig comment on JIRA JDO-589 Autocommit or nontransactional action
[Sep 23 2011] AI Michael document when changing dependencies (to DataNucleus) it's necessary to rebuild the exectck project before running tck.

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!