Hi Michelle,
I'm afraid it's too late to vote, but just in case it's not:
+1
Regards Michael
This vote is to release the Apache JDO 2.1.1 TCK and API (both legacy
and current versions) with the projects that they depend on: enhancer,
model, and util.
[+1] Release JDO 2.1.1 api, tck, enhanc
[
https://issues.apache.org/jira/browse/JDO-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Russell reassigned JDO-595:
-
Assignee: Michelle Caisse
> Provide more configuration output from test run
> --
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. api2-legacy: maintain or dump? Looking for a volunteer to back-port
all of the api2 changes to api2-legacy. To stimulate discussion, Craig
will call for a VOTE on the expert group and dev aliases.
2. JDO 2.2 release tim
> 2. There is one issue that is a bug in the reference implementation
> https://issues.apache.org/jira/browse/JDO-573 Is this going to be fixed any
> time soon?
The short answer is no.
The long answer is as follows. The JDOQL process used by the DataNucleus RDBMS
plugin uses the mechanism that T
[
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 in targ
[
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 w
