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 "Andy Jefferson (JIRA)" <ji...@apache.org> on 2011/02/24 14:40:38 UTC
[jira] Created: (JDO-676) Upgrade to use DataNucleus 3.0 jars
Upgrade to use DataNucleus 3.0 jars
-----------------------------------
Key: JDO-676
URL: https://issues.apache.org/jira/browse/JDO-676
Project: JDO
Issue Type: Task
Components: tck
Reporter: Andy Jefferson
Assignee: Andy Jefferson
Fix For: JDO 3 maintenance release 1
DataNucleus 2.2 is in maintenance mode now, and for timescales of JDO3.1 we need to be using DataNucleus 3.0 (although milestone builds currently, though as stable as any previous release)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (JDO-676) Upgrade to use DataNucleus 3.0 jars
Posted by "Andy Jefferson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Jefferson resolved JDO-676.
--------------------------------
Resolution: Fixed
TCK Maven1 build now uses relevant DataNucleus 3.0 M2 jars. Presumably the Maven2 build will need updating, but AFAIK that isn't complete
> Upgrade to use DataNucleus 3.0 jars
> -----------------------------------
>
> Key: JDO-676
> URL: https://issues.apache.org/jira/browse/JDO-676
> Project: JDO
> Issue Type: Task
> Components: tck
> Reporter: Andy Jefferson
> Assignee: Andy Jefferson
> Fix For: JDO 3 maintenance release 1
>
>
> DataNucleus 2.2 is in maintenance mode now, and for timescales of JDO3.1 we need to be using DataNucleus 3.0 (although milestone builds currently, though as stable as any previous release)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira