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 (JIRA)" <ji...@apache.org> on 2008/11/23 23:07:44 UTC
[jira] Created: (JDO-618) Deprecate api2-legacy and tck2-legacy
Deprecate api2-legacy and tck2-legacy
-------------------------------------
Key: JDO-618
URL: https://issues.apache.org/jira/browse/JDO-618
Project: JDO
Issue Type: Task
Components: api2-legacy, tck2-legacy
Affects Versions: JDO 2 maintenance release 3
Reporter: Michael Bouschen
Assignee: Michael Bouschen
Fix For: JDO 2 maintenance release 3
There is the idea of requiring JDK 1.5 for JDO 2.3 and subsequent releases. This means there are no more planned releases of api2-legacy and thus the subprojects api2-legacy and tck2-legacy are not needed any longer.
Some implementation details:
- Add a comment to the project.xml in api2-legacy and tck2-legacy that the subproject is deprecated.
- Remove api2-legacy and tck2-legacy from the list of subprojects in the top level project.properties.
- Check JDO Wiki (e.g. FrontPage Topic 4, ProjectStructure)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JDO-618) Deprecate api2-legacy and tck2-legacy
Posted by "Andy Jefferson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Jefferson resolved JDO-618.
--------------------------------
Resolution: Fixed
Assignee: Andy Jefferson (was: Michael Bouschen)
All references to legacy are marked as deprecated
> Deprecate api2-legacy and tck2-legacy
> -------------------------------------
>
> Key: JDO-618
> URL: https://issues.apache.org/jira/browse/JDO-618
> Project: JDO
> Issue Type: Task
> Components: api2-legacy, tck2-legacy
> Affects Versions: JDO 2 maintenance release 3
> Reporter: Michael Bouschen
> Assignee: Andy Jefferson
> Fix For: JDO 2 maintenance release 3
>
>
> There is the idea of requiring JDK 1.5 for JDO 2.3 and subsequent releases. This means there are no more planned releases of api2-legacy and thus the subprojects api2-legacy and tck2-legacy are not needed any longer.
> Some implementation details:
> - Add a comment to the project.xml in api2-legacy and tck2-legacy that the subproject is deprecated.
> - Remove api2-legacy and tck2-legacy from the list of subprojects in the top level project.properties.
> - Check JDO Wiki (e.g. FrontPage Topic 4, ProjectStructure)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.