[
https://issues.apache.org/jira/browse/JDO-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-557:
Attachment: jdo-557.patch
First two tests work; third (passing props to JDOHelper.getPMF()) fails
[
https://issues.apache.org/jira/browse/JDO-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-557:
Attachment: (was: jdo-557.patch)
Create tests in api2 api2-legacy for JDO implementation's
Hi,
We will have our regular meeting Friday, May 28 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 06916106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2.
2. Extra checks in PMF.close tests
https://issues.apache.org/jira/browse/JDO-653: Are the observed
failures violations of the spec? (11.4 Close the
PersistenceManagerFactory)
Michelle will verify these changes.
I'm not clear what else is needed here. I verified that there are RI
failures
Hi,
We will have our regular meeting Friday, May 20 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 06916106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2.
[
https://issues.apache.org/jira/browse/JDO-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868969#action_12868969
]
Michelle Caisse commented on JDO-653:
-
After applying the second patch, I get three test
Hi,
We will have our regular meeting Friday, May 14 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 06916106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2.
:
On 04/04/2010 05:56 AM, Michelle Caisse wrote:
Hi all,
For JDO-557 (api tests for JDOHelper calls to
PersistenceManagerFactory(Map, Map), I've been trying to to set up a
ClassLoader that has both the test classes in it (so the proxy class
returning a pmf can be found) and jdoconfig.xml. I have
Hi all,
For JDO-557 (api tests for JDOHelper calls to
PersistenceManagerFactory(Map, Map), I've been trying to to set up a
ClassLoader that has both the test classes in it (so the proxy class
returning a pmf can be found) and jdoconfig.xml. I have not found a way
to programmatically, during
[
https://issues.apache.org/jira/browse/JDO-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-557:
Attachment: (was: jdo-557.patch)
Create tests in api2 api2-legacy for JDO implementation's
Hi,
Please note :
- The U.S. has switched to Daylight Saving Time..
We will have our regular meeting Friday, March 26 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code :
[
https://issues.apache.org/jira/browse/JDO-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-557:
Attachment: jdo-557.patch
Attached draft work for this issue containing three new files, along
Hi,
Please note :
- This week's meeting is temporarily at a different time AND
- The U.S. has switched to Daylight Saving Time..
We will have our regular meeting Friday, March 12 at 11 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
Craig L Russell wrote:
The behead script that removes the first several lines from
annotations and enums doesn't work for regular classes and interfaces.
It would be nice if the script could also support classes and interfaces.
I've checked in a new version that supports any .java file with a
Hi,
We will have our regular meeting Friday, March 12 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Query Cancel TCK tests
2. Tests in api2 for ...
[
https://issues.apache.org/jira/browse/JDO-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842527#action_12842527
]
Michelle Caisse commented on JDO-557:
-
I'm not clear how we can use a dynamic proxy
Hi,
We will have our regular meeting Friday, February 26 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Create tests ... for JDO implementation's
Hi,
We will have our regular meeting Friday, February 19 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Create tests ... for JDO implementation's
Hi,
We will have our regular meeting Friday, January 15 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Support specification of exact class in
Hi,
We will have our regular meeting Friday, December 18 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Query timeout in JDO / Update timeout
2.
Hi,
We will have our regular meeting Friday, December 11 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Query timeout in JDO / Update timeout - Done
[
https://issues.apache.org/jira/browse/JDO-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-644:
Attachment: jta-01-new.patch
Per discussion at the last teleconference, propose using this new patch
If the issue is support for JDBC setQueryTimeout, it appears that at
least PostgreSQL lacks support. Here are links to discussions of the
issue for a few databases.
Oracle: supported, but timing issues can affect results
http://forums.oracle.com/forums/thread.jspa?threadID=550257
[
https://issues.apache.org/jira/browse/JDO-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse resolved JDO-639.
-
Resolution: Fixed
Complete with revision 829438
tck enhancement should make use of feature
3
Reporter: Michelle Caisse
Doing maven build in runtime2, I get:
java:compile:
[echo] Compiling to /home/michelle/jdo/jdo/trunk/runtime20/target/classes
[javac] Compiling 51 source files to
/home/michelle/jdo/jdo/trunk/runtime20/target/classes
[javac]
/home/michelle/jdo
[
https://issues.apache.org/jira/browse/JDO-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12769028#action_12769028
]
Michelle Caisse commented on JDO-644:
-
I don't think we're maintaining the -legacy
Hi,
We will have our regular meeting Friday, October 23 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Change JTA 1.1 dependency artifact id from
[
https://issues.apache.org/jira/browse/JDO-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-639:
Attachment: jdo-639.txt
The attached patch implements the changes as spec'ed. Enhancement and TCK run
[
https://issues.apache.org/jira/browse/JDO-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12766831#action_12766831
]
Michelle Caisse commented on JDO-641:
-
After creating the missing files, this patch works
Hi,
We will have our regular meeting Friday, October 16 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Update DataNucleus dependencies in tck2
[
https://issues.apache.org/jira/browse/JDO-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12765894#action_12765894
]
Michelle Caisse commented on JDO-641:
-
I get an enhancer test failure after applying
Hi,
We will have our regular meeting Friday, October 2 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. javax.jdo.Enhancer fails to pass full path name
Components: api2
Affects Versions: JDO 2 maintenance release 3
Reporter: Michelle Caisse
Assignee: Craig Russell
When a directory is supplied as an argument to the enhancer, javax.jdo.Enhancer
does not pass full path name to the implementation's enhancer, so
[
https://issues.apache.org/jira/browse/JDO-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12748799#action_12748799
]
Michelle Caisse commented on JDO-635:
-
Checked in documentation fix with revision 808870
Hi,
We will have our regular meeting Friday, August 28 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Add annotations for instance callbacks
Hi,
We will have our regular meeting Friday, August 14 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Add annotations for instance callbacks
Hi,
We will have our regular meeting Friday, August 7 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Patch to review for
Hi,
We will NOT have our regular meeting this week. Back next week.
-- Michelle
Attendees: Craig Russell, Michelle Caisse
1. Using resource names vs file names: Add javax.jdo.JDOEnhancerMain to
call the enhancer via standard API
https://issues.apache.org/jira/browse/JDO-621
Agree that resource names which don't reference an exact file location
are a good idea
Hi,
We will have our regular meeting Friday, July 24 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Using resource names vs file names: Add
[
https://issues.apache.org/jira/browse/JDO-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12733472#action_12733472
]
Michelle Caisse commented on JDO-635:
-
I was able to compile with JDK 1.5.0.18 on Linux
Hi,
We will have our regular meeting Friday, July 3 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. JDO TCK project.properties changes
2. DataNucleus
Attendees: Michael Bouschen, Michelle Caisse
1. Use JDO TCK to test Querydsl query creation?
The Query test suite in the JDO TCK could be used to extract the JDOQL
and use this to generate a query. There is no way to inject the
generated JDOQL into the tests (without rewriting the tests
Hi,
We will have our regular meeting Friday, June 5 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. JDOQL Querydsl
2. Other issues
Action Items
stumbling on the problem of running the tck against
datanucleus as implementation under test. Michelle had written previously:
FromMichelle Caisse mcai...@sonic.net
Subject Re: runtck.iut
DateFri, 03 Apr 2009 04:00:00 GMT
I just checked in a fix for this problem. When the tck
Hi,
We will have our regular meeting Friday, May 29 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. MetaData specification API patch
[
https://issues.apache.org/jira/browse/JDO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714291#action_12714291
]
Michelle Caisse commented on JDO-615:
-
Patch applies fine for me but I get:
java:compile
[+1] Release JDO 2.3 early access api, tck, enhancer, model, and util
Tests pass, looks good.
-- Michelle
Andy Jefferson wrote:
This vote is to release JDO 2.3 EA (early access) which contains the API jar
and the TCK. **This is not to release the specification**. The release of the
JDO2.3
Hi,
We will have our regular meeting Friday, May 8 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. [VOTE] Release JDO2.3 early access
2. JDO 2.3-ea :
Hi,
We will have our regular meeting Friday, May 1 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. API required for enabling/disabling FOR UPDATE
Hi,
We will have our regular meeting Friday, April 3 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. M2 repo error
2. Embedded object and evict
3.
I just checked in a fix for this problem. When the tck datanucleus
dependencies change, both jdo.jdori.classpath in maven.xml and
iut.runtck.classpath in build.properties need to be updated in parallel.
The latter is used when runtck.iut is invoked.
-- Michelle
Joerg von Frantzius wrote:
Hi,
We will have our regular meeting Friday, March 27 at 9 am PDT to discuss
JDO TCK issues and status. NOTE that the U.S. has switched to Daylight
Savings Time
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Hi,
We will have our regular meeting Friday, February 27 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Support for streams
Hi,
We will have our regular meeting Friday, February 20 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Support for streams
Hi,
We will have our regular meeting Friday, February 13 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Enhancer specification proposal
2. Other
Hi,
We will have our regular meeting Friday, February 6 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Model API. JDO-615
2. Other issues
Should we
Hi,
We will have our regular meeting Friday, January 9 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Enhancer specification text
2. Other issues
Hi,
We will have our regular meeting Friday, December 19 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. (JDO-591) Enhancer Invocation API
2. Other
Hi,
We will have our regular meeting Friday, December 11 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. (JDO-615) MetaData specification API
2.
Hi,
We will have our regular meeting Friday, December 4 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. (JDO-615) MetaData specification API
2.
Issue Type: Bug
Components: specification
Affects Versions: JDO 2 maintenance release 2
Reporter: Michelle Caisse
Assignee: Michelle Caisse
Priority: Minor
Fix For: JDO 2 maintenance release 3
In the bookmarks (sidebar TOC
There will be no conference call on Friday November 28 due to the U.S.
Thanksgiving holiday.
-- Michelle
Hi,
We will have our regular meeting Friday, November 21 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. (JDO-591) Enhancer Invocation API
2.
[
https://issues.apache.org/jira/browse/JDO-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse resolved JDO-613.
-
Resolution: Fixed
Fix Version/s: JDO 2 maintenance release 3
fixed in trunk
Missing
[
https://issues.apache.org/jira/browse/JDO-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse closed JDO-613.
---
Fixed in trunk and 2.2.1
Missing addTearDownClass in PersistenceManagerTest
[
https://issues.apache.org/jira/browse/JDO-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-613:
Fix Version/s: JDO 2 maintenance release 2 update 1
Missing addTearDownClass
[
https://issues.apache.org/jira/browse/JDO-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse closed JDO-611.
---
Resolution: Fixed
Fix Version/s: JDO 2 maintenance release 2 update 1
JDO 2
Hi,
We will have our regular meeting Friday, November 14 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. (JDO-591) Enhancer Invocation API
2.
[
https://issues.apache.org/jira/browse/JDO-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse reassigned JDO-613:
---
Assignee: Michelle Caisse
Missing addTearDownClass in PersistenceManagerTest
[
https://issues.apache.org/jira/browse/JDO-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse reassigned JDO-611:
---
Assignee: Michelle Caisse
GetObjectIdForPersistentInterface - Implementation Class / PICompany
Hi,
We will have our regular meeting Friday, November 7 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Methods in the result of an JDOQL query
2.
Hi,
We will have our regular meeting Friday, October 31 at 9 am PDT to
discuss JDO TCK issues and status. NOTE that the U.S. is still on
daylight savings time.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
member]
Michelle Caisse [pmc member]
Christian Ernst
Andy Jefferson [pmc member]
Craig Russell [pmc member]
Richard Schilling
-- Michelle
Hi,
We will have our regular meeting Friday, October 24 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Methods in the result of an JDOQL query
2.
+1
Tested on Windows and Ubuntu linux.
-- Michelle
Michelle Caisse wrote:
This vote is to release the Apache JDO 2.2 specification, TCK, and API
(both legacy and current versions) with the projects that they depend
on: enhancer, model, and util.
[+1] Release JDO 2.2 specification, api, tck
Hi,
We will have our regular meeting Friday, October 17 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. JDO 2.2 release status
2. JDO 2.3 planning
[
https://issues.apache.org/jira/browse/JDO-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-500:
Fix Version/s: (was: JDO 2 maintenance release 2)
JDO 2 maintenance release 3
[
https://issues.apache.org/jira/browse/JDO-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-557:
Affects Version/s: (was: JDO 2 maintenance release 1)
JDO 2 maintenance
[
https://issues.apache.org/jira/browse/JDO-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-557:
Fix Version/s: (was: JDO 2 maintenance release 2)
JDO 2 maintenance
This vote is to release the Apache JDO 2.2 specification, TCK, and API
(both legacy and current versions) with the projects that they depend
on: enhancer, model, and util.
[+1] Release JDO 2.2 specification, api, tck, enhancer, model, and util
[0] Don't care
[-1] Don't releaseJDO 2.2
Some things need to be ported to tck2-legacy. Signature test fails and a
query test fails (both identity types).
1)
testSignatures(org.apache.jdo.tck.api.SignatureTest)junit.framework.AssertionFailedError:
API Signature Test failed:
Found problems or signature descrepancies.
Test Output:
tests to a point in time where someone wants to own the tck2-legacy code.
Craig
On Oct 9, 2008, at 11:08 AM, Michelle Caisse wrote:
Some things need to be ported to tck2-legacy. Signature test fails
and a query test fails (both identity types).
1)
testSignatures
Hi,
We will have our regular meeting Friday, October 10 at 9 am PDT (7 pm
EEST) to discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. JDO 2.2 release issues
2. Use of
Hi Richard,
I also don't see this error message when running maven javadoc from
trunk/api2. The variables that use the assignment that is producing
this error only occur in the top-level maven.xml in trunk, not the one
in api2. So it's hard to see how you would get this from api2.
--
I haven't run the TCK for a while, but I'm getting the following errors
with transactions.conf in the new 2.2 branch (4 errors total, 2 for each
identity type). I'm using datanucleus 1.0.1.
20:14:03,296 (main) INFO [org.apache.jdo.tck] - Exception during setUp
or runtest:
Hi,
We will have our regular meeting Friday, September 19 at 9 am PDT (7 pm
EEST) to discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Control over transaction
Attendees also included Richard Schilling and Michael Bouschen.
-- Michelle
Craig L Russell wrote:
Attendees: Michelle Caisse, Craig Russell
Agenda:
1. JDO 2.2 draft spec: The draft has been published on Craig's Apache
home page http:people.apache.org/~clr/jdo-2008-09-12.pdf . AI
Hi,
We will have our regular meeting Friday, September 12 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. JDO 2.2 draft spec
2. Control over
Hi,
We will have our regular meeting Friday, September 5 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. JDO 2.2 release timing
2. Other issues
The vote to release Apache JDO 2.1.1 passed with six +1 votes and zero 0
and -1 votes.
Andy Jefferson
Craig Russell (binding)
Michelle Caisse (binding)
Christian Ernst
Awais Bajwa
Michael Bouschen (binding)
-- Michelle
Original Message
Subject:[VOTE] Release Apache
Hi,
We will have our regular meeting Friday, Aug 29 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. JDO 2.2 release timing
2. Other issues
Action
[
https://issues.apache.org/jira/browse/JDO-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse resolved JDO-566.
-
Resolution: Fixed
Completed: At revision: 688171
One output file per schema/identity type
[
https://issues.apache.org/jira/browse/JDO-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse resolved JDO-595.
-
Resolution: Fixed
Completed: At revision: 688171
Now reports in standard output whether the run
Hi,
We will have our regular meeting Friday, Aug 22 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. api2-legacy: maintain or dump?
2. JDO 2.2 release
[
https://issues.apache.org/jira/browse/JDO-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse resolved JDO-583.
-
Resolution: Fixed
Completed: At revision: 687404
Works for both /* */ and // comments.
License
[
https://issues.apache.org/jira/browse/JDO-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse resolved JDO-603.
-
Resolution: Fixed
Completed: At revision: 687454
dist goal fails if top level dir does not end
[
https://issues.apache.org/jira/browse/JDO-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12622917#action_12622917
]
Michelle Caisse commented on JDO-603:
-
We should test on dist that the directory has
[
https://issues.apache.org/jira/browse/JDO-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse resolved JDO-585.
-
Resolution: Fixed
Fix Version/s: (was: JDO 2 maintenance release 2)
Updated
[
https://issues.apache.org/jira/browse/JDO-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse resolved JDO-593.
-
Resolution: Fixed
Changes are in 2.1.1 branch. Maintenance release is in progress.
Cleanup
201 - 300 of 1141 matches
Mail list logo
